Re: [PATCH v9 00/21] Introduce ACPI for ARM64 based on ACPI 5.1
On 2015/3/6 2:57, Olof Johansson wrote: > Hi, Hi Olof, > > On Wed, Feb 25, 2015 at 04:39:40PM +0800, Hanjun Guo wrote: >> Changes since v8: >> - remove MPIDR packing things by introducing phys_cpuid_t; >> >> - update patch acpi: fix acpi_os_ioremap for arm64 to follow >> Rafael's suggestion; >> >> - Squash patch (disable ACPI if ACPI less than 5.1) to patch >> (Get RSDP and ACPI boot-time table); >> >> - Move sleep_arm.c to arch/arm64/ and rename it as acpi_sleep.c >> >> - Rework the uefi generated empty dtb to enable acpi when no dtb >> is available, thanks Ard for the updated patch. >> >> - rework the function of register cpu for kexec case >> >> - use pr_debug() instead of pr_info() when scanning MADT. >> >> - rebase on top of 4.0-rc1 >> > I've looked at most of the arch code besides GIC and some of the timer stuff, > which I might revisit later, but the pieces I've seen seem reasonable. I've > acked individual patches. Thank you very much for the ACKs and review comments! > > There are some cleanups to be made, but that can be done incrementally on top, > it's all internal implementation details. Definitely in my TODO list :) > > I also haven't looked closely at the documentation patches yet, so I might > have > some comments on those showing up. OK, thanks. Regards Hanjun -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [PATCH v9 00/21] Introduce ACPI for ARM64 based on ACPI 5.1
Hi, On Wed, Feb 25, 2015 at 04:39:40PM +0800, Hanjun Guo wrote: > Changes since v8: > - remove MPIDR packing things by introducing phys_cpuid_t; > > - update patch acpi: fix acpi_os_ioremap for arm64 to follow > Rafael's suggestion; > > - Squash patch (disable ACPI if ACPI less than 5.1) to patch > (Get RSDP and ACPI boot-time table); > > - Move sleep_arm.c to arch/arm64/ and rename it as acpi_sleep.c > > - Rework the uefi generated empty dtb to enable acpi when no dtb > is available, thanks Ard for the updated patch. > > - rework the function of register cpu for kexec case > > - use pr_debug() instead of pr_info() when scanning MADT. > > - rebase on top of 4.0-rc1 > I've looked at most of the arch code besides GIC and some of the timer stuff, which I might revisit later, but the pieces I've seen seem reasonable. I've acked individual patches. There are some cleanups to be made, but that can be done incrementally on top, it's all internal implementation details. I also haven't looked closely at the documentation patches yet, so I might have some comments on those showing up. -Olof -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [PATCH v9 00/21] Introduce ACPI for ARM64 based on ACPI 5.1
On 2015/3/5 6:56, Rafael J. Wysocki wrote: > On Wednesday, February 25, 2015 04:39:40 PM Hanjun Guo wrote: >> Changes since v8: >> - remove MPIDR packing things by introducing phys_cpuid_t; >> >> - update patch acpi: fix acpi_os_ioremap for arm64 to follow >> Rafael's suggestion; >> >> - Squash patch (disable ACPI if ACPI less than 5.1) to patch >> (Get RSDP and ACPI boot-time table); >> >> - Move sleep_arm.c to arch/arm64/ and rename it as acpi_sleep.c >> >> - Rework the uefi generated empty dtb to enable acpi when no dtb >> is available, thanks Ard for the updated patch. >> >> - rework the function of register cpu for kexec case >> >> - use pr_debug() instead of pr_info() when scanning MADT. >> >> - rebase on top of 4.0-rc1 >> >> Thanks >> Hanjun >> >> Al Stone (4): >> ARM64 / ACPI: Get RSDP and ACPI boot-time tables >> ARM64 / ACPI: Introduce early_param "acpi=" to enable/disable ACPI >> ARM64 / ACPI: Select ACPI_REDUCED_HARDWARE_ONLY if ACPI is enabled on >> ARM64 >> ARM64 / ACPI: additions of ACPI documentation for arm64 >> >> Graeme Gregory (6): >> ACPI: add arm64 to the platforms that use ioremap >> ACPI / sleep: Introduce arm64 specific acpi_sleep.c >> ARM64 / ACPI: If we chose to boot from acpi then disable FDT >> ARM64 / ACPI: Get PSCI flags in FADT for PSCI init >> ARM64 / ACPI: Enable ARM64 in Kconfig >> Documentation: ACPI for ARM64 >> >> Hanjun Guo (8): >> ACPI / table: Use pr_debug() instead of pr_info() for MADT table >> scanning >> ACPI / processor: Introduce phys_cpuid_t for CPU hardware ID >> ARM64 / ACPI: Introduce PCI stub functions for ACPI >> ACPI / table: Print GIC information when MADT is parsed >> ARM64 / ACPI: Parse MADT for SMP initialization >> ACPI / processor: Make it possible to get CPU hardware ID via GICC >> ARM64 / ACPI: Introduce ACPI_IRQ_MODEL_GIC and register device's gsi >> clocksource / arch_timer: Parse GTDT to initialize arch timer >> >> Mark Salter (2): >> ARM64: allow late use of early_ioremap >> ACPI: fix acpi_os_ioremap for arm64 >> >> Tomasz Nowicki (1): >> irqchip: Add GICv2 specific ACPI boot support > I've ACKed or commented the ones relevant for me. As for the ARM64-specific > code, I don't think I can give any meaningful input. Hi Rafael, thank you very much for the ACKs and review comments, I will wait for other maintainers comments and then update this patch set. Regards Hanjun -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [PATCH v9 00/21] Introduce ACPI for ARM64 based on ACPI 5.1
On 02/27/2015 02:50 AM, Ard Biesheuvel wrote: Are you not seeing this on v4.0-rc1 without the patchset applied? Could the crash be inside the subsequent call to SetVirtualAddressMap() instead of inside ExitBootServices()? If so, you have a firmware bug: Mark Rutland spotted a similar bug in the AMD Seattle firmware, which has been fixed in the mean time. It has to do with the firmware dereferencing the virtual mapping as it is being installed, which violates the UEFI spec. It looks like you are right. We fixed the bug in our UEFI and now this patchset works. So all 21 patches: Tested-by: Timur Tabi However, I did notice one thing. Booting the kernel displays this line: [ 69.424001] Failed to find cpu0 device node That's because CONFIG_OF is still defined (part of "config ARM64"), and therefore cache_setup_of_node() attempts to get the cache information from the device tree. Should CONFIG_OF still be defined? -- Qualcomm Innovation Center, Inc. The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum, a Linux Foundation Collaborative Project. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [PATCH v9 00/21] Introduce ACPI for ARM64 based on ACPI 5.1
On Wednesday, February 25, 2015 04:39:40 PM Hanjun Guo wrote: > Changes since v8: > - remove MPIDR packing things by introducing phys_cpuid_t; > > - update patch acpi: fix acpi_os_ioremap for arm64 to follow > Rafael's suggestion; > > - Squash patch (disable ACPI if ACPI less than 5.1) to patch > (Get RSDP and ACPI boot-time table); > > - Move sleep_arm.c to arch/arm64/ and rename it as acpi_sleep.c > > - Rework the uefi generated empty dtb to enable acpi when no dtb > is available, thanks Ard for the updated patch. > > - rework the function of register cpu for kexec case > > - use pr_debug() instead of pr_info() when scanning MADT. > > - rebase on top of 4.0-rc1 > > Thanks > Hanjun > > Al Stone (4): > ARM64 / ACPI: Get RSDP and ACPI boot-time tables > ARM64 / ACPI: Introduce early_param "acpi=" to enable/disable ACPI > ARM64 / ACPI: Select ACPI_REDUCED_HARDWARE_ONLY if ACPI is enabled on > ARM64 > ARM64 / ACPI: additions of ACPI documentation for arm64 > > Graeme Gregory (6): > ACPI: add arm64 to the platforms that use ioremap > ACPI / sleep: Introduce arm64 specific acpi_sleep.c > ARM64 / ACPI: If we chose to boot from acpi then disable FDT > ARM64 / ACPI: Get PSCI flags in FADT for PSCI init > ARM64 / ACPI: Enable ARM64 in Kconfig > Documentation: ACPI for ARM64 > > Hanjun Guo (8): > ACPI / table: Use pr_debug() instead of pr_info() for MADT table > scanning > ACPI / processor: Introduce phys_cpuid_t for CPU hardware ID > ARM64 / ACPI: Introduce PCI stub functions for ACPI > ACPI / table: Print GIC information when MADT is parsed > ARM64 / ACPI: Parse MADT for SMP initialization > ACPI / processor: Make it possible to get CPU hardware ID via GICC > ARM64 / ACPI: Introduce ACPI_IRQ_MODEL_GIC and register device's gsi > clocksource / arch_timer: Parse GTDT to initialize arch timer > > Mark Salter (2): > ARM64: allow late use of early_ioremap > ACPI: fix acpi_os_ioremap for arm64 > > Tomasz Nowicki (1): > irqchip: Add GICv2 specific ACPI boot support I've ACKed or commented the ones relevant for me. As for the ARM64-specific code, I don't think I can give any meaningful input. -- I speak only for myself. Rafael J. Wysocki, Intel Open Source Technology Center. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [PATCH v9 00/21] Introduce ACPI for ARM64 based on ACPI 5.1
On 02/27/2015 02:50 AM, Ard Biesheuvel wrote: On 27 February 2015 at 03:20, Timur Tabi wrote: On 02/25/2015 02:39 AM, Hanjun Guo wrote: Changes since v8: I'm still debugging it, but v9 on the 4.0-rc1 kernel crashes after calling the UEFI boot time services exit function. That is, this line: status = sys_table->boottime->exit_boot_services(handle, mmap_key); in allocate_new_fdt_and_exit_boot() gets called, and then soon after it returns, the kernel crashes. It's really early because the UEFI exception handler is called. I did not have this problem with v8 patchset on 3.19. Are you not seeing this on v4.0-rc1 without the patchset applied? You're right -- I get the same crash even without the patchset applied. Could the crash be inside the subsequent call to SetVirtualAddressMap() instead of inside ExitBootServices()? It looks that way. I'm going to have to debug that. If so, you have a firmware bug: Mark Rutland spotted a similar bug in the AMD Seattle firmware, which has been fixed in the mean time. It has to do with the firmware dereferencing the virtual mapping as it is being installed, which violates the UEFI spec. Thanks. -- Qualcomm Innovation Center, Inc. The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum, a Linux Foundation Collaborative Project. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [PATCH v9 00/21] Introduce ACPI for ARM64 based on ACPI 5.1
On 2015/2/27 16:37, Hanjun Guo wrote: > Hi Timur, > > On 2015年02月27日 11:20, Timur Tabi wrote: >> On 02/25/2015 02:39 AM, Hanjun Guo wrote: >>> Changes since v8: >> >> I'm still debugging it, but v9 on the 4.0-rc1 kernel crashes after >> calling the UEFI boot time services exit function. That is, this line: >> >> status = sys_table->boottime->exit_boot_services(handle, mmap_key); >> >> in allocate_new_fdt_and_exit_boot() gets called, and then soon after it >> returns, the kernel crashes. It's really early because the UEFI >> exception handler is called. >> >> I did not have this problem with v8 patchset on 3.19. > > I tested this patch set on FVP base model with UEFI, and booted ok. > Can you boot the system without this ACPI patch set? > >> >> >> Also, you still have a couple whitespace problems in these patches: >> >> Applying: ARM64 / ACPI: additions of ACPI documentation for arm64 >> /local/mnt/workspace/linux.0/.git/rebase-apply/patch:607: new blank line >> at EOF. >> + >> /local/mnt/workspace/linux.0/.git/rebase-apply/patch:844: new blank line >> at EOF. >> + >> warning: 2 lines add whitespace errors. >> Applying: Documentation: ACPI for ARM64 >> /local/mnt/workspace/linux.0/.git/rebase-apply/patch:517: new blank line >> at EOF. >> + >> warning: 1 line adds whitespace errors. > > Weired, When I checked the patch locally there were no whitespace > problems: I found those whitespace errors too. Please see the comments in each patch. -- Thanks, Shannon -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [PATCH v9 00/21] Introduce ACPI for ARM64 based on ACPI 5.1
> > I'm still debugging it, but v9 on the 4.0-rc1 kernel crashes after calling > > the UEFI boot time services exit function. That is, this line: > > > > status = sys_table->boottime->exit_boot_services(handle, mmap_key); > > > > in allocate_new_fdt_and_exit_boot() gets called, and then soon after it > > returns, the kernel crashes. It's really early because the UEFI exception > > handler is called. > > > > I did not have this problem with v8 patchset on 3.19. > > > > Are you not seeing this on v4.0-rc1 without the patchset applied? > > Could the crash be inside the subsequent call to > SetVirtualAddressMap() instead of inside ExitBootServices()? > > If so, you have a firmware bug: Mark Rutland spotted a similar bug in > the AMD Seattle firmware, which has been fixed in the mean time. > It has to do with the firmware dereferencing the virtual mapping as it > is being installed, which violates the UEFI spec. A simple way to test is to change EFI_RT_VIRTUAL_BASE to point to the (unmapped) high half of the address space (e.g. set it to 0x). If EFI is using pointers erroneously then something should fault within SetVirtualAddressMap(), and you can catch this with your favourite debugger. Otherwise it's possible that the virtual address space chosen will cover memory and/or devices in the existing idmap, and any erroneous accesses will corrupt memory and/or cause devices to explode. Thanks, Mark -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [PATCH v9 00/21] Introduce ACPI for ARM64 based on ACPI 5.1
On 27 February 2015 at 03:20, Timur Tabi wrote: > On 02/25/2015 02:39 AM, Hanjun Guo wrote: >> >> Changes since v8: > > > I'm still debugging it, but v9 on the 4.0-rc1 kernel crashes after calling > the UEFI boot time services exit function. That is, this line: > > status = sys_table->boottime->exit_boot_services(handle, mmap_key); > > in allocate_new_fdt_and_exit_boot() gets called, and then soon after it > returns, the kernel crashes. It's really early because the UEFI exception > handler is called. > > I did not have this problem with v8 patchset on 3.19. > Are you not seeing this on v4.0-rc1 without the patchset applied? Could the crash be inside the subsequent call to SetVirtualAddressMap() instead of inside ExitBootServices()? If so, you have a firmware bug: Mark Rutland spotted a similar bug in the AMD Seattle firmware, which has been fixed in the mean time. It has to do with the firmware dereferencing the virtual mapping as it is being installed, which violates the UEFI spec. > > Also, you still have a couple whitespace problems in these patches: > > Applying: ARM64 / ACPI: additions of ACPI documentation for arm64 > /local/mnt/workspace/linux.0/.git/rebase-apply/patch:607: new blank line at > EOF. > + > /local/mnt/workspace/linux.0/.git/rebase-apply/patch:844: new blank line at > EOF. > + > warning: 2 lines add whitespace errors. > Applying: Documentation: ACPI for ARM64 > /local/mnt/workspace/linux.0/.git/rebase-apply/patch:517: new blank line at > EOF. > + > warning: 1 line adds whitespace errors. > > > -- > Sent by an employee of the Qualcomm Innovation Center, Inc. > The Qualcomm Innovation Center, Inc. is a member of the > Code Aurora Forum, hosted by The Linux Foundation. > > ___ > linux-arm-kernel mailing list > linux-arm-ker...@lists.infradead.org > http://lists.infradead.org/mailman/listinfo/linux-arm-kernel -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [PATCH v9 00/21] Introduce ACPI for ARM64 based on ACPI 5.1
Hi Timur, On 2015年02月27日 11:20, Timur Tabi wrote: On 02/25/2015 02:39 AM, Hanjun Guo wrote: Changes since v8: I'm still debugging it, but v9 on the 4.0-rc1 kernel crashes after calling the UEFI boot time services exit function. That is, this line: status = sys_table->boottime->exit_boot_services(handle, mmap_key); in allocate_new_fdt_and_exit_boot() gets called, and then soon after it returns, the kernel crashes. It's really early because the UEFI exception handler is called. I did not have this problem with v8 patchset on 3.19. I tested this patch set on FVP base model with UEFI, and booted ok. Can you boot the system without this ACPI patch set? Also, you still have a couple whitespace problems in these patches: Applying: ARM64 / ACPI: additions of ACPI documentation for arm64 /local/mnt/workspace/linux.0/.git/rebase-apply/patch:607: new blank line at EOF. + /local/mnt/workspace/linux.0/.git/rebase-apply/patch:844: new blank line at EOF. + warning: 2 lines add whitespace errors. Applying: Documentation: ACPI for ARM64 /local/mnt/workspace/linux.0/.git/rebase-apply/patch:517: new blank line at EOF. + warning: 1 line adds whitespace errors. Weired, When I checked the patch locally there were no whitespace problems: ./scripts/checkpatch.pl 0020-Documentation-ACPI-for-ARM64.patch WARNING: added, moved or deleted file(s), does MAINTAINERS need updating? #23: new file mode 100644 WARNING: use relative pathname instead of absolute in changelog text #25: --- /dev/null total: 0 errors, 2 warnings, 506 lines checked 0020-Documentation-ACPI-for-ARM64.patch has style problems, please review. ./scripts/checkpatch.pl 0021-ARM64-ACPI-additions-of-ACPI-documentation-for-arm64.patch WARNING: added, moved or deleted file(s), does MAINTAINERS need updating? #32: new file mode 100644 WARNING: use relative pathname instead of absolute in changelog text #34: --- /dev/null WARNING: use relative pathname instead of absolute in changelog text #634: --- /dev/null total: 0 errors, 3 warnings, 825 lines checked 0021-ARM64-ACPI-additions-of-ACPI-documentation-for-arm64.patch has style problems, please review. Can you provide me the exact line of code which have whitespace problems? Thanks Hanjun -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [PATCH v9 00/21] Introduce ACPI for ARM64 based on ACPI 5.1
On 02/25/2015 02:39 AM, Hanjun Guo wrote: Changes since v8: I'm still debugging it, but v9 on the 4.0-rc1 kernel crashes after calling the UEFI boot time services exit function. That is, this line: status = sys_table->boottime->exit_boot_services(handle, mmap_key); in allocate_new_fdt_and_exit_boot() gets called, and then soon after it returns, the kernel crashes. It's really early because the UEFI exception handler is called. I did not have this problem with v8 patchset on 3.19. Also, you still have a couple whitespace problems in these patches: Applying: ARM64 / ACPI: additions of ACPI documentation for arm64 /local/mnt/workspace/linux.0/.git/rebase-apply/patch:607: new blank line at EOF. + /local/mnt/workspace/linux.0/.git/rebase-apply/patch:844: new blank line at EOF. + warning: 2 lines add whitespace errors. Applying: Documentation: ACPI for ARM64 /local/mnt/workspace/linux.0/.git/rebase-apply/patch:517: new blank line at EOF. + warning: 1 line adds whitespace errors. -- Sent by an employee of the Qualcomm Innovation Center, Inc. The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum, hosted by The Linux Foundation. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
[PATCH v9 00/21] Introduce ACPI for ARM64 based on ACPI 5.1
Changes since v8: - remove MPIDR packing things by introducing phys_cpuid_t; - update patch acpi: fix acpi_os_ioremap for arm64 to follow Rafael's suggestion; - Squash patch (disable ACPI if ACPI less than 5.1) to patch (Get RSDP and ACPI boot-time table); - Move sleep_arm.c to arch/arm64/ and rename it as acpi_sleep.c - Rework the uefi generated empty dtb to enable acpi when no dtb is available, thanks Ard for the updated patch. - rework the function of register cpu for kexec case - use pr_debug() instead of pr_info() when scanning MADT. - rebase on top of 4.0-rc1 Thanks Hanjun Al Stone (4): ARM64 / ACPI: Get RSDP and ACPI boot-time tables ARM64 / ACPI: Introduce early_param "acpi=" to enable/disable ACPI ARM64 / ACPI: Select ACPI_REDUCED_HARDWARE_ONLY if ACPI is enabled on ARM64 ARM64 / ACPI: additions of ACPI documentation for arm64 Graeme Gregory (6): ACPI: add arm64 to the platforms that use ioremap ACPI / sleep: Introduce arm64 specific acpi_sleep.c ARM64 / ACPI: If we chose to boot from acpi then disable FDT ARM64 / ACPI: Get PSCI flags in FADT for PSCI init ARM64 / ACPI: Enable ARM64 in Kconfig Documentation: ACPI for ARM64 Hanjun Guo (8): ACPI / table: Use pr_debug() instead of pr_info() for MADT table scanning ACPI / processor: Introduce phys_cpuid_t for CPU hardware ID ARM64 / ACPI: Introduce PCI stub functions for ACPI ACPI / table: Print GIC information when MADT is parsed ARM64 / ACPI: Parse MADT for SMP initialization ACPI / processor: Make it possible to get CPU hardware ID via GICC ARM64 / ACPI: Introduce ACPI_IRQ_MODEL_GIC and register device's gsi clocksource / arch_timer: Parse GTDT to initialize arch timer Mark Salter (2): ARM64: allow late use of early_ioremap ACPI: fix acpi_os_ioremap for arm64 Tomasz Nowicki (1): irqchip: Add GICv2 specific ACPI boot support Documentation/arm64/acpi_object_usage.txt | 594 ++ Documentation/arm64/arm-acpi.txt | 506 + Documentation/arm64/why_use_acpi.txt | 231 Documentation/kernel-parameters.txt | 3 +- arch/arm64/Kconfig| 3 + arch/arm64/include/asm/acenv.h| 18 + arch/arm64/include/asm/acpi.h | 96 + arch/arm64/include/asm/cpu_ops.h | 1 + arch/arm64/include/asm/fixmap.h | 3 + arch/arm64/include/asm/pci.h | 6 + arch/arm64/include/asm/psci.h | 3 +- arch/arm64/include/asm/smp.h | 5 +- arch/arm64/kernel/Makefile| 1 + arch/arm64/kernel/acpi.c | 386 +++ arch/arm64/kernel/acpi_sleep.c| 28 ++ arch/arm64/kernel/cpu_ops.c | 2 +- arch/arm64/kernel/pci.c | 25 ++ arch/arm64/kernel/psci.c | 78 ++-- arch/arm64/kernel/setup.c | 21 +- arch/arm64/kernel/smp.c | 2 +- arch/arm64/kernel/time.c | 7 + arch/ia64/include/asm/acpi.h | 4 + arch/ia64/kernel/acpi.c | 2 +- arch/x86/include/asm/acpi.h | 4 + arch/x86/kernel/acpi/boot.c | 2 +- drivers/acpi/Kconfig | 3 +- drivers/acpi/Makefile | 2 + drivers/acpi/acpi_processor.c | 7 +- drivers/acpi/bus.c| 3 + drivers/acpi/osl.c| 6 +- drivers/acpi/processor_core.c | 60 ++- drivers/acpi/tables.c | 52 ++- drivers/clocksource/arm_arch_timer.c | 132 +-- drivers/irqchip/irq-gic.c | 102 + drivers/irqchip/irqchip.c | 3 + include/acpi/acpi_io.h| 4 + include/acpi/processor.h | 6 +- include/linux/acpi.h | 17 +- include/linux/clocksource.h | 6 + include/linux/irqchip/arm-gic-acpi.h | 29 ++ 40 files changed, 2359 insertions(+), 104 deletions(-) create mode 100644 Documentation/arm64/acpi_object_usage.txt create mode 100644 Documentation/arm64/arm-acpi.txt create mode 100644 Documentation/arm64/why_use_acpi.txt create mode 100644 arch/arm64/include/asm/acenv.h create mode 100644 arch/arm64/include/asm/acpi.h create mode 100644 arch/arm64/kernel/acpi.c create mode 100644 arch/arm64/kernel/acpi_sleep.c create mode 100644 include/linux/irqchip/arm-gic-acpi.h -- 1.9.1 -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
