Hi Feng,
On Fri, Dec 18, 2020 at 04:41:37PM +0000, Chen Feng via TF-A wrote:
Hi,
While reading the Arm Firmware Framework for Armv8-A https://developer.arm.com/documentation/den0077/latest
I do not find the API that for a sp to request vIRQ, or do I miss something.
Is this some private API that is implementing defined FF-A IDs?
Is what you have in mind is an ABI that allows SP0 to raise an interrupt in SP1?
Could you please provide more information about your use case?
cheers, Achin
-- cheers, feng
-- TF-A mailing list TF-A@lists.trustedfirmware.org https://lists.trustedfirmware.org/mailman/listinfo/tf-a
Hi,
On 2020/12/19 6:04 上午, Achin Gupta wrote:
Hi Feng,
On Fri, Dec 18, 2020 at 04:41:37PM +0000, Chen Feng via TF-A wrote:
Hi,
While reading the Arm Firmware Framework for Armv8-A https://developer.arm.com/documentation/den0077/latest
I do not find the API that for a sp to request vIRQ, or do I miss something.
Is this some private API that is implementing defined FF-A IDs?
Is what you have in mind is an ABI that allows SP0 to raise an interrupt in SP1?
Could you please provide more information about your use case?
I mean a sel1-firmware-driver SP. How does it to enable and request vIRQ from ff-a ABI?
cheers, Achin
-- cheers, feng
-- TF-A mailing list TF-A@lists.trustedfirmware.org https://lists.trustedfirmware.org/mailman/listinfo/tf-a
Hi Feng,
On Sat, Dec 19, 2020 at 07:51:33AM +0800, Chen Feng wrote:
Hi,
On 2020/12/19 6:04 上午, Achin Gupta wrote:
Hi Feng,
On Fri, Dec 18, 2020 at 04:41:37PM +0000, Chen Feng via TF-A wrote:
Hi,
While reading the Arm Firmware Framework for Armv8-A https://developer.arm.com/documentation/den0077/latest
I do not find the API that for a sp to request vIRQ, or do I miss something.
Is this some private API that is implementing defined FF-A IDs?
Is what you have in mind is an ABI that allows SP0 to raise an interrupt in SP1?
Could you please provide more information about your use case?
I mean a sel1-firmware-driver SP. How does it to enable and request vIRQ from ff-a ABI?
Table 3.3 in Section 3.2 of the FF-A spec describes how a SP can request the SPMC to assign a device to it.
The SP manifest must specify the physical interrupts used by the device. It must also specify the MMIO regions of the device.
At run-time, the device is programmed by the SP. The physical device interrupt is received at S-EL2 by the SPMC. The SPMC injects a vIRQ into the SP. The SP uses the HF_INTERRUPT_GET ABI to obtain the ID of the vIRQ.
Does this answer your query?
cheers, Achin
cheers, Achin
-- cheers, feng
-- TF-A mailing list TF-A@lists.trustedfirmware.org https://lists.trustedfirmware.org/mailman/listinfo/tf-a
-- cheers, feng
Hi Feng,
Aligned with Achin.
Just to complement: HF_INTERRUPT_GET is a Hafnium implementation specific hypervisor call (it's not specified by FF-A v1.0): https://git.trustedfirmware.org/hafnium/hafnium.git/tree/inc/vmapi/hf/abi.h#...
Also notice interrupt injection into a SP is work in progress (you won't find the appropriate logic in the upstream implementation). Early changes should be made visible in gerrit in the coming weeks.
Regards, Olivier.
________________________________________ From: Achin Gupta Achin.Gupta@arm.com Sent: 20 December 2020 17:20 To: Chen Feng Cc: Manish Pandey2; Madhukar Pappireddy; Olivier Deprez; tf-a@lists.trustedfirmware.org Subject: Re: [TF-A] Interrupt about ff-a spec
Hi Feng,
On Sat, Dec 19, 2020 at 07:51:33AM +0800, Chen Feng wrote:
Hi,
On 2020/12/19 6:04 上午, Achin Gupta wrote:
Hi Feng,
On Fri, Dec 18, 2020 at 04:41:37PM +0000, Chen Feng via TF-A wrote:
Hi,
While reading the Arm Firmware Framework for Armv8-A https://developer.arm.com/documentation/den0077/latest
I do not find the API that for a sp to request vIRQ, or do I miss something.
Is this some private API that is implementing defined FF-A IDs?
Is what you have in mind is an ABI that allows SP0 to raise an interrupt in SP1?
Could you please provide more information about your use case?
I mean a sel1-firmware-driver SP. How does it to enable and request vIRQ from ff-a ABI?
Table 3.3 in Section 3.2 of the FF-A spec describes how a SP can request the SPMC to assign a device to it.
The SP manifest must specify the physical interrupts used by the device. It must also specify the MMIO regions of the device.
At run-time, the device is programmed by the SP. The physical device interrupt is received at S-EL2 by the SPMC. The SPMC injects a vIRQ into the SP. The SP uses the HF_INTERRUPT_GET ABI to obtain the ID of the vIRQ.
Does this answer your query?
cheers, Achin
cheers, Achin
-- cheers, feng
-- TF-A mailing list TF-A@lists.trustedfirmware.org https://lists.trustedfirmware.org/mailman/listinfo/tf-a
-- cheers, feng
tf-a@lists.trustedfirmware.org
-
Achin Gupta -
Chen Feng -
Olivier Deprez