From: Sudeep Holla <sudeep.holla@arm.com>
To: Rob Herring <robh@kernel.org>
Cc: Sudeep Holla <sudeep.holla@arm.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
"linux-arm-msm@vger.kernel.org" <linux-arm-msm@vger.kernel.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
Arnd Bergmann <arnd@arndb.de>, Andy Gross <andy.gross@linaro.org>,
Jens Wiklander <jens.wiklander@linaro.org>,
Bjorn Andersson <bjorn.andersson@linaro.org>
Subject: Re: [PATCH 1/3] firmware: of: populate /firmware/ node during init
Date: Fri, 11 Aug 2017 16:22:35 +0100 [thread overview]
Message-ID: <9e247a72-67d6-2f85-90bd-1a5fb6852c0e@arm.com> (raw)
In-Reply-To: <7a3b73d0-988c-1d2a-43cc-4d30b4eac0f1@arm.com>
On 11/08/17 16:16, Sudeep Holla wrote:
>
>
> On 11/08/17 15:15, Rob Herring wrote:
[...]
> "tlm,trusted-foundations" appears
>> to be needed early for bringing up cores, so it probably can't change.
>
> That was my intially understand too when I looked at the way probe was
> handled, but then I see it's module_init, so I went ahead with this change.
>
Scratch this, I was referring "linaro,optee-tz" and not
"tlm,trusted-foundations"
--
Regards,
Sudeep
next prev parent reply other threads:[~2017-08-11 15:22 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-11 13:30 [PATCH 0/3] " Sudeep Holla
2017-08-11 13:30 ` [PATCH 1/3] " Sudeep Holla
2017-08-11 14:15 ` Rob Herring
2017-08-11 15:16 ` Sudeep Holla
2017-08-11 15:22 ` Sudeep Holla [this message]
2017-08-11 14:37 ` Arnd Bergmann
2017-08-11 15:05 ` Rob Herring
2017-08-11 15:54 ` Arnd Bergmann
2017-08-14 13:28 ` Sudeep Holla
2017-09-27 16:54 ` Sudeep Holla
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=9e247a72-67d6-2f85-90bd-1a5fb6852c0e@arm.com \
--to=sudeep.holla@arm.com \
--cc=andy.gross@linaro.org \
--cc=arnd@arndb.de \
--cc=bjorn.andersson@linaro.org \
--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
all inboxes | Powered by JetHome®