arm-trusted-firmware

4477 Commits

5 Branches

114 Tags

55 MiB

Tree: 55cf015c20

Commit Graph

Author	SHA1	Message	Date
Rajan Vaja	85dc2d4dae	zynqmp: pm_service: Make PMU IPI-1 channel unsecure PMU IPI-1 is used for callbacks from PMU to master. Unsecure master can also receive callbacks from PMU, so make PMU IPI-1 as non-secure. All requests from master(s) to PMU would still go on PMU IPI-1 secure channel. Signed-off-by: Rajan Vaja <rajanv@xilinx.com>	7 years ago
Wendy Liang	dc1dfe831f	Introduce ZynqMP IPI implementation Previously, ZynqMP IPI in ATF is only for ZynqMP PM, This patch is to have a ZynqMP IPI implementation to handle both ZynqMP PM IPI requirement and IPI mailbox service requirement which will be introduced next. We control IPI agents registers access but not IPI buffers access in this implementation. Each IPI mailbox user will directly access the IPI buffers. Signed-off-by: Wendy Liang <jliang@xilinx.com>	7 years ago

Author

SHA1

Message

Date

Rajan Vaja

85dc2d4dae

zynqmp: pm_service: Make PMU IPI-1 channel unsecure

PMU IPI-1 is used for callbacks from PMU to master. Unsecure
master can also receive callbacks from PMU, so make PMU IPI-1
as non-secure.

All requests from master(s) to PMU would still go on PMU IPI-1
secure channel.

Signed-off-by: Rajan Vaja <rajanv@xilinx.com>

7 years ago

Wendy Liang

dc1dfe831f

Introduce ZynqMP IPI implementation

Previously, ZynqMP IPI in ATF is only for ZynqMP PM,
This patch is to have a ZynqMP IPI implementation to handle
both ZynqMP PM IPI requirement and IPI mailbox service requirement
which will be introduced next.

We control IPI agents registers access but not IPI buffers access in
this implementation. Each IPI mailbox user will directly access the
IPI buffers.

Signed-off-by: Wendy Liang <jliang@xilinx.com>

7 years ago

2 Commits (55cf015c20d6c768344338fd1215c729844a985f)