Re: [PATCH v3 5/6] xen/arm: zynqmp: implement zynqmp_eemi

[Julien Grall <julien.grall@arm.com>]

Hi,

On 10/10/2018 11:49 PM, Stefano Stabellini wrote:
> On Tue, 28 Aug 2018, Julien Grall wrote:
>> Hi Stefano,
>>
>> On 11/08/18 01:01, Stefano Stabellini wrote:
>>> From: "Edgar E. Iglesias" <edgar.iglesias@xilinx.com>
>>>
>>> From: Edgar E. Iglesias <edgar.iglesias@xilinx.com>
>>>
>>> zynqmp_eemi uses the defined functions and structs to decide whether to
>>> make a call to the firmware, or to simply return a predefined value.
>>>
>>> Signed-off-by: Edgar E. Iglesias <edgar.iglesias@xilinx.com>
>>> Signed-off-by: Stefano Stabellini <stefanos@xilinx.com>
>>> ---
>>>    xen/arch/arm/platforms/xilinx-zynqmp-eemi.c | 143
>>> +++++++++++++++++++++++++++-
>>>    1 file changed, 142 insertions(+), 1 deletion(-)
>>>
>>> diff --git a/xen/arch/arm/platforms/xilinx-zynqmp-eemi.c
>>> b/xen/arch/arm/platforms/xilinx-zynqmp-eemi.c
>>> index 62cc15c..1dbdf04 100644
>>> --- a/xen/arch/arm/platforms/xilinx-zynqmp-eemi.c
>>> +++ b/xen/arch/arm/platforms/xilinx-zynqmp-eemi.c
>>> @@ -808,7 +808,148 @@ static bool domain_has_mmio_access(struct domain *d,
>>>      bool zynqmp_eemi(struct cpu_user_regs *regs)
>>>    {
>>> -    return false;
>>> +    struct arm_smccc_res res;
>>> +    bool is_mmio_write = false;
>>> +    uint32_t fid = get_user_reg(regs, 0);
>>> +    uint32_t nodeid = get_user_reg(regs, 1);
>>> +    unsigned int pm_fn = fid & 0xFFFF;
>>
>> Here you will receive all the function ID for the SIP subsystem. Can you
>> confirm the EEMI can be accessed from both SMC32 and SMC64 convention?
> 
> Yep

Can you point me to the documentation? For instance, CALL_COUNT, UID and 
VERSION are only accessible via SMC32.

Cheers,

-- 
Julien Grall

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel