Re: [PATCH v2 05/18] ARM64 / ACPI: Parse FADT table to get PSCI flags for PSCI init

2014-08-19 Thread Hanjun Guo
- >> a...@vger.kernel.org; linux-arm-ker...@lists.infradead.org; linux- >> ker...@vger.kernel.org; linaro-a...@lists.linaro.org >> Subject: Re: [PATCH v2 05/18] ARM64 / ACPI: Parse FADT table to get PSCI >> flags for PSCI init >> >> On 2014-8-19 19

RE: [PATCH v2 05/18] ARM64 / ACPI: Parse FADT table to get PSCI flags for PSCI init

2014-08-19 Thread Moore, Robert
Herring; Robert Richter; Zheng, Lv; Moore, Robert; Lorenzo > Pieralisi; Liviu Dudau; Randy Dunlap; Charles Garcia-Tobin; linux- > a...@vger.kernel.org; linux-arm-ker...@lists.infradead.org; linux- > ker...@vger.kernel.org; linaro-a...@lists.linaro.org > Subject: Re: [PATCH v2 05/18] ARM64

Re: [PATCH v2 05/18] ARM64 / ACPI: Parse FADT table to get PSCI flags for PSCI init

2014-08-19 Thread Hanjun Guo
On 2014-8-19 19:10, Mark Rutland wrote: @@ -47,6 +49,26 @@ void __init __acpi_unmap_table(char *map, unsigned long size) early_memunmap(map, size); } +static int __init acpi_parse_fadt(struct acpi_table_header *table) +{ + struct acpi_table_fadt *fadt

Re: [PATCH v2 05/18] ARM64 / ACPI: Parse FADT table to get PSCI flags for PSCI init

2014-08-19 Thread Mark Rutland
> >> @@ -47,6 +49,26 @@ void __init __acpi_unmap_table(char *map, unsigned long > >> size) > >>early_memunmap(map, size); > >> } > >> > >> +static int __init acpi_parse_fadt(struct acpi_table_header *table) > >> +{ > >> + struct acpi_table_fadt *fadt = (struct acpi_table_fadt *)table; > >>

Re: [PATCH v2 05/18] ARM64 / ACPI: Parse FADT table to get PSCI flags for PSCI init

2014-08-19 Thread Sudeep Holla
On 19/08/14 11:39, Hanjun Guo wrote: On 2014-8-19 2:32, Sudeep Holla wrote: On 04/08/14 16:28, Hanjun Guo wrote: There are two flags: PSCI_COMPLIANT and PSCI_USE_HVC. When set, the former signals to the OS that the hardware is PSCI compliant. The latter selects the appropriate conduit for PSC

Re: [PATCH v2 05/18] ARM64 / ACPI: Parse FADT table to get PSCI flags for PSCI init

2014-08-19 Thread Hanjun Guo
On 2014-8-19 2:32, Sudeep Holla wrote: > On 04/08/14 16:28, Hanjun Guo wrote: >> There are two flags: PSCI_COMPLIANT and PSCI_USE_HVC. When set, >> the former signals to the OS that the hardware is PSCI compliant. >> The latter selects the appropriate conduit for PSCI calls by >> toggling between H

Re: [PATCH v2 05/18] ARM64 / ACPI: Parse FADT table to get PSCI flags for PSCI init

2014-08-18 Thread Hanjun Guo
On 2014-8-18 22:27, Catalin Marinas wrote: > On Mon, Aug 04, 2014 at 04:28:12PM +0100, Hanjun Guo wrote: >> There are two flags: PSCI_COMPLIANT and PSCI_USE_HVC. When set, >> the former signals to the OS that the hardware is PSCI compliant. > > Actually it signals that the firmware is PSCI complia

Re: [PATCH v2 05/18] ARM64 / ACPI: Parse FADT table to get PSCI flags for PSCI init

2014-08-18 Thread Sudeep Holla
On 04/08/14 16:28, Hanjun Guo wrote: There are two flags: PSCI_COMPLIANT and PSCI_USE_HVC. When set, the former signals to the OS that the hardware is PSCI compliant. The latter selects the appropriate conduit for PSCI calls by toggling between Hypervisor Calls (HVC) and Secure Monitor Calls (S

[PATCH v2 05/18] ARM64 / ACPI: Parse FADT table to get PSCI flags for PSCI init

2014-08-04 Thread Hanjun Guo
There are two flags: PSCI_COMPLIANT and PSCI_USE_HVC. When set, the former signals to the OS that the hardware 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 informatio