From: guohanjun@huawei.com (Hanjun Guo)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] tee: ACPI support for optee driver
Date: Thu, 21 Sep 2017 15:45:28 +0800 [thread overview]
Message-ID: <59C36E18.1050106@huawei.com> (raw)
In-Reply-To: <1505977937-25034-1-git-send-email-mchitale@apm.com>
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
Thanks
Hanjun
next prev parent reply other threads:[~2017-09-21 7:45 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 [this message]
2017-09-21 7:56 ` Mayuresh Chitale
2017-09-22 9:37 ` Lorenzo Pieralisi
2017-10-03 6:19 ` Jon Masters
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=59C36E18.1050106@huawei.com \
--to=guohanjun@huawei.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).