From: Frank Rowand <frowand.list@gmail.com>
To: Sudeep Holla <sudeep.holla@arm.com>,
linux-arm-kernel@lists.infradead.org
Cc: linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
Rob Herring <robh+dt@kernel.org>,
Frank Rowand <frowand.list@gmail.com>
Subject: Re: [RESEND][PATCH 0/4] firmware: of: populate /firmware/ node during init
Date: Mon, 16 Oct 2017 15:44:07 -0700 [thread overview]
Message-ID: <59E53637.8020502@gmail.com> (raw)
In-Reply-To: <1506595562-10592-1-git-send-email-sudeep.holla@arm.com>
+ me
On 09/28/17 03:45, Sudeep Holla wrote:
> Hi Rob, Arnd,
>
> There's a push to place all firmware related device node under
> /firmware/ node. However all the associated drivers are dealing with
> device creation in their own ways. For example, qcom_scm, optee and
> meson-sm drivers deal with the node in their own way. The SCMI drivers
> I am about to add also needs to do the same. This small series is to
> make it generic so that all the users of /firmware/ node need not
> repeat the same.
>
> There was concern that /firmware in DT is fit for /sys/firmware in sysfs.
> IMO anything exposed to userspace from such firmware interface must
> be in "/sys/firmware", but I don't see any issue with kernel handling
> them as platform device/driver internally.
>
> Sudeep Holla (4):
> of: platform: populate /firmware/ node from
> of_platform_default_populate_init()
> firmware: qcom_scm: drop redandant of_platform_populate
> drivers: tee: rework optee_driver_{init,exit} to use platform device
> firmware: meson-sm: rework meson_sm_init to use
> module_platform_driver_probe
>
> drivers/firmware/meson/meson_sm.c | 21 ++++++-----
> drivers/firmware/qcom_scm.c | 24 -------------
> drivers/of/platform.c | 4 +++
> drivers/tee/optee/core.c | 74 +++++++++++++--------------------------
> 4 files changed, 41 insertions(+), 82 deletions(-)
>
> --
> 2.7.4
>
> --
> To unsubscribe from this list: send the line "unsubscribe devicetree" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
prev parent reply other threads:[~2017-10-16 22:44 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-28 10:45 [RESEND][PATCH 0/4] firmware: of: populate /firmware/ node during init Sudeep Holla
2017-09-28 10:45 ` [RESEND][PATCH 1/4] of: platform: populate /firmware/ node from of_platform_default_populate_init() Sudeep Holla
[not found] ` <1506595562-10592-2-git-send-email-sudeep.holla-5wv7dgnIgG8@public.gmane.org>
2017-10-16 22:44 ` Frank Rowand
2017-12-26 21:26 ` Bjorn Andersson
2017-10-17 13:02 ` Rob Herring
[not found] ` <CAL_JsqJYNXoZbN4zydkkZHWYxJuH4ObYJGgz2L7++kMgTWC1vg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2017-10-23 15:59 ` Sudeep Holla
2017-09-28 10:46 ` [RESEND][PATCH 2/4] firmware: qcom_scm: drop redandant of_platform_populate Sudeep Holla
2017-09-28 10:46 ` [RESEND][PATCH 3/4] drivers: tee: rework optee_driver_{init,exit} to use platform device Sudeep Holla
2017-09-28 10:46 ` [RESEND][PATCH 4/4] firmware: meson-sm: rework meson_sm_init to use module_platform_driver_probe Sudeep Holla
2017-10-16 22:44 ` Frank Rowand [this message]
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=59E53637.8020502@gmail.com \
--to=frowand.list@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh+dt@kernel.org \
--cc=sudeep.holla@arm.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).