diff options
| author | Graeme Gregory <[email protected]> | 2015-03-24 14:02:43 +0000 |
|---|---|---|
| committer | Will Deacon <[email protected]> | 2015-03-25 11:49:31 +0000 |
| commit | 7c59a3df15df29c8402a05b92385e83e55355778 (patch) | |
| tree | 1e41299662d072c04f8d6d45c4d51d5a1f581de5 /tools/perf/scripts/python/bin/stackcollapse-report | |
| parent | 3505f30fb6a980283116390e9a962d60cf8e2a57 (diff) | |
ARM64 / ACPI: Get PSCI flags in FADT for PSCI init
There are two flags: PSCI_COMPLIANT and PSCI_USE_HVC. When set,
the former signals to the OS that the firmware is PSCI compliant.
The latter selects the appropriate conduit for PSCI calls by
toggling between Hypervisor Calls (HVC) and Secure Monitor Calls
(SMC).
FADT table contains such information in ACPI 5.1, FADT table was
parsed in ACPI table init and copy to struct acpi_gbl_FADT, so
use the flags in struct acpi_gbl_FADT for PSCI init.
Since ACPI 5.1 doesn't support self defined PSCI function IDs,
which means that only PSCI 0.2+ is supported in ACPI.
CC: Lorenzo Pieralisi <[email protected]>
CC: Catalin Marinas <[email protected]>
CC: Will Deacon <[email protected]>
Tested-by: Suravee Suthikulpanit <[email protected]>
Tested-by: Yijing Wang <[email protected]>
Tested-by: Mark Langsdorf <[email protected]>
Tested-by: Jon Masters <[email protected]>
Tested-by: Timur Tabi <[email protected]>
Tested-by: Robert Richter <[email protected]>
Acked-by: Robert Richter <[email protected]>
Acked-by: Olof Johansson <[email protected]>
Acked-by: Grant Likely <[email protected]>
Signed-off-by: Graeme Gregory <[email protected]>
Signed-off-by: Tomasz Nowicki <[email protected]>
Signed-off-by: Hanjun Guo <[email protected]>
Signed-off-by: Will Deacon <[email protected]>
Diffstat (limited to 'tools/perf/scripts/python/bin/stackcollapse-report')
0 files changed, 0 insertions, 0 deletions