From: mbrugger@suse.com (Matthias Brugger)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/2] tee: optee: report OP-TEE revision information
Date: Fri, 12 Jan 2018 13:11:30 +0100 [thread overview]
Message-ID: <e02ea595-946e-c94e-19a8-5ba1a57cb3df@suse.com> (raw)
In-Reply-To: <cover.1511533457.git.jerome.forissier@linaro.org>
On 11/24/2017 03:47 PM, Jerome Forissier wrote:
> Hi,
>
> This patchset updates the OP-TEE driver to report the version of the
> secure OS upon initialization. To further facilitate troubleshooting,
> an optional build ID is introduced in the response to the
> OPTEE_SMC_CALL_GET_OS_REVISION request. Upstream OP-TEE uses this field
> to report its Git SHA1 since commit 29cff5cf09aa ("core: GET_OS_REVISION:
> return SHA1 of current Git commit").
>
> Typical boot log (>> is introduced by this patchset):
>
> optee: probing for conduit method from DT.
> >> optee: revision 2.6 (947cfeec)
> optee: initialized driver
>
> ...or, if the build ID is not set by the TEE or set to zero:
>
> optee: probing for conduit method from DT.
> >> optee: revision 2.6
> optee: initialized driver
>
> Jerome Forissier (2):
> tee: optee: GET_OS_REVISION: document a2 as a build identifier
> tee: optee: report OP-TEE revision information
>
> drivers/tee/optee/core.c | 23 +++++++++++++++++++++++
> drivers/tee/optee/optee_smc.h | 10 +++++++++-
> 2 files changed, 32 insertions(+), 1 deletion(-)
>
Reviewed-by: Matthias Brugger <mbruger@suse.com>
prev parent reply other threads:[~2018-01-12 12:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-24 14:47 [PATCH 0/2] tee: optee: report OP-TEE revision information Jerome Forissier
2017-11-24 14:47 ` [PATCH 1/2] tee: optee: GET_OS_REVISION: document a2 as a build identifier Jerome Forissier
2017-11-24 14:47 ` [PATCH 2/2] tee: optee: report OP-TEE revision information Jerome Forissier
2018-01-12 8:25 ` [PATCH 0/2] " Jerome Forissier
2018-01-12 12:11 ` Matthias Brugger [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=e02ea595-946e-c94e-19a8-5ba1a57cb3df@suse.com \
--to=mbrugger@suse.com \
--cc=linux-arm-kernel@lists.infradead.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).