diff options
| author | Soby Mathew <soby.mathew@arm.com> | 2016-06-07 17:06:27 +0100 |
|---|---|---|
| committer | Soby Mathew <soby.mathew@arm.com> | 2016-07-07 11:59:33 +0100 |
| commit | 47c6876a49595b8b162332d56670b4451b36afb4 (patch) | |
| tree | e6606ca97683e4ca0c14c62d5712fb0cc9cab9f9 /lib/psci/psci_main.c | |
| parent | 6f511c4782f079c75928a4dae3a4e3e4f6754831 (diff) | |
| download | platform_external_arm-trusted-firmware-47c6876a49595b8b162332d56670b4451b36afb4.tar.gz platform_external_arm-trusted-firmware-47c6876a49595b8b162332d56670b4451b36afb4.tar.bz2 platform_external_arm-trusted-firmware-47c6876a49595b8b162332d56670b4451b36afb4.zip | |
GIC: Ensure SGIs and PPIs are Group0 before setup
The legacy GIC driver assumes that the SGIs and PPIs are Group0 during
initialization. This is true if the driver is the first one to initialize
the GIC hardware after reset. But in some cases, earlier BL stages could
have already initialized the GIC hardware which means that SGI and PPI
configuration are not the expected reset values causing assertion failure
in `gicd_set_ipriorityr()`. This patch explicitly resets the SGI and PPI
to Group0 prior to their initialization in the driver. The same patch is
not done in the GICv2-only driver because unlike in the legacy driver,
`gicd_set_ipriorityr()` of GICv2 driver doesn't enforce this policy and
the appropriate group is set irrespective of the initial value.
Fixes ARM-software/tf-issues#396
Change-Id: I521d35caa37470ce542c796c2ba99716e4763105
Diffstat (limited to 'lib/psci/psci_main.c')
0 files changed, 0 insertions, 0 deletions