From: Peter Maydell <peter.maydell@linaro.org>
To: Jerome Forissier <jerome.forissier@linaro.org>
Cc: qemu-arm <qemu-arm@nongnu.org>,
QEMU Developers <qemu-devel@nongnu.org>,
Etienne Carriere <etienne.carriere@linaro.org>,
tee-dev@lists.linaro.org, Rob Herring <robh+dt@kernel.org>
Subject: Re: [Qemu-devel] [PATCH] hw/arm/virt: add DT property /secure-chosen/sdtout-path being secure UART
Date: Tue, 16 Oct 2018 11:14:18 +0100 [thread overview]
Message-ID: <CAFEAcA-+tmc5E7VksWTe_0UEs5xt9YBVGiE+8ev8ChDu0OLRYw@mail.gmail.com> (raw)
In-Reply-To: <70f911cb-7d49-e8cb-e3cd-081033e010c2@linaro.org>
On 15 October 2018 at 10:08, Jerome Forissier
<jerome.forissier@linaro.org> wrote:
> Hi Peter,
>
> On 10/05/2018 11:26 AM, Jerome Forissier wrote:
>> +CC: Rob Herring
>>
>> On 10/05/2018 11:16 AM, Peter Maydell wrote:
>>> On 5 October 2018 at 09:07, Jerome Forissier
>>> <jerome.forissier@linaro.org> wrote:
>>>> Bindings for /secure-chosen and /secure-chosen/stdout-path have been
>>>> proposed 1.5 years ago [1] and implemented in OP-TEE at the same time [2].
>>>>
>>>> This patch creates the property when the machine is secure.
>>>>
>>>> [1] https://patchwork.kernel.org/patch/9602401/
>>>> [2] https://github.com/OP-TEE/optee_os/commit/4dc31c52544a
>>>>
>>>> Signed-off-by: Jerome Forissier <jerome.forissier@linaro.org>
>>>
>>> The patch seems OK, but it looks like the DT bindings are
>>> not upstream yet? [*]
>>
>> No, they're not.
>
> Update: Rob has now accepted the bindings [3] (thanks!).
OK; I've applied the QEMU patch to my target-arm.next branch.
thanks
-- PMM
prev parent reply other threads:[~2018-10-16 10:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-05 8:07 [Qemu-devel] [PATCH] hw/arm/virt: add DT property /secure-chosen/sdtout-path being secure UART Jerome Forissier
2018-10-05 9:16 ` Peter Maydell
2018-10-05 9:26 ` Jerome Forissier
2018-10-15 9:08 ` Jerome Forissier
2018-10-16 10:14 ` Peter Maydell [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=CAFEAcA-+tmc5E7VksWTe_0UEs5xt9YBVGiE+8ev8ChDu0OLRYw@mail.gmail.com \
--to=peter.maydell@linaro.org \
--cc=etienne.carriere@linaro.org \
--cc=jerome.forissier@linaro.org \
--cc=qemu-arm@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=robh+dt@kernel.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).