From: Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>
To: 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: Fri, 22 Sep 2017 10:37:03 +0100 [thread overview]
Message-ID: <20170922093703.GD1523@red-moon> (raw)
In-Reply-To: <59C36E18.1050106@huawei.com>
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.
Lorenzo
WARNING: multiple messages have this Message-ID (diff)
From: lorenzo.pieralisi@arm.com (Lorenzo Pieralisi)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] tee: ACPI support for optee driver
Date: Fri, 22 Sep 2017 10:37:03 +0100 [thread overview]
Message-ID: <20170922093703.GD1523@red-moon> (raw)
In-Reply-To: <59C36E18.1050106@huawei.com>
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.
Lorenzo
next prev parent reply other threads:[~2017-09-22 9:34 UTC|newest]
Thread overview: 11+ 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:12 ` Mayuresh Chitale
2017-09-21 7:45 ` Hanjun Guo
2017-09-21 7:45 ` Hanjun Guo
2017-09-21 7:45 ` Hanjun Guo
2017-09-21 7:56 ` Mayuresh Chitale
2017-09-21 7:56 ` Mayuresh Chitale
2017-09-22 9:37 ` Lorenzo Pieralisi [this message]
2017-09-22 9:37 ` Lorenzo Pieralisi
2017-10-03 6:19 ` Jon Masters
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=20170922093703.GD1523@red-moon \
--to=lorenzo.pieralisi@arm.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=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.