From: Ard Biesheuvel <ard.biesheuvel@linaro.org>
To: linux-arm-kernel@lists.infradead.org
Cc: linux-kernel@vger.kernel.org,
Ard Biesheuvel <ard.biesheuvel@linaro.org>,
Jens Wiklander <jens.wiklander@linaro.org>,
Sumit Garg <sumit.garg@linaro.org>,
Graeme Gregory <graeme.gregory@linaro.org>,
Jerome Forissier <jerome.forissier@linaro.org>
Subject: [RFC PATCH 0/2] allow optee to be exposed on ACPI systems
Date: Thu, 27 Dec 2018 20:01:20 +0100 [thread overview]
Message-ID: <20181227190122.23149-1-ard.biesheuvel@linaro.org> (raw)
Similar to how OP-TEE is exposed as a pseudo device under /firmware/optee
on DT systems, permit OP-TEE presence to be exposed via a device object
in the ACPI namespace. This makes it possible to model the OP-TEE interface
as a platform device gets instantiated automatically both on DT and ACPI
systems, and implement the driver as a platform driver that is able to
use the generic device properties API to access the 'method' attribute
as well as potential future extensions to the binding that introduce
new attributes.
What remains to be discussed is how to expose OP-TEE pseudo devices,
e.g., Sumit's RNG implementation on SynQuacer which we would like to
bind a Linux driver to.
Cc: Jens Wiklander <jens.wiklander@linaro.org>
Cc: Sumit Garg <sumit.garg@linaro.org>
Cc: Graeme Gregory <graeme.gregory@linaro.org>
Cc: Jerome Forissier <jerome.forissier@linaro.org>
Ard Biesheuvel (2):
optee: model OP-TEE as a platform device/driver
optee: add ACPI support
drivers/tee/optee/core.c | 94 +++++++++-----------
1 file changed, 41 insertions(+), 53 deletions(-)
--
2.19.2
next reply other threads:[~2018-12-27 19:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-27 19:01 Ard Biesheuvel [this message]
2018-12-27 19:01 ` [RFC PATCH 1/2] optee: model OP-TEE as a platform device/driver Ard Biesheuvel
2019-01-02 9:30 ` Jens Wiklander
2018-12-27 19:01 ` [RFC PATCH 2/2] optee: add ACPI support Ard Biesheuvel
2019-01-02 5:04 ` [RFC PATCH 0/2] allow optee to be exposed on ACPI systems Sumit Garg
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=20181227190122.23149-1-ard.biesheuvel@linaro.org \
--to=ard.biesheuvel@linaro.org \
--cc=graeme.gregory@linaro.org \
--cc=jens.wiklander@linaro.org \
--cc=jerome.forissier@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sumit.garg@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).