From: Rob Herring <robh@kernel.org>
To: Jerome Forissier <jerome.forissier@linaro.org>
Cc: Mark Rutland <mark.rutland@arm.com>,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
Peter Maydell <peter.maydell@linaro.org>,
Etienne Carriere <etienne.carriere@linaro.org>,
tee-dev@lists.linaro.org
Subject: Re: [PATCH v2] Documentation: dt: Add binding for /secure-chosen/stdout-path
Date: Fri, 12 Oct 2018 15:45:13 -0500 [thread overview]
Message-ID: <20181012204513.GA29769@bogus> (raw)
In-Reply-To: <20181008101642.8040-1-jerome.forissier@linaro.org>
On Mon, Oct 08, 2018 at 06:16:42PM +0800, Jerome Forissier wrote:
> Some platforms may use a single device tree to describe two address
> spaces, as described in d9f43babb998 ("Documentation: dt: Add bindings
> for Secure-only devices"). For these platforms it makes sense to define
> a secure counterpart of /chosen, namely: /secure-chosen. This new node
> is meant to be used by the secure firmware to pass data to the secure
> OS. Only the stdout-path property is supported for now.
>
> Signed-off-by: Jerome Forissier <jerome.forissier@linaro.org>
> ---
>
> Notes:
> Sending this again, slightly modified. Previous submission was in March
> 2017 [1]. Since then, OP-TEE has implemented this binding for platforms
> that use DT [2] (fallback to /chosen/stdout-path to be implemented in
> [3]). A patch for QEMU has been proposed [4], to which the maintainer
> responded "Are the DT bindings upstream yet?" ;-)
>
> [1] https://patchwork.kernel.org/patch/9602401/
> [2] https://github.com/OP-TEE/optee_os/commit/4dc31c52544a
> [3] https://github.com/OP-TEE/optee_os/pull/2569
> [4] https://patchwork.ozlabs.org/patch/979345/
>
> Changes since v1:
> - Use "should" instead of "may" ("...the Secure OS should use the value
> of /chosen/stdout-path...").
>
> Documentation/devicetree/bindings/arm/secure.txt | 19 ++++++++++++++++++-
> 1 file changed, 18 insertions(+), 1 deletion(-)
Applied.
Rob
prev parent reply other threads:[~2018-10-12 20:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-08 10:16 [PATCH v2] Documentation: dt: Add binding for /secure-chosen/stdout-path Jerome Forissier
2018-10-12 20:45 ` Rob Herring [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=20181012204513.GA29769@bogus \
--to=robh@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=etienne.carriere@linaro.org \
--cc=jerome.forissier@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=peter.maydell@linaro.org \
--cc=tee-dev@lists.linaro.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).