From: Jon Masters <jcm@redhat.com>
To: Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>,
Hanjun Guo <guohanjun@huawei.com>
Cc: Mayuresh Chitale <mchitale@apm.com>,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, linux-acpi@vger.kernel.org,
jens.wiklander@linaro.org, patches@apm.com
Subject: Re: [PATCH] tee: ACPI support for optee driver
Date: Tue, 3 Oct 2017 02:19:00 -0400 [thread overview]
Message-ID: <03008e2f-5a2f-78af-528a-3b31b1013aad@redhat.com> (raw)
In-Reply-To: <20170922093703.GD1523@red-moon>
On 09/22/2017 05:37 AM, Lorenzo Pieralisi wrote:
> On Thu, Sep 21, 2017 at 03:45:28PM +0800, Hanjun Guo wrote:
>> On 2017/9/21 15:12, Mayuresh Chitale wrote:
>>> This patch modifies the optee driver to add support for parsing
>>> the conduit method from an ACPI node.
>>
>> Sorry I didn't involve this earlier, but I think this is a wrong
>> approach, in ACPI 5.1+ spec, there is a bit in FADT table which
>> indicates PSCI using SMC or HVC, please see ACPI 6.2 [1],
>> Table 5-37 Fixed ACPI Description Table ARM Boot Architecture Flags.
>>
>> Can we just use that to get the conduit method for optee driver too?
>>
>> [1]: http://www.uefi.org/sites/default/files/resources/ACPI_6_2.pdf
>
> It is just not a matter of conduit method but also to define how OPTEE
> should be detected. It is up to Linaro (who owns OP-TEE) to put forward
> a binding at ACPI (ARM) spec level.
>
> We do not define ACPI bindings on a kernel mailing list.
>
> NAK on this patch.
Is this actively being tracked by Linaro? If not, can Applied folks ping
me off-list and I will proxy your request into Linaro.
Jon.
--
Computer Architect | Sent from my Fedora powered laptop
prev parent reply other threads:[~2017-10-03 6:19 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-21 7:12 [PATCH] tee: ACPI support for optee driver Mayuresh Chitale
2017-09-21 7:45 ` Hanjun Guo
2017-09-21 7:56 ` Mayuresh Chitale
2017-09-22 9:37 ` Lorenzo Pieralisi
2017-10-03 6:19 ` Jon Masters [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=03008e2f-5a2f-78af-528a-3b31b1013aad@redhat.com \
--to=jcm@redhat.com \
--cc=guohanjun@huawei.com \
--cc=jens.wiklander@linaro.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lorenzo.pieralisi@arm.com \
--cc=mchitale@apm.com \
--cc=patches@apm.com \
/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