Subject: Re: [PATCH] tee: ACPI support for optee driver
To: 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>
References: <1505977937-25034-1-git-send-email-mchitale@apm.com>
CC: <patches@apm.com>
From: Hanjun Guo <guohanjun@huawei.com>
Message-ID: <59C36E18.1050106@huawei.com>
Date: Thu, 21 Sep 2017 15:45:28 +0800
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:38.0) Gecko/20100101
 Thunderbird/38.5.1
MIME-Version: 1.0
In-Reply-To: <1505977937-25034-1-git-send-email-mchitale@apm.com>
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 562
Lines: 16

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