From: James Morse <james.morse@arm.com>
To: Sudeep Holla <sudeep.holla@arm.com>
Cc: linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, "will@kernel.org" <will@kernel.org>,
Catalin Marinas <catalin.marinas@arm.com>
Subject: Re: [PATCH] firmware: arm_sdei: Drop check for /firmware/ node and always register driver
Date: Mon, 4 May 2020 18:14:41 +0100 [thread overview]
Message-ID: <bcadd00b-cd76-8321-e1c9-0a076fe64deb@arm.com> (raw)
In-Reply-To: <20200422122823.1390-1-sudeep.holla@arm.com>
Hi Sudeep,
(CC: +Will and +Catalin)
On 22/04/2020 13:28, Sudeep Holla wrote:
> As with most of the drivers, let us register this driver unconditionally
> by dropping the checks for presence of firmware nodes(DT) or entries(ACPI).
>
> Further, as mentioned in the commit acafce48b07b ("firmware: arm_sdei:
> Fix DT platform device creation"), the core takes care of creation of
> platform device when the appropriate device node is found and probe
> is called accordingly.
>
> Let us check only for the presence of ACPI firmware entry before creating
> the platform device and flag warning if we fail.
Reviewed-by: James Morse <james.morse@arm.com>
Will/Catalin, any chance you could pick this up for v5.8?
Original message:
https://lore.kernel.org/linux-arm-kernel/20200422122823.1390-1-sudeep.holla@arm.com/
Thanks!
James
WARNING: multiple messages have this Message-ID (diff)
From: James Morse <james.morse@arm.com>
To: Sudeep Holla <sudeep.holla@arm.com>
Cc: Catalin Marinas <catalin.marinas@arm.com>,
"will@kernel.org" <will@kernel.org>,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] firmware: arm_sdei: Drop check for /firmware/ node and always register driver
Date: Mon, 4 May 2020 18:14:41 +0100 [thread overview]
Message-ID: <bcadd00b-cd76-8321-e1c9-0a076fe64deb@arm.com> (raw)
In-Reply-To: <20200422122823.1390-1-sudeep.holla@arm.com>
Hi Sudeep,
(CC: +Will and +Catalin)
On 22/04/2020 13:28, Sudeep Holla wrote:
> As with most of the drivers, let us register this driver unconditionally
> by dropping the checks for presence of firmware nodes(DT) or entries(ACPI).
>
> Further, as mentioned in the commit acafce48b07b ("firmware: arm_sdei:
> Fix DT platform device creation"), the core takes care of creation of
> platform device when the appropriate device node is found and probe
> is called accordingly.
>
> Let us check only for the presence of ACPI firmware entry before creating
> the platform device and flag warning if we fail.
Reviewed-by: James Morse <james.morse@arm.com>
Will/Catalin, any chance you could pick this up for v5.8?
Original message:
https://lore.kernel.org/linux-arm-kernel/20200422122823.1390-1-sudeep.holla@arm.com/
Thanks!
James
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2020-05-04 17:14 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-22 12:28 [PATCH] firmware: arm_sdei: Drop check for /firmware/ node and always register driver Sudeep Holla
2020-04-22 12:28 ` Sudeep Holla
2020-05-04 17:14 ` James Morse [this message]
2020-05-04 17:14 ` James Morse
2020-05-04 21:04 ` Will Deacon
2020-05-04 21:04 ` Will Deacon
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bcadd00b-cd76-8321-e1c9-0a076fe64deb@arm.com \
--to=james.morse@arm.com \
--cc=catalin.marinas@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sudeep.holla@arm.com \
--cc=will@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.