From: Sudeep Holla <sudeep.holla@arm.com>
To: linux-kernel@vger.kernel.org
Cc: Sudeep Holla <sudeep.holla@arm.com>,
linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
Rob Herring <robh@kernel.org>, Arnd Bergmann <arnd@arndb.de>,
Andy Gross <andy.gross@linaro.org>,
Jens Wiklander <jens.wiklander@linaro.org>
Subject: [PATCH 0/3] firmware: of: populate /firmware/ node during init
Date: Fri, 11 Aug 2017 14:30:34 +0100 [thread overview]
Message-ID: <1502458237-1683-1-git-send-email-sudeep.holla@arm.com> (raw)
Hi Rob, Arnd,
Recently Rob pointed to place SCMI device node under /firmware/ node
and when I did that, I observed I had to populate the node first to
get scmi node populated. Some research showed qcom_scm and optee drivers
handle it in their own ways. This small series is to make it generic
so that all the users of /firmware/ node need not repeat the same.
Sudeep Holla (3):
firmware: of: populate /firmware/ node during init
firmware: qcom_scm: drop redandant of_platform_populate
drivers: tee: rework optee_driver_{init,exit} to use platform device
drivers/firmware/Makefile | 1 +
drivers/firmware/of.c | 34 +++++++++++++++++++++
drivers/firmware/qcom_scm.c | 24 ---------------
drivers/tee/optee/core.c | 74 +++++++++++++++------------------------------
4 files changed, 60 insertions(+), 73 deletions(-)
create mode 100644 drivers/firmware/of.c
--
2.7.4
next reply other threads:[~2017-08-11 13:30 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-11 13:30 Sudeep Holla [this message]
2017-08-11 13:30 ` [PATCH 1/3] firmware: of: populate /firmware/ node during init Sudeep Holla
2017-08-11 14:15 ` Rob Herring
2017-08-11 15:16 ` Sudeep Holla
[not found] ` <7a3b73d0-988c-1d2a-43cc-4d30b4eac0f1-5wv7dgnIgG8@public.gmane.org>
2017-08-11 15:22 ` Sudeep Holla
[not found] ` <1502458237-1683-2-git-send-email-sudeep.holla-5wv7dgnIgG8@public.gmane.org>
2017-08-11 14:37 ` Arnd Bergmann
2017-08-11 15:05 ` Rob Herring
[not found] ` <CABGGisyQKfre_qMqnngOiKbqUaHF0KWKtZyYPJ47iPwgL5t6xw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2017-08-11 15:54 ` Arnd Bergmann
2017-08-14 13:28 ` Sudeep Holla
2017-09-27 16:54 ` Sudeep Holla
[not found] ` <CAK8P3a1p8xS4u5EQ9auqgcmhXaybhDdsa6ah3G-7TeEf+ko9kA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2017-08-11 15:37 ` Sudeep Holla
2017-08-11 13:30 ` [PATCH 2/3] firmware: qcom_scm: drop redandant of_platform_populate Sudeep Holla
2017-08-11 13:30 ` [PATCH 3/3] drivers: tee: rework optee_driver_{init,exit} to use platform device Sudeep Holla
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=1502458237-1683-1-git-send-email-sudeep.holla@arm.com \
--to=sudeep.holla@arm.com \
--cc=andy.gross@linaro.org \
--cc=arnd@arndb.de \
--cc=devicetree@vger.kernel.org \
--cc=jens.wiklander@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh@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 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).