- Linaro-acpi - lists.linaro.org

[PATCH v14 0/4] Watchdog: introduce ARM SBSA watchdog driver

by fu.wei＠linaro.org

From: Fu Wei <fu.wei(a)linaro.org> This patchset: (1)Introduce Documentation/devicetree/bindings/watchdog/sbsa-gwdt.txt for FDT info of SBSA Generic Watchdog, and give two examples of adding SBSA Generic Watchdog device node into the dts files: foundation-v8.dts and amd-seattle-soc.dtsi. (2)Introduce ARM SBSA watchdog driver: a.Use linux kernel watchdog framework; b.Work with FDT on ARM64; c.Support getting timeout from parameter and FDT at the driver init stage. d.The driver works in two modes: (1) single stage timeout (ignore WS0 interrupt) (2) two stages timeout (register WS0 interrupt, do panic in routine) e.User can config working mode by module parameter "action". This patchset has been tested with watchdog daemon (ACPI/FDT, module/build-in) on the following platforms: (1)ARM Foundation v8 model (2)AMD Seattle platform This patchset has been tested with kdump successfully. Changelog: v14:Fix a bug of registering interrupt routine: do a ping before registering interrupt routine, in case where is a pending interrupt. Reorder the initialization code to postpone registering interrupt routine. Improve some code style: (1)add some macro of string (2)use watchdog_get_drvdata instead of to_sbsa_gwdt, delete to_sbsa_gwdt. v13:https://lkml.org/lkml/2016/2/16/713 Fix a dev_warn message typo"signle"-->"single" Add MODULE_ALIAS Add more *ed-by in commit message. v12:https://lkml.org/lkml/2016/2/16/154 Fix a dev_warn message typo"fall"--"falling" Remove unnecessary "status" in dts Add more *ed-by in commit message. v11:https://lkml.org/lkml/2016/2/9/577 Merge patch 4 and 5. Improve some comments. The driver works in two modes, it's configured by "action"(instead of panic_enabled). Improve the initialization of the timeout limits. Feeding dog by writing "0" to WRR. v10:https://lkml.org/lkml/2016/2/3/817 Delete pretimeout support. Separate the driver to two parts: (1) single stage timeout driver(ignore WS0 interrupt); (2) register WS0 interrupt for the half timeout panic. timeout == (enable --> WS1). v9: https://lkml.org/lkml/2015/11/9/57 Rebase to latest kernel version(4.3). Update the Documentation of sbsa-gwdt device node info of FDT: (1) move some introduction to pretimeout patch (2) delete WS1 value from "interrupts" of binding documentation, since WS1 won't be handled by Linux. v8: https://lkml.org/lkml/2015/10/27/466 Rebase to latest kernel version(4.3-rc7). Separate the patches of GTDT support and arm_arch_timer. This clocksource relevant patch will upstreamed in a individual patchset. Update all the default timeout and pretimeout to 30s and 60s. Improve documentation and inline comments. Fix a bug in pretimeout support which makes timeout and pretimeout parameters initialization fail. v7: https://lkml.org/lkml/2015/8/24/611 Rebase to latest kernel version(4.2-rc7). Improve FDT support: geting resource by order, instead of name. According to the FDT support, Update the example dts file, gtdt.c and sbsa_gwdt.c. Pass the sparse test, and fix the warning. Fix the max_pretimeout and max_timeout value overflow bug. Delete the WCV output value. v6: https://lkml.org/lkml/2015/6/23/359 Improve the dtb example files: reduce the register frame size to 4K. Improve pretimeout support: (1) improve watchdog_init_timeouts function (2) rename watchdog_check_min_max_timeouts back to the original name (1) improve watchdog_timeout_invalid/watchdog_pretimeout_invalid Add the new features in the sbsa_gwdt driver: (1) In the second stage, user can feed the dog without cleaning WS0. (2) In the second stage, user can trigger WS1 by setting pretimeout = 0. (3) expand the max value of pretimeout, in case 10 second is not enough for a kdump kernel reboot in panic. v5: https://lkml.org/lkml/2015/6/10/357 Improve pretimeout support: (1)fix typo in documentation and comments. (2)fix the timeout limits validation bug. Simplify sbsa_gwdt driver: (1)integrate all the registers access functions into caller. v4: https://lkml.org/lkml/2015/6/2/4 Refactor GTDT support code: remove it from arch/arm64/kernel/acpi.c, put it into drivers/acpi/gtdt.c file. Integrate the GTDT code of drivers/clocksource/arm_arch_timer.c into drivers/acpi/gtdt.c. Improve pretimeout support, fix "pretimeout == 0" problem. Simplify sbsa_gwdt driver: (1)timeout/pretimeout limits setup; (2)keepalive function; (3)delete "clk == 0" check; (4)delete WS0 status bit check in interrupt routine; (5)sbsa_gwdt_set_wcv function. v3: https://lkml.org/lkml/2015/5/25/111 Delete "export arch_timer_get_rate" patch. Driver back to use arch_timer_get_cntfrq. Improve watchdog_init_timeouts function and update relevant documentation. Improve watchdog_timeout_invalid and watchdog_pretimeout_invalid. Improve foundation-v8.dts: delete the unnecessary tag of device node. Remove "ARM64 || COMPILE_TEST" from Kconfig. Add comments in arch/arm64/kernel/acpi.c Fix typoes and incorrect comments. v2: https://lkml.org/lkml/2015/5/21/172 Improve watchdog-kernel-api.txt documentation for pretimeout support. Export "arch_timer_get_rate" in arm_arch_timer.c. Add watchdog_init_timeouts API for pretimeout support in framework. Improve suspend and resume foundation in driver Improve timeout/pretimeout values init code in driver. Delete unnecessary items of the sbsa_gwdt struct and #define. Delete all unnecessary debug info in driver. Fix 64bit division bug. Use the arch_timer interface to get watchdog clock rate. Add MODULE_DEVICE_TABLE for platform device id. Fix typoes. v1: https://lkml.org/lkml/2015/5/15/279 The first version upstream patchset to linux mailing list. Fu Wei (4): Documentation: add sbsa-gwdt driver documentation ARM64: add SBSA Generic Watchdog device node in foundation-v8.dts ARM64: add SBSA Generic Watchdog device node in amd-seattle-soc.dtsi Watchdog: introduce ARM SBSA watchdog driver .../devicetree/bindings/watchdog/sbsa-gwdt.txt | 31 ++ Documentation/watchdog/watchdog-parameters.txt | 7 + arch/arm64/boot/dts/amd/amd-seattle-soc.dtsi | 8 + arch/arm64/boot/dts/arm/foundation-v8.dts | 7 + drivers/watchdog/Kconfig | 20 + drivers/watchdog/Makefile | 1 + drivers/watchdog/sbsa_gwdt.c | 408 +++++++++++++++++++++ 7 files changed, 482 insertions(+) create mode 100644 Documentation/devicetree/bindings/watchdog/sbsa-gwdt.txt create mode 100644 drivers/watchdog/sbsa_gwdt.c -- 2.5.0

9 years, 1 month

5
10
0 0

leg-kernel tag leg-20160328.0 released

by Graeme Gregory

The leg-kernel release has been made and tagged as leg-20160328.0 This is based on mainline kernel v4.6-rc1 Repository : http://git.linaro.org/leg/acpi/leg-kernel.git Direct Link: http://git.linaro.org/leg/acpi/leg-kernel.git/commit/d5c925dfbf42d7cd6e2282… Topic Branches :- http://git.linaro.org/leg/acpi/acpi.git - topic-pci [topic-pci-20160328.0] - topic-acpi-console [topic-acpi-console-20160328.0] - topic-gtdt-wakeup-timer [topic-gtdt-wakeup-timer-20160328.0] - topic-fvp [topic-fvp-20160328.0] - topic-kvm-acpi [topic-kvm-acpi-20160328.0] - topic-apei [topic-apei-20160328.0] http://git.linaro.org/leg/acpi/leg-kernel.git - leg-configs [leg-configs-20160216.0] NOTES:-

9 years, 1 month

1
0
0 0

[PATCH v7] acpi, apei, arm64: APEI initial support for aarch64.

by fu.wei＠linaro.org

From: Tomasz Nowicki <tomasz.nowicki(a)linaro.org> This commit provides APEI arch-specific bits for aarch64 Meanwhile, (1)add a new subfunction "hest_ia32_init" for "acpi_disable_cmcff" which is used by IA-32 Architecture Corrected Machine Check (CMC). (2)move HEST type (ACPI_HEST_TYPE_IA32_CORRECTED_CHECK) checking to a generic place. Signed-off-by: Tomasz Nowicki <tomasz.nowicki(a)linaro.org> Tested-by: Jonathan (Zhixiong) Zhang <zjzhang(a)codeaurora.org> Signed-off-by: Fu Wei <fu.wei(a)linaro.org> Acked-by: Hanjun Guo <hanjun.guo(a)linaro.org> Tested-by: Tyler Baicar <tbaicar(a)codeaurora.org> --- Changelog: v7: Add comment for arch_apei_flush_tlb_one in arch/arm64/include/asm/acpi.h v6: https://lists.linaro.org/pipermail/linaro-acpi/2016-March/006644.html Move HEST type (ACPI_HEST_TYPE_IA32_CORRECTED_CHECK) checking to a generic place. Delete HAVE_ACPI_APEI_HEST_IA32. v5: https://lkml.org/lkml/2015/12/10/131 Add "HAVE_ACPI_APEI_HEST_IA32" instead of "#if defined(__i386__) || defined(__x86_64__)". v4: https://lkml.org/lkml/2015/12/8/188 Rebase to latest kernel version(4.4-rc4). Move arch_apei_flush_tlb_one into header file as a inline function Add a new subfunction "hest_ia_init" for "acpi_disable_cmcff". v3: https://lkml.org/lkml/2015/12/3/521 Remove "acpi_disable_cmcff" from arm64 code, and wrap it in hest.c by "#if defined(__i386__) || defined(__x86_64__)" v2: https://lkml.org/lkml/2015/12/2/432 Rebase to latest kernel version(4.4-rc3). Move arch_apei_flush_tlb_one() to arch/arm64/kernel/acpi.c v1: https://lkml.org/lkml/2015/8/14/199 Move arch_apei_flush_tlb_one() to arch/arm64/include/asm/apci.h. Delete arch/arm64/kernel/apei.c. Add "#ifdef CONFIG_ACPI_APEI" for "acpi_disable_cmcff". arch/arm64/Kconfig | 1 + arch/arm64/include/asm/acpi.h | 15 ++++++++++++++- arch/x86/kernel/acpi/apei.c | 3 --- drivers/acpi/apei/hest.c | 18 +++++++++++++++--- 4 files changed, 30 insertions(+), 7 deletions(-) diff --git a/arch/arm64/Kconfig b/arch/arm64/Kconfig index b3f2522..0260b4c 100644 --- a/arch/arm64/Kconfig +++ b/arch/arm64/Kconfig @@ -3,6 +3,7 @@ config ARM64 select ACPI_CCA_REQUIRED if ACPI select ACPI_GENERIC_GSI if ACPI select ACPI_REDUCED_HARDWARE_ONLY if ACPI + select HAVE_ACPI_APEI if ACPI select ARCH_HAS_DEVMEM_IS_ALLOWED select ARCH_HAS_ATOMIC64_DEC_IF_POSITIVE select ARCH_HAS_ELF_RANDOMIZE diff --git a/arch/arm64/include/asm/acpi.h b/arch/arm64/include/asm/acpi.h index caafd63..077a87d 100644 --- a/arch/arm64/include/asm/acpi.h +++ b/arch/arm64/include/asm/acpi.h @@ -17,6 +17,7 @@ #include <asm/cputype.h> #include <asm/smp_plat.h> +#include <asm/tlbflush.h> /* Macros for consistency checks of the GICC subtable of MADT */ #define ACPI_MADT_GICC_LENGTH \ @@ -93,7 +94,19 @@ static inline const char *acpi_get_enable_method(int cpu) } #ifdef CONFIG_ACPI_APEI +#define acpi_disable_cmcff 1 pgprot_t arch_apei_get_mem_attribute(phys_addr_t addr); -#endif +/* + * This inline function is used in IRQ context (by GHES driver now), + * see ghes_iounmap_irq and ghes_iounmap_nmi in drivers/acpi/apei/ghes.c. + * The page mapped is reserved for firmware in kernel. This invalidate TLB + * maintenance should be broadcasted safely to make sure that all the cores + * will do TLB invalidation, then get the right pages. + */ +static inline void arch_apei_flush_tlb_one(unsigned long addr) +{ + flush_tlb_kernel_range(addr, addr + PAGE_SIZE); +} +#endif /* CONFIG_ACPI_APEI */ #endif /*_ASM_ACPI_H*/ diff --git a/arch/x86/kernel/acpi/apei.c b/arch/x86/kernel/acpi/apei.c index c280df6..ea3046e 100644 --- a/arch/x86/kernel/acpi/apei.c +++ b/arch/x86/kernel/acpi/apei.c @@ -24,9 +24,6 @@ int arch_apei_enable_cmcff(struct acpi_hest_header *hest_hdr, void *data) struct acpi_hest_ia_corrected *cmc; struct acpi_hest_ia_error_bank *mc_bank; - if (hest_hdr->type != ACPI_HEST_TYPE_IA32_CORRECTED_CHECK) - return 0; - cmc = (struct acpi_hest_ia_corrected *)hest_hdr; if (!cmc->enabled) return 0; diff --git a/drivers/acpi/apei/hest.c b/drivers/acpi/apei/hest.c index 20b3fcf..792a0d9 100644 --- a/drivers/acpi/apei/hest.c +++ b/drivers/acpi/apei/hest.c @@ -123,7 +123,18 @@ EXPORT_SYMBOL_GPL(apei_hest_parse); */ static int __init hest_parse_cmc(struct acpi_hest_header *hest_hdr, void *data) { - return arch_apei_enable_cmcff(hest_hdr, data); + if (hest_hdr->type != ACPI_HEST_TYPE_IA32_CORRECTED_CHECK) + return 0; + + if (!acpi_disable_cmcff) + return !arch_apei_enable_cmcff(hest_hdr, data); + + return 0; +} + +static inline int __init hest_ia32_init(void) +{ + return apei_hest_parse(hest_parse_cmc, NULL); } struct ghes_arr { @@ -232,8 +243,9 @@ void __init acpi_hest_init(void) goto err; } - if (!acpi_disable_cmcff) - apei_hest_parse(hest_parse_cmc, NULL); + rc = hest_ia32_init(); + if (rc) + goto err; if (!ghes_disable) { rc = apei_hest_parse(hest_parse_ghes_count, &ghes_count); -- 2.5.0

9 years, 1 month

2
1
0 0

[RESEND PATCH v2] ARM64: ACPI: Update documentation for latest specification version

by Al Stone

The ACPI 6.1 specification was recently released at the end of January 2016, but the arm64 kernel documentation for the use of ACPI was written for the 5.1 version of the spec. There were significant additions to the spec that had not yet been mentioned -- for example, the 6.0 mechanisms added to make it easier to define processors and low power idle states, as well as the 6.1 addition allowing regular interrupts (not just from GPIO) be used to signal ACPI general purpose events. This patch reflects going back through and examining the specs in detail and updating content appropriately. Whilst there, a few odds and ends of typos were caught as well. This brings the documentation up to date with ACPI 6.1 for arm64. RESEND: -- Corrected From: header and added missing Cc's Changes for v2: -- Clean up white space (Harb Abdulhahmid) -- Clarification on _CCA usage (Harb Abdulhamid) -- IORT moved to required from recommended (Hanjun Guo) -- Clarify IORT description (Hanjun Guo) Signed-off-by: Al Stone <al.stone(a)linaro.org> Cc: Catalin Marinas <catalin.marinas(a)arm.com> Cc: Will Deacon <will.deacon(a)arm.com> Cc: Jonathan Corbet <corbet(a)lwn.net> --- Documentation/arm64/acpi_object_usage.txt | 445 ++++++++++++++++++++++-------- Documentation/arm64/arm-acpi.txt | 28 +- 2 files changed, 356 insertions(+), 117 deletions(-) diff --git a/Documentation/arm64/acpi_object_usage.txt b/Documentation/arm64/acpi_object_usage.txt index a6e1a18..29bc1a1 100644 --- a/Documentation/arm64/acpi_object_usage.txt +++ b/Documentation/arm64/acpi_object_usage.txt @@ -11,15 +11,16 @@ outside of the UEFI Forum (see Section 5.2.6 of the specification). For ACPI on arm64, tables also fall into the following categories: - -- Required: DSDT, FADT, GTDT, MADT, MCFG, RSDP, SPCR, XSDT + -- Required: DSDT, FADT, GTDT, IORT, MADT, MCFG, RSDP, SPCR, XSDT - -- Recommended: BERT, EINJ, ERST, HEST, SSDT + -- Recommended: BERT, EINJ, ERST, HEST, PCCT, SSDT - -- Optional: BGRT, CPEP, CSRT, DRTM, ECDT, FACS, FPDT, MCHI, MPST, - MSCT, RASF, SBST, SLIT, SPMI, SRAT, TCPA, TPM2, UEFI + -- Optional: BGRT, CPEP, CSRT, DBG2, DRTM, ECDT, FACS, FPDT, MCHI, + MPST, MSCT, NFIT, PMTT, RASF, SBST, SLIT, SPMI, SRAT, STAO, TCPA, + TPM2, UEFI, XENV - -- Not supported: BOOT, DBG2, DBGP, DMAR, ETDT, HPET, IBFT, IVRS, - LPIT, MSDM, RSDT, SLIC, WAET, WDAT, WDRT, WPBT + -- Not supported: BOOT, DBGP, DMAR, ETDT, HPET, IBFT, IVRS, LPIT, + MSDM, OEMx, PSDT, RSDT, SLIC, WAET, WDAT, WDRT, WPBT Table Usage for ARMv8 Linux @@ -50,7 +51,8 @@ CSRT Signature Reserved (signature == "CSRT") DBG2 Signature Reserved (signature == "DBG2") == DeBuG port table 2 == - Microsoft only table, will not be supported. + License has changed and should be usable. Optional if used instead + of earlycon=<device> on the command line. DBGP Signature Reserved (signature == "DBGP") == DeBuG Port table == @@ -133,10 +135,11 @@ GTDT Section 5.2.24 (signature == "GTDT") HEST Section 18.3.2 (signature == "HEST") == Hardware Error Source Table == - Until further error source types are defined, use only types 6 (AER - Root Port), 7 (AER Endpoint), 8 (AER Bridge), or 9 (Generic Hardware - Error Source). Firmware first error handling is possible if and only - if Trusted Firmware is being used on arm64. + ARM-specific error sources have been defined; please use those or the + PCI types such as type 6 (AER Root Port), 7 (AER Endpoint), or 8 (AER + Bridge), or use type 9 (Generic Hardware Error Source). Firmware first + error handling is possible if and only if Trusted Firmware is being + used on arm64. Must be supplied if RAS support is provided by the platform. It is recommended this table be supplied. @@ -149,20 +152,27 @@ IBFT Signature Reserved (signature == "IBFT") == iSCSI Boot Firmware Table == Microsoft defined table, support TBD. +IORT Signature Reserved (signature == "IORT") + == Input Output Remapping Table == + arm64 only table, required in order to describe IO topology, SMMUs, + and GIC ITSs, and how those various components are connected together, + such as identifying which components are behind which SMMUs/ITSs. + IVRS Signature Reserved (signature == "IVRS") == I/O Virtualization Reporting Structure == x86_64 (AMD) only table, will not be supported. LPIT Signature Reserved (signature == "LPIT") == Low Power Idle Table == - x86 only table as of ACPI 5.1; future versions have been adapted for - use with ARM and will be recommended in order to support ACPI power - management. + x86 only table as of ACPI 5.1; starting with ACPI 6.0, processor + descriptions and power states on ARM platforms should use the DSDT + and define processor container devices (_HID ACPI0010, Section 8.4, + and more specifically 8.4.3 and and 8.4.4). MADT Section 5.2.12 (signature == "APIC") == Multiple APIC Description Table == Required for arm64. Only the GIC interrupt controller structures - should be used (types 0xA - 0xE). + should be used (types 0xA - 0xF). MCFG Signature Reserved (signature == "MCFG") == Memory-mapped ConFiGuration space == @@ -176,14 +186,38 @@ MPST Section 5.2.21 (signature == "MPST") == Memory Power State Table == Optional, not currently supported. +MSCT Section 5.2.19 (signature == "MSCT") + == Maximum System Characteristic Table == + Optional, not currently supported. + MSDM Signature Reserved (signature == "MSDM") == Microsoft Data Management table == Microsoft only table, will not be supported. -MSCT Section 5.2.19 (signature == "MSCT") - == Maximum System Characteristic Table == +NFIT Section 5.2.25 (signature == "NFIT") + == NVDIMM Firmware Interface Table == Optional, not currently supported. +OEMx Signature of "OEMx" only + == OEM Specific Tables == + All tables starting with a signature of "OEM" are reserved for OEM + use. Since these are not meant to be of general use but are limited + to very specific end users, they are not recommended for use and are + not supported by the kernel for arm64. + +PCCT Section 14.1 (signature == "PCCT) + == Platform Communications Channel Table == + Recommend for use on arm64, and required when using CPPC to control + power on the platform. + +PMTT Section 5.2.21.12 (signature == "PMTT") + == Platform Memory Topology Table == + Optional, but useful, but not currently supported. + +PSDT Section 5.2.11.3 (signature == "PSDT") + == Persistent System Description Table == + Obsolete table, will not be supported. + RASF Section 5.2.20 (signature == "RASF") == RAS Feature table == Optional, not currently supported. @@ -195,7 +229,7 @@ RSDP Section 5.2.5 (signature == "RSD PTR") RSDT Section 5.2.7 (signature == "RSDT") == Root System Description Table == Since this table can only provide 32-bit addresses, it is deprecated - on arm64, and will not be used. + on arm64, and will not be used. If provided, it will be ignored. SBST Section 5.2.14 (signature == "SBST") == Smart Battery Subsystem Table == @@ -207,7 +241,7 @@ SLIC Signature Reserved (signature == "SLIC") SLIT Section 5.2.17 (signature == "SLIT") == System Locality distance Information Table == - Optional in general, but required for NUMA systems. + Optional in general, but required for arm64 NUMA systems. SPCR Signature Reserved (signature == "SPCR") == Serial Port Console Redirection table == @@ -220,7 +254,7 @@ SPMI Signature Reserved (signature == "SPMI") SRAT Section 5.2.16 (signature == "SRAT") == System Resource Affinity Table == Optional, but if used, only the GICC Affinity structures are read. - To support NUMA, this table is required. + To support arm64 NUMA, this table is required. SSDT Section 5.2.11.2 (signature == "SSDT") == Secondary System Description Table == @@ -235,6 +269,11 @@ SSDT Section 5.2.11.2 (signature == "SSDT") These tables are optional, however. ACPI tables should contain only one DSDT but can contain many SSDTs. +STAO Signature Reserved (signature == "STAO") + == _STA Override table == + Optional, but only necessary in virtualized environments in order to + hide devices from guest OSs. + TCPA Signature Reserved (signature == "TCPA") == Trusted Computing Platform Alliance table == Optional, not currently supported, and may need changes to fully @@ -266,6 +305,10 @@ WPBT Signature Reserved (signature == "WPBT") == Windows Platform Binary Table == Microsoft only table, will not be supported. +XENV Signature Reserved (signature == "XENV") + == Xen project table == + Optional, used only by Xen at present. + XSDT Section 5.2.8 (signature == "XSDT") == eXtended System Description Table == Required for arm64. @@ -273,31 +316,57 @@ XSDT Section 5.2.8 (signature == "XSDT") ACPI Objects ------------ -The expectations on individual ACPI objects are discussed in the list that -follows: +The expectations on individual ACPI objects that are likely to be used are +shown in the list that follows: Name Section Usage for ARMv8 Linux ---- ------------ ------------------------------------------------- +_ACx 11.4.1 Use as needed. + _ADR 6.1.1 Use as needed. +_ALx 11.4.2 Use as needed. + +_ART 11.4.3 Use as needed. + _BBN 6.5.5 Use as needed; PCI-specific. -_BDN 6.5.3 Optional; not likely to be used on arm64. +_CCA 6.2.17 This method must be defined for all bus masters + on arm64 -- there are no assumptions made about + whether such devices are cache coherent or not. + The _CCA value is inherited by all descendants of + these devices so it does not need to be repeated. + Without _CCA on arm64, the kernel does not know what + to do about setting up DMA for the device. -_CCA 6.2.17 This method should be defined for all bus masters - on arm64. While cache coherency is assumed, making - it explicit ensures the kernel will set up DMA as - it should. + NB: this method provides default cache coherency + attributes; the presence of an SMMU can be used to + modify that, however. For example, a master could + default to non-coherent, but be made coherent with + the appropriate SMMU configuration (see Table 17 of + the IORT specification, ARM Document DEN 0049B). -_CDM 6.2.1 Optional, to be used only for processor devices. +_CDM 6.2.1 Use as needed, to be used only for processor devices. -_CID 6.1.2 Use as needed. +_CID 6.1.2 Use as needed, see also _HID. -_CLS 6.1.3 Use as needed. +_CLS 6.1.3 Use as needed, see also _HID. + +_CPC 8.4.7.1 Use as needed; power management specific. CPPC is + recommended on arm64. + +_CR3 11.4.5 Use as needed. _CRS 6.2.2 Required on arm64. -_DCK 6.5.2 Optional; not likely to be used on arm64. +_CRT 11.4.4 Use as needed. + +_CSD 8.4.2.2 Use as needed, used only in conjuction with _CST. + +_CST 8.4.2.1 Low power idle states (8.4.4) are recommended instead + of C-states. + +_CWS 9.18.6 Use as needed. _DDN 6.1.4 This field can be used for a device name. However, it is meant for DOS device names (e.g., COM1), so be @@ -305,11 +374,11 @@ _DDN 6.1.4 This field can be used for a device name. However, _DEP 6.5.8 Use as needed. -_DIS 6.2.3 Optional, for power management use. +_DIS 6.2.3 Use as needed, for power management use. -_DLM 5.7.5 Optional. +_DLM 5.7.5 Use as needed. -_DMA 6.2.4 Optional. +_DMA 6.2.4 Use as needed. _DSD 6.2.5 To be used with caution. If this object is used, try to use it within the constraints already defined by the @@ -325,19 +394,29 @@ _DSD 6.2.5 To be used with caution. If this object is used, try with the UEFI Forum; this may cause some iteration as more than one OS will be registering entries. -_DSM Do not use this method. It is not standardized, the +_DSM 9.1.1 Do not use this method. It is not standardized, the return values are not well documented, and it is currently a frequent source of error. -_DSW 7.2.1 Use as needed; power management specific. +_DSW 7.3.1 Use as needed; power management specific. -_EDL 6.3.1 Optional. +_DTI 11.4.6 Use as needed. -_EJD 6.3.2 Optional. +_EDL 6.3.1 Use as needed. -_EJx 6.3.3 Optional. +_EJD 6.3.2 Use as needed. -_FIX 6.2.7 x86 specific, not used on arm64. +_EJx 6.3.3 Use as needed. + +_FIF 11.3.1.1 Use as needed. + +_FPS 11.3.1.2 Use as needed. + +_FSL 11.3.1.3 Use as needed. + +_FST 11.3.1.4 Use as needed. + +_GCP 9.18.2 Use as needed. \_GL 5.7.1 This object is not to be used in hardware reduced mode, and therefore should not be used on arm64. @@ -349,35 +428,57 @@ _GLK 6.5.7 This object requires a global lock be defined; there \_GPE 5.3.1 This namespace is for x86 use only. Do not use it on arm64. -_GSB 6.2.7 Optional. +_GRT 9.18.3 Use as needed. + +_GSB 6.2.7 Use as needed. + +_GTF 9.9.1.1 Use as needed. + +_GWS 9.18.5 Use as needed. _HID 6.1.5 Use as needed. This is the primary object to use in device probing, though _CID and _CLS may also be used. -_HPP 6.2.8 Optional, PCI specific. +_HOT 11.4.7 Use as needed. + +_HPP 6.2.8 Use as needed, PCI specific. -_HPX 6.2.9 Optional, PCI specific. +_HPX 6.2.9 Use as needed, PCI specific. -_HRV 6.1.6 Optional, use as needed to clarify device behavior; in - some cases, this may be easier to use than _DSD. +_HRV 6.1.6 Use as needed, use as needed to clarify device + behavior; in some cases, this may be easier to use + than _DSD. _INI 6.5.1 Not required, but can be useful in setting up devices when UEFI leaves them in a state that may not be what the driver expects before it starts probing. -_IRC 7.2.15 Use as needed; power management specific. +_IRC 7.3.15 Use as needed; power management specific. + +_LCK 6.3.4 Use as needed. + +_LPI 8.4.4.3 Use as needed, but recommended for use with processor + definitions (_HID ACPI0010) on arm64. -_LCK 6.3.4 Optional. +_MAT 6.2.10 Use as needed; see also the MADT. -_MAT 6.2.10 Optional; see also the MADT. +_MBM 9.13.2.1 Use as needed. -_MLS 6.1.7 Optional, but highly recommended for use in +_MLS 6.1.7 Use as needed, but highly recommended for use in internationalization. -_OFF 7.1.2 It is recommended to define this method for any device +_MSG 9.2.2 Use as needed. + +_MSM 9.13.2.2 Use as needed. + +_MTL 11.4.8 Use as needed. + +_NTT 11.4.9 Use as needed. + +_OFF 7.2.2 It is recommended to define this method for any device that can be turned on or off. -_ON 7.1.3 It is recommended to define this method for any device +_ON 7.2.3 It is recommended to define this method for any device that can be turned on or off. \_OS 5.7.3 This method will return "Linux" by default (this is @@ -405,115 +506,219 @@ _OSC 6.2.11 This method can be a global method in ACPI (i.e., being used or what functionality is provided. The _OSC method is to be used instead. -_OST 6.3.5 Optional. +_OST 6.3.5 Use as needed. + +_PCT 8.4.6.1 Use as needed; power management specific. _PDC 8.4.1 Deprecated, do not use on arm64. +_PDL 8.4.6.2 Use as needed; power management specific. + \_PIC 5.8.1 The method should not be used. On arm64, the only interrupt model available is GIC. -_PLD 6.1.8 Optional. +_PLD 6.1.8 Use as needed. + +_PPC 8.4.6.3 Use as needed; power management specific. + +_PPE 8.4.8 Use as needed. \_PR 5.3.1 This namespace is for x86 use only on legacy systems. Do not use it on arm64. -_PRS 6.2.12 Optional. +_PRE 7.3.12 Use as needed; power management specific. + +_PRR 7.3.26 Use as needed; power management specific. + +_PRS 6.2.12 Use as needed. _PRT 6.2.13 Required as part of the definition of all PCI root devices. -_PRW 7.2.13 Use as needed; power management specific. +_PRW 7.3.13 Use as needed; power management specific. -_PRx 7.2.8-11 Use as needed; power management specific. If _PR0 is +_PRx 7.3.8-11 Use as needed; power management specific. If _PR0 is defined, _PR3 must also be defined. -_PSC 7.2.6 Use as needed; power management specific. +_PSC 7.3.6 Use as needed; power management specific. + +_PSD 8.4.6.5 Use as needed; power management specific. -_PSE 7.2.7 Use as needed; power management specific. +_PSE 7.3.7 Use as needed; power management specific. -_PSW 7.2.14 Use as needed; power management specific. +_PSL 11.4.10 Use as needed. -_PSx 7.2.2-5 Use as needed; power management specific. If _PS0 is +_PSS 8.4.6.2 Use as needed; power management specific. + +_PSV 11.4.11 Use as needed. + +_PSW 7.3.14 Use as needed; power management specific. + +_PSx 7.3.2-5 Use as needed; power management specific. If _PS0 is defined, _PS3 must also be defined. If clocks or regulators need adjusting to be consistent with power usage, change them in these methods. -\_PTS 7.3.1 Use as needed; power management specific. +_PTC 8.4.5.1 Use as needed; power management specific. + +\_PTS 7.4.1 Use as needed; power management specific. + +_PUR 8.5.1.1 Use as needed. + +_PXM 6.2.14 Use as needed. -_PXM 6.2.14 Optional. +_RDI 8.4.4.4 Use as needed, but recommended for use with processor + definitions (_HID ACPI0010) on arm64. _REG 6.5.4 Use as needed. \_REV 5.7.4 Always returns the latest version of ACPI supported. -_RMV 6.3.6 Optional. +_RMV 6.3.6 Use as needed. + +_RST 7.3.25 Use as needed; power management specific. + +_RTV 11.4.12 Use as needed. \_SB 5.3.1 Required on arm64; all devices must be defined in this namespace. +_SCP 11.4.13 Use as needed. + +_SDD 9.9.3.3.1 Use as needed. + _SEG 6.5.6 Use as needed; PCI-specific. -\_SI 5.3.1, Optional. - 9.1 +\_SI 5.3.1, Use as needed. + 9.2 + +_SLI 6.2.15 Use as needed; recommended when SLIT table is in use. -_SLI 6.2.15 Optional; recommended when SLIT table is in use. +_SRT 9.18.4 Use as needed. _STA 6.3.7, It is recommended to define this method for any device - 7.1.4 that can be turned on or off. + 7.2.4 that can be turned on or off. See also the STAO table + that provides overrides to hide devices in virtualized + environments. -_SRS 6.2.16 Optional; see also _PRS. +_SRS 6.2.16 Use as needed; see also _PRS. + +_SST 9.2.1 Use as needed. _STR 6.1.10 Recommended for conveying device names to end users; this is preferred over using _DDN. +_SST 9.2.1 Use as needed. + +_STP 9.18.7 Use as needed. + +_STV 9.18.8 Use as needed. + _SUB 6.1.9 Use as needed; _HID or _CID are preferred. -_SUN 6.1.11 Optional. +_SUN 6.1.11 Use as needed, but recommended. -\_Sx 7.3.2 Use as needed; power management specific. +\_Sx 7.4.2 Use as needed; power management specific. -_SxD 7.2.16-19 Use as needed; power management specific. +_SxD 7.3.16-19 Use as needed; power management specific. -_SxW 7.2.20-24 Use as needed; power management specific. +_SxW 7.3.20-24 Use as needed; power management specific. -_SWS 7.3.3 Use as needed; power management specific; this may +_SWS 7.4.3 Use as needed; power management specific; this may require specification changes for use on arm64. -\_TTS 7.3.4 Use as needed; power management specific. +_TC1 11.4.14 Use as needed. + +_TC2 11.4.15 Use as needed. + +_TDL 8.4.5.5 Use as needed; power management specific. + +_TFP 11.4.16 Use as needed. + +_TIP 9.18.9 Use as needed. + +_TIV 9.18.10 Use as needed. + +_TMP 11.4.17 Use as needed. + +_TPC 8.4.5.3 Use as needed; power management specific. -\_TZ 5.3.1 Optional. +_TPT 11.4.18 Use as needed. + +_TRT 11.4.19 Use as needed. + +_TSD 8.4.5.4 Use as needed; power management specific. + +_TSN 11.4.20 Use as needed. + +_TSP 11.4.21 Use as needed. + +_TSS 8.4.5.2 Use as needed; power management specific. + +_TST 11.4.22 Use as needed. + +\_TTS 7.4.4 Use as needed; power management specific. + +\_TZ 5.3.1 Use as needed. + +_TZD 11.4.23 Use as needed. + +_TZM 11.4.24 Use as needed. + +_TZP 11.4.25 Use as needed. _UID 6.1.12 Recommended for distinguishing devices of the same class; define it if at all possible. -\_WAK 7.3.5 Use as needed; power management specific. +_UPC 9.14 Use as needed. + +\_WAK 7.4.5 Use as needed; power management specific. + + ACPI Event Model ---------------- Do not use GPE block devices; these are not supported in the hardware reduced profile used by arm64. Since there are no GPE blocks defined for use on ARM -platforms, GPIO-signaled interrupts should be used for creating system events. +platforms, ACPI events must be signaled differently. + +There are two options: GPIO-signaled interrupts (Section 5.6.5), and +interrupt-signaled events (Section 5.6.9). Interrupt-signaled events are a +new feature in the ACPI 6.1 specification. Either -- or both -- can be used +on a given platform, and which to use may be dependent of limitations in any +given SoC. If possible, interrupt-signaled events are recommended. ACPI Processor Control ---------------------- -Section 8 of the ACPI specification is currently undergoing change that -should be completed in the 6.0 version of the specification. Processor -performance control will be handled differently for arm64 at that point -in time. Processor aggregator devices (section 8.5) will not be used, -for example, but another similar mechanism instead. - -While UEFI constrains what we can say until the release of 6.0, it is -recommended that CPPC (8.4.5) be used as the primary model. This will -still be useful into the future. C-states and P-states will still be -provided, but most of the current design work appears to favor CPPC. +Section 8 of the ACPI specification changed significantly in version 6.0. +Processors should now be defined as Device objects with _HID ACPI0007; do +not use the deprecated Processor statement in ASL. All multiprocessor systems +should also define a hierarchy of processors, done with Processor Container +Devices (see Section 8.4.3.1, _HID ACPI0010); do not use processor aggregator +devices (Section 8.5) to describe processor topology. Section 8.4 of the +specification describes the semantics of these object definitions and how +they interrelate. + +Most importantly, the processor hierarchy defined also defines the low power +idle states that are available to the platform, along with the rules for +determining which processors can be turned on or off and the circumstances +that control that. Without this information, the processors will run in +whatever power state they were left in by UEFI. + +Note too, that the processor Device objects defined and the entries in the +MADT for GICs are expected to be in sychronization. The _UID of the Device +object must correspond to processor IDs used in the MADT. + +It is recommended that CPPC (8.4.5) be used as the primary model for processor +performance control on arm64. C-states and P-states may become available at +some point in the future, but most current design work appears to favor CPPC. Further, it is essential that the ARMv8 SoC provide a fully functional implementation of PSCI; this will be the only mechanism supported by ACPI -to control CPU power state (including secondary CPU booting). - -More details will be provided on the release of the ACPI 6.0 specification. +to control CPU power state. Booting of secondary CPUs may be possible using +parking protocol, but only PSCI is to be used for ARM servers. ACPI System Address Map Interfaces @@ -535,21 +740,25 @@ used to indicate fatal errors that cannot be corrected, and require immediate attention. Since there is no direct equivalent of the x86 SCI or NMI, arm64 handles -these slightly differently. The SCI is handled as a normal GPIO-signaled -interrupt; given that these are corrected (or correctable) errors being -reported, this is sufficient. The NMI is emulated as the highest priority -GPIO-signaled interrupt possible. This implies some caution must be used -since there could be interrupts at higher privilege levels or even interrupts -at the same priority as the emulated NMI. In Linux, this should not be the -case but one should be aware it could happen. +these slightly differently. The SCI is handled as a high priority interrupt; +given that these are corrected (or correctable) errors being reported, this +is sufficient. The NMI is emulated as the highest priority interrupt +possible. This implies some caution must be used since there could be +interrupts at higher privilege levels or even interrupts at the same priority +as the emulated NMI. In Linux, this should not be the case but one should +be aware it could happen. ACPI Objects Not Supported on ARM64 ----------------------------------- While this may change in the future, there are several classes of objects that can be defined, but are not currently of general interest to ARM servers. +Some of these objects have x86 equivalents, and may actually make sense in ARM +servers. However, there is either no hardware available at present, or there +may not even be a non-ARM implementation yet. Hence, they are not currently +supported. -These are not supported: +The following classes of objects are not supported: -- Section 9.2: ambient light sensor devices @@ -571,16 +780,6 @@ These are not supported: -- Section 9.18: time and alarm devices (see 9.15) - -ACPI Objects Not Yet Implemented --------------------------------- -While these objects have x86 equivalents, and they do make some sense in ARM -servers, there is either no hardware available at present, or in some cases -there may not yet be a non-ARM implementation. Hence, they are currently not -implemented though that may change in the future. - -Not yet implemented are: - -- Section 10: power source and power meter devices -- Section 11: thermal management @@ -589,5 +788,31 @@ Not yet implemented are: -- Section 13: SMBus interfaces - -- Section 17: NUMA support (prototypes have been submitted for - review) + +This also mean that there is no support for the following objects: + +Name Section Name Section +---- ------------ ---- ------------ +_ALC 9.3.4 _FDM 9.10.3 +_ALI 9.3.2 _FIX 6.2.7 +_ALP 9.3.6 _GAI 10.4.5 +_ALR 9.3.5 _GHL 10.4.7 +_ALT 9.3.3 _GTM 9.9.2.1.1 +_BCT 10.2.2.10 _LID 9.5.1 +_BDN 6.5.3 _PAI 10.4.4 +_BIF 10.2.2.1 _PCL 10.3.2 +_BIX 10.2.2.1 _PIF 10.3.3 +_BLT 9.2.3 _PMC 10.4.1 +_BMA 10.2.2.4 _PMD 10.4.8 +_BMC 10.2.2.12 _PMM 10.4.3 +_BMD 10.2.2.11 _PRL 10.3.4 +_BMS 10.2.2.5 _PSR 10.3.1 +_BST 10.2.2.6 _PTP 10.4.2 +_BTH 10.2.2.7 _SBS 10.1.3 +_BTM 10.2.2.9 _SHL 10.4.6 +_BTP 10.2.2.8 _STM 9.9.2.1.1 +_DCK 6.5.2 _UPD 9.16.1 +_EC 12.12 _UPP 9.16.2 +_FDE 9.10.1 _WPC 10.5.2 +_FDI 9.10.2 _WPP 10.5.3 + diff --git a/Documentation/arm64/arm-acpi.txt b/Documentation/arm64/arm-acpi.txt index 570a4f8..12381c1 100644 --- a/Documentation/arm64/arm-acpi.txt +++ b/Documentation/arm64/arm-acpi.txt @@ -57,11 +57,11 @@ The short form of the rationale for ACPI on ARM is: -- The new ACPI governance process works well and Linux is now at the same table as hardware vendors and other OS vendors. In fact, there is no - longer any reason to feel that ACPI is only belongs to Windows or that + longer any reason to feel that ACPI only belongs to Windows or that Linux is in any way secondary to Microsoft in this arena. The move of ACPI governance into the UEFI forum has significantly opened up the specification development process, and currently, a large portion of the - changes being made to ACPI is being driven by Linux. + changes being made to ACPI are being driven by Linux. Key to the use of ACPI is the support model. For servers in general, the responsibility for hardware behaviour cannot solely be the domain of the @@ -159,7 +159,7 @@ Further, the ACPI core will only use the 64-bit address fields in the FADT (Fixed ACPI Description Table). Any 32-bit address fields in the FADT will be ignored on arm64. -Hardware reduced mode (see Section 4.1 of the ACPI 5.1 specification) will +Hardware reduced mode (see Section 4.1 of the ACPI 6.1 specification) will be enforced by the ACPI core on arm64. Doing so allows the ACPI core to run less complex code since it no longer has to provide support for legacy hardware from other architectures. Any fields that are not to be used for @@ -167,7 +167,7 @@ hardware reduced mode must be set to zero. For the ACPI core to operate properly, and in turn provide the information the kernel needs to configure devices, it expects to find the following -tables (all section numbers refer to the ACPI 5.1 specfication): +tables (all section numbers refer to the ACPI 6.1 specfication): -- RSDP (Root System Description Pointer), section 5.2.5 @@ -185,9 +185,22 @@ tables (all section numbers refer to the ACPI 5.1 specfication): -- If PCI is supported, the MCFG (Memory mapped ConFiGuration Table), section 5.2.6, specifically Table 5-31. + -- If booting without a console=<device> kernel parameter is + supported, the SPCR (Serial Port Console Redirection table), + section 5.2.6, specifically Table 5-31. + + -- If virtualization is supported, the IORT (Input Output Remapping + Table, section 5.2.6, specifically Table 5-31. + + -- If NUMA is supported, the SRAT (System Resource Affinity Table) + and SLIT (System Locality distance Information Table), sections + 5.2.16 and 5.2.17, respectively. + If the above tables are not all present, the kernel may or may not be able to boot properly since it may not be able to configure all of the -devices available. +devices available. This list of tables is not meant to be all inclusive; +in some environments other tables may be needed (e.g., any of the APEI +tables from section 18) to support specific functionality. ACPI Detection @@ -233,7 +246,7 @@ that looks like this: Name(KEY0, "value0"). An ACPI device driver would then retrieve the value of the property by evaluating the KEY0 object. However, using Name() this way has multiple problems: (1) ACPI limits names ("KEY0") to four characters unlike DT; (2) there is no industry -wide registry that maintains a list of names, minimzing re-use; (3) +wide registry that maintains a list of names, minimizing re-use; (3) there is also no registry for the definition of property values ("value0"), again making re-use difficult; and (4) how does one maintain backward compatibility as new hardware comes out? The _DSD method was created @@ -434,7 +447,8 @@ The ACPI specification changes regularly. During the year 2014, for instance, version 5.1 was released and version 6.0 substantially completed, with most of the changes being driven by ARM-specific requirements. Proposed changes are presented and discussed in the ASWG (ACPI Specification Working Group) which -is a part of the UEFI Forum. +is a part of the UEFI Forum. The current version of the ACPI specification +is 6.1 release in January 2016. Participation in this group is open to all UEFI members. Please see http://www.uefi.org/workinggroup for details on group membership. -- 2.5.0

9 years, 1 month

3
3
0 0

[PATCH v4 0/5] acpi, clocksource, kvm: add GTDT and ARM memory-mapped timer support

by fu.wei＠linaro.org

From: Fu Wei <fu.wei(a)linaro.org> This patchset: (1)Move some enums and marcos to header file for arm_arch_timer, improve the pr_* code by defining "pr_fmt(fmt)" in arm_arch_timer.c (2)Introduce ACPI GTDT parser: drivers/acpi/gtdt.c Parse all kinds of timer in GTDT table of ACPI:arch timer, memory-mapped timer and SBSA Generic Watchdog timer. This driver can help to simplify all the relevant timer drivers, and separate all the ACPI GTDT knowledge from them. (3)Simplify ACPI code for arch timer in arm_arch_timer.c (4)Add memory-mapped timer support in arm_arch_timer.c Changelog: v4: Delete the kvm relevant patches Separate two patches for sorting out the code for arm_arch_timer. Improve irq info export code to allow missing irq info in GTDT table. v3: https://lkml.org/lkml/2016/2/1/658 Improve GTDT driver code: (1)improve pr_* by defining pr_fmt(fmt) (2)simplify gtdt_sbsa_gwdt_init (3)improve gtdt_arch_timer_data_init, if table is NULL, it will try to get GTDT table. Move enum ppi_nr to arm_arch_timer.h, and add enum spi_nr. Add arm_arch_timer get ppi from DT and GTDT support for kvm. v2: https://lkml.org/lkml/2015/12/2/10 Rebase to latest kernel version(4.4-rc3). Fix the bug about the config problem, use CONFIG_ACPI_GTDT instead of CONFIG_ACPI in arm_arch_timer.c v1: The first upstreaming version: https://lkml.org/lkml/2015/10/28/553 Fu Wei (5): clocksource: move some enums and marcos to header file for arm_arch_timer ACPI: add GTDT table parse driver into ACPI driver clocksource: simplify ACPI code in arm_arch_timer.c clocksource: a little improvment for printk in arm_arch_timer.c clocksource: add memory-mapped timer support in arm_arch_timer.c drivers/acpi/Kconfig | 9 + drivers/acpi/Makefile | 1 + drivers/acpi/gtdt.c | 376 +++++++++++++++++++++++++++++++++++ drivers/clocksource/Kconfig | 1 + drivers/clocksource/arm_arch_timer.c | 217 ++++++++++++++------ include/clocksource/arm_arch_timer.h | 33 +++ include/linux/acpi.h | 17 ++ 7 files changed, 595 insertions(+), 59 deletions(-) create mode 100644 drivers/acpi/gtdt.c -- 2.5.0

9 years, 1 month

4
11
0 0

Re: [Linaro-acpi] Firmware Test Suite 16.03.00 is released

by Itaru Kitayama

Hi, Is anyone continuously testing QEMU F/W with this test suite within Linaro in an automated way? I'd like to compare my results.log obtained locally with it, if available. Itaru

9 years, 1 month

1
0
0 0

Fwd: Firmware Test Suite 16.03.00 is released

by Alex Hung

FWTS 16.03.00 is released. It is available from: Tar: http://fwts.ubuntu.com/release/fwts-V16.03.00.tar.gz PPA: https://launchpad.net/~firmware-testing-team/+archive/ubuntu/ppa-fwts-stable Release notes: https://wiki.ubuntu.com/FirmwareTestSuite/ReleaseNotes/16.03.00 = New Features = * debian/control: Add s390x to Architecture list (LP: #1549737) * Add s390x build support, don't build ACPI specific code for this arch * Add s390x build support: skip tests that are not build in for this arch * Add s390x build support, don't build UEFI specific code for this arch * uefi: add sanity check for UEFI ESRT table (LP: #1553043) = Fixed Bugs = * Debian/control: don't build UEFI kernel module for s390x * uefi: esrt: don't build UEFI specific code for s390x * smatchify: add two passes option * acpi: csrt: fix a spelling mistake in a comment * acpi: csrt: fix resource descriptor can go over boundary * lib: fwts_cpu: fix memory leak and incorrect return (LP: #1549723) * acpi: fan: fix indentation, remove extraneous tab * acpi: method: fix a few incorrectly idented lines of code * bios: mpcheck: fix trivial indentation issue * bios: mpdump: fix trivial indentation issue * uefi: uefirtvariable: fix trivial indentation issues * uefi: uefirtauthvar: fix trivial indentation issues * uefi: esrt: fix the resource leak found by Coverity Scan * uefi: esrt: fix build failure due to lack of header file * acpi: method: fix fail check on _EC control method (LP: #1556720) * acpi: method: fix _ON method never be tested. * acpi: method: remove some reduntant and unused tests. = Detail Changelog = To check /usr/share/doc/fwts/changelog.Debian.gz or fwts_16.03.00-0ubuntu1.debian.tar.gz from https://launchpad.net/ubuntu/+source/fwts

9 years, 1 month

1
0
0 0

[PATCH V4 0/5] acpi: cppc optimization patches

by Prashanth Prakash

Changes in V4: [1] Added another patch which decides if or when to send a request to the platform based on the Minimum Request Turnaround Time(MRTT) and Maximum Periodic Access Rate(MPAR) to make sure the implementation is compliant to ACPI spec [2] Fixed the condition for pr_debug message in cppc_chan_tx_done() Changes in V3: Addressed the review comments from Alexey, Ashwin and Timur Changes in V2: Fixed compilation error on i386 This series introduces changes to reduce the time required to send a frequency transition requests to the platform while using the cppc-cpufreq driver. With these changes we see significant improvement in the average time to send freq. transition request to the platform. Profiling on an ARM platform showed that the average transaction time per request reduced from 200us to under 20us. Ashwin Chaugule (1): ACPI / CPPC: Optimize PCC Read Write operations Prashanth Prakash (4): acpi: cppc: optimized cpc_read and cpc_write mailbox: pcc: optimized pcc_send_data acpi: cppc: replace writeX/readX to PCC with relaxed version acpi/cppc: use MRTT/MPAR to decide if/when a req can be sent drivers/acpi/cppc_acpi.c | 237 ++++++++++++++++++++++++++++++++++++++--------- drivers/mailbox/pcc.c | 111 ++++++++++++++++++++-- 2 files changed, 295 insertions(+), 53 deletions(-) -- Qualcomm Technologies, Inc. on behalf of the Qualcomm Innovation Center, Inc. The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum, a Linux Foundation Collaborative Project.

9 years, 2 months

3
8
0 0

[PATCH v6] acpi, apei, arm64: APEI initial support for aarch64.

by fu.wei＠linaro.org

From: Tomasz Nowicki <tomasz.nowicki(a)linaro.org> This commit provides APEI arch-specific bits for aarch64 Meanwhile, (1)add a new subfunction "hest_ia32_init" for "acpi_disable_cmcff" which is used by IA-32 Architecture Corrected Machine Check (CMC). (2)move HEST type (ACPI_HEST_TYPE_IA32_CORRECTED_CHECK) checking to a generic place. Signed-off-by: Tomasz Nowicki <tomasz.nowicki(a)linaro.org> Tested-by: Jonathan (Zhixiong) Zhang <zjzhang(a)codeaurora.org> Signed-off-by: Fu Wei <fu.wei(a)linaro.org> Acked-by: Hanjun Guo <hanjun.guo(a)linaro.org> Tested-by: Tyler Baicar <tbaicar(a)codeaurora.org> --- Changelog: v6: Move HEST type (ACPI_HEST_TYPE_IA32_CORRECTED_CHECK) checking to a generic place. Delete HAVE_ACPI_APEI_HEST_IA32. v5: Add "HAVE_ACPI_APEI_HEST_IA32" instead of "#if defined(__i386__) || defined(__x86_64__)". v4: Rebase to latest kernel version(4.4-rc4). Move arch_apei_flush_tlb_one into header file as a inline function Add a new subfunction "hest_ia_init" for "acpi_disable_cmcff". v3: https://lkml.org/lkml/2015/12/3/521 Remove "acpi_disable_cmcff" from arm64 code, and wrap it in hest.c by "#if defined(__i386__) || defined(__x86_64__)" v2: https://lkml.org/lkml/2015/12/2/432 Rebase to latest kernel version(4.4-rc3). Move arch_apei_flush_tlb_one() to arch/arm64/kernel/acpi.c v1: https://lkml.org/lkml/2015/8/14/199 Move arch_apei_flush_tlb_one() to arch/arm64/include/asm/apci.h. Delete arch/arm64/kernel/apei.c. Add "#ifdef CONFIG_ACPI_APEI" for "acpi_disable_cmcff". arch/arm64/Kconfig | 1 + arch/arm64/include/asm/acpi.h | 8 +++++++- arch/x86/kernel/acpi/apei.c | 3 --- drivers/acpi/apei/hest.c | 18 +++++++++++++++--- 4 files changed, 23 insertions(+), 7 deletions(-) diff --git a/arch/arm64/Kconfig b/arch/arm64/Kconfig index 8cc6228..7b430d9 100644 --- a/arch/arm64/Kconfig +++ b/arch/arm64/Kconfig @@ -3,6 +3,7 @@ config ARM64 select ACPI_CCA_REQUIRED if ACPI select ACPI_GENERIC_GSI if ACPI select ACPI_REDUCED_HARDWARE_ONLY if ACPI + select HAVE_ACPI_APEI if ACPI select ARCH_HAS_DEVMEM_IS_ALLOWED select ARCH_HAS_ATOMIC64_DEC_IF_POSITIVE select ARCH_HAS_ELF_RANDOMIZE diff --git a/arch/arm64/include/asm/acpi.h b/arch/arm64/include/asm/acpi.h index caafd63..1a21c996 100644 --- a/arch/arm64/include/asm/acpi.h +++ b/arch/arm64/include/asm/acpi.h @@ -17,6 +17,7 @@ #include <asm/cputype.h> #include <asm/smp_plat.h> +#include <asm/tlbflush.h> /* Macros for consistency checks of the GICC subtable of MADT */ #define ACPI_MADT_GICC_LENGTH \ @@ -93,7 +94,12 @@ static inline const char *acpi_get_enable_method(int cpu) } #ifdef CONFIG_ACPI_APEI +#define acpi_disable_cmcff 1 pgprot_t arch_apei_get_mem_attribute(phys_addr_t addr); -#endif +static inline void arch_apei_flush_tlb_one(unsigned long addr) +{ + flush_tlb_kernel_range(addr, addr + PAGE_SIZE); +} +#endif /* CONFIG_ACPI_APEI */ #endif /*_ASM_ACPI_H*/ diff --git a/arch/x86/kernel/acpi/apei.c b/arch/x86/kernel/acpi/apei.c index c280df6..ea3046e 100644 --- a/arch/x86/kernel/acpi/apei.c +++ b/arch/x86/kernel/acpi/apei.c @@ -24,9 +24,6 @@ int arch_apei_enable_cmcff(struct acpi_hest_header *hest_hdr, void *data) struct acpi_hest_ia_corrected *cmc; struct acpi_hest_ia_error_bank *mc_bank; - if (hest_hdr->type != ACPI_HEST_TYPE_IA32_CORRECTED_CHECK) - return 0; - cmc = (struct acpi_hest_ia_corrected *)hest_hdr; if (!cmc->enabled) return 0; diff --git a/drivers/acpi/apei/hest.c b/drivers/acpi/apei/hest.c index 20b3fcf..792a0d9 100644 --- a/drivers/acpi/apei/hest.c +++ b/drivers/acpi/apei/hest.c @@ -123,7 +123,18 @@ EXPORT_SYMBOL_GPL(apei_hest_parse); */ static int __init hest_parse_cmc(struct acpi_hest_header *hest_hdr, void *data) { - return arch_apei_enable_cmcff(hest_hdr, data); + if (hest_hdr->type != ACPI_HEST_TYPE_IA32_CORRECTED_CHECK) + return 0; + + if (!acpi_disable_cmcff) + return !arch_apei_enable_cmcff(hest_hdr, data); + + return 0; +} + +static inline int __init hest_ia32_init(void) +{ + return apei_hest_parse(hest_parse_cmc, NULL); } struct ghes_arr { @@ -232,8 +243,9 @@ void __init acpi_hest_init(void) goto err; } - if (!acpi_disable_cmcff) - apei_hest_parse(hest_parse_cmc, NULL); + rc = hest_ia32_init(); + if (rc) + goto err; if (!ghes_disable) { rc = apei_hest_parse(hest_parse_ghes_count, &ghes_count); -- 2.5.0

9 years, 2 months

1
0
0 0

[PATCH V4 00/23] MMCONFIG refactoring and support for ARM64 PCI hostbridge init based on ACPI

by Tomasz Nowicki

>From the functionality point of view this series might be split into the following logic parts: 1. Make MMCONFIG code arch-agnostic which allows all architectures to collect PCI config regions and used when necessary. 2. Move non-arch specific bits to the core code. 3. Use MMCONFIG code and implement generic ACPI based PCI host controller driver. 4. Enable above driver on ARM64 Patches has been built on top of 4.5-rc1 and can be found here: git@github.com:semihalf-nowicki-tomasz/linux.git (pci-acpi-v4) NOTE, this patch set depends on Lorenzo's fixes: https://patchwork.ozlabs.org/patch/576450/ which can be found in pci-acpi-v4 branch. This has been tested on Cavium ThunderX server, JunoR2, HP RX2660 IA64, x86, Hip05, X-Gene and QEMU-aarch64. Any help in reviewing and testing is very appreciated. v3 -> v4 - dropped Jiang's fix http://lkml.iu.edu/hypermail/linux/kernel/1601.1/04318.html - added Lorenzo's fix patch 19/24 - ACPI PCI bus domain number assigning cleanup - changed resource management, we now claim and reassign resources - improvements for applying quirks - dropped Matthew's http://www.spinics.net/lists/linux-pci/msg45950.html dependency - rebased to 4.5-rc1 v2 -> v3 - fix legacy IRQ assigning and IO ports registration - remove reference to arch specific companion device for ia64 - move ACPI PCI host controller driver to pci_root.c - drop generic domain assignment for x86 and ia64 as I am not able to run all necessary test variants - drop patch which cleaned legacy IRQ assignment since it belongs to Mathew's series: https://patchwork.ozlabs.org/patch/557504/ - extend MCFG quirk code - rebased to 4.4 v1 -> v2 - moved non-arch specific piece of code to dirver/acpi/ directory - fixed IO resource handling - introduced PCI config accessors quirks matching - moved ACPI_COMPANION_SET to generic code v1 - https://lkml.org/lkml/2015/10/27/504 v2 - https://lkml.org/lkml/2015/12/16/246 v3 - http://lkml.iu.edu/hypermail/linux/kernel/1601.1/04308.html Lorenzo Pieralisi (1): drivers: pci: add generic code to claim bus resources Tomasz Nowicki (22): x86, pci: Reorder logic of pci_mmconfig_insert() function x86, pci, acpi: Move arch-agnostic MMCONFIG (aka ECAM) and ACPI code out of arch/x86/ directory pci, acpi, mcfg: Provide generic implementation of MCFG code initialization. x86, pci: mmconfig_{32,64}.c code refactoring - remove code duplication. x86, pci, ecam: mmconfig_64.c becomes default implementation for ECAM driver. XEN / PCI: Remove the dependence on arch x86 when PCI_MMCONFIG=y pci, acpi, mcfg: Provide default RAW ACPI PCI config space accessors. arm64, acpi: Use MCFG and empty PCI config space accessors from mcfg.c file. pci, acpi, ecam: Add flag to indicate whether ECAM region was hot added or not. x86, pci: Cleanup platform specific MCFG data by using ECAM hot_added flag. pci, acpi: Move ACPI host bridge device companion assignment to core code. x86, ia64, pci: Remove ACPI companion device from platform specific data. pci, acpi: Provide generic way to assign bus domain number. x86, ia64: Include acpi_pci_{add|remove}_bus to the default pcibios_{add|remove}_bus implementation. acpi, mcfg: Implement two calls that might be used to inject/remove MCFG region. x86, acpi, pci: Use equivalent function from mcfg.c driver. acpi, mcfg: Add default PCI config accessors implementation and initial support for related quirks. pci, of: Move the PCI I/O space management to PCI core code. pci, acpi: Support for ACPI based generic PCI host controller init pci, acpi: Match PCI config space accessors against platfrom specific quirks. arm64, pci, acpi: Assign legacy IRQs once device is enable. arm64, pci, acpi: Start using ACPI based PCI host bridge driver for ARM64. arch/arm64/Kconfig | 8 ++ arch/arm64/kernel/pci.c | 37 ++---- arch/ia64/hp/common/sba_iommu.c | 2 +- arch/ia64/include/asm/pci.h | 1 - arch/ia64/pci/pci.c | 26 ---- arch/ia64/sn/kernel/io_acpi_init.c | 4 +- arch/x86/Kconfig | 4 + arch/x86/include/asm/pci.h | 3 - arch/x86/include/asm/pci_x86.h | 28 +---- arch/x86/pci/acpi.c | 56 ++------- arch/x86/pci/common.c | 10 -- arch/x86/pci/mmconfig-shared.c | 250 ++++++------------------------------- arch/x86/pci/mmconfig_32.c | 11 +- arch/x86/pci/mmconfig_64.c | 67 +--------- arch/x86/pci/numachip.c | 1 + drivers/acpi/Kconfig | 7 ++ drivers/acpi/Makefile | 1 + drivers/acpi/mcfg.c | 201 +++++++++++++++++++++++++++++ drivers/acpi/pci_root.c | 134 +++++++++++++++++++- drivers/of/address.c | 116 +---------------- drivers/pci/Kconfig | 10 ++ drivers/pci/Makefile | 5 + drivers/pci/ecam.c | 234 ++++++++++++++++++++++++++++++++++ drivers/pci/pci.c | 126 ++++++++++++++++++- drivers/pci/probe.c | 5 + drivers/pci/setup-bus.c | 63 ++++++++++ drivers/xen/pci.c | 7 +- include/acpi/acpi_bus.h | 1 + include/asm-generic/vmlinux.lds.h | 7 ++ include/linux/acpi.h | 2 + include/linux/ecam.h | 62 +++++++++ include/linux/of_address.h | 9 -- include/linux/pci-acpi.h | 19 +++ include/linux/pci.h | 6 + 34 files changed, 962 insertions(+), 561 deletions(-) create mode 100644 drivers/acpi/mcfg.c create mode 100644 drivers/pci/ecam.c create mode 100644 include/linux/ecam.h -- 1.9.1

9 years, 2 months

3
35
0 0

[PATCH v2] ARM64: ACPI: Update documentation for latest specification version

by Al Stone

From: Al Stone <ahs3(a)redhat.com> The ACPI 6.1 specification was recently released at the end of January 2016, but the arm64 kernel documentation for the use of ACPI was written for the 5.1 version of the spec. There were significant additions to the spec that had not yet been mentioned -- for example, the 6.0 mechanisms added to make it easier to define processors and low power idle states, as well as the 6.1 addition allowing regular interrupts (not just from GPIO) be used to signal ACPI general purpose events. This patch reflects going back through and examining the specs in detail and updating content appropriately. Whilst there, a few odds and ends of typos were caught as well. This brings the documentation up to date with ACPI 6.1 for arm64. Changes for v2: -- Clean up white space (Harb Abdulhahmid) -- Clarification on _CCA usage (Harb Abdulhamid) -- IORT moved to required from recommended (Hanjun Guo) -- Clarify IORT description (Hanjun Guo) Signed-off-by: Al Stone <al.stone(a)linaro.org> --- Documentation/arm64/acpi_object_usage.txt | 445 ++++++++++++++++++++++-------- Documentation/arm64/arm-acpi.txt | 28 +- 2 files changed, 356 insertions(+), 117 deletions(-) diff --git a/Documentation/arm64/acpi_object_usage.txt b/Documentation/arm64/acpi_object_usage.txt index a6e1a18..29bc1a1 100644 --- a/Documentation/arm64/acpi_object_usage.txt +++ b/Documentation/arm64/acpi_object_usage.txt @@ -11,15 +11,16 @@ outside of the UEFI Forum (see Section 5.2.6 of the specification). For ACPI on arm64, tables also fall into the following categories: - -- Required: DSDT, FADT, GTDT, MADT, MCFG, RSDP, SPCR, XSDT + -- Required: DSDT, FADT, GTDT, IORT, MADT, MCFG, RSDP, SPCR, XSDT - -- Recommended: BERT, EINJ, ERST, HEST, SSDT + -- Recommended: BERT, EINJ, ERST, HEST, PCCT, SSDT - -- Optional: BGRT, CPEP, CSRT, DRTM, ECDT, FACS, FPDT, MCHI, MPST, - MSCT, RASF, SBST, SLIT, SPMI, SRAT, TCPA, TPM2, UEFI + -- Optional: BGRT, CPEP, CSRT, DBG2, DRTM, ECDT, FACS, FPDT, MCHI, + MPST, MSCT, NFIT, PMTT, RASF, SBST, SLIT, SPMI, SRAT, STAO, TCPA, + TPM2, UEFI, XENV - -- Not supported: BOOT, DBG2, DBGP, DMAR, ETDT, HPET, IBFT, IVRS, - LPIT, MSDM, RSDT, SLIC, WAET, WDAT, WDRT, WPBT + -- Not supported: BOOT, DBGP, DMAR, ETDT, HPET, IBFT, IVRS, LPIT, + MSDM, OEMx, PSDT, RSDT, SLIC, WAET, WDAT, WDRT, WPBT Table Usage for ARMv8 Linux @@ -50,7 +51,8 @@ CSRT Signature Reserved (signature == "CSRT") DBG2 Signature Reserved (signature == "DBG2") == DeBuG port table 2 == - Microsoft only table, will not be supported. + License has changed and should be usable. Optional if used instead + of earlycon=<device> on the command line. DBGP Signature Reserved (signature == "DBGP") == DeBuG Port table == @@ -133,10 +135,11 @@ GTDT Section 5.2.24 (signature == "GTDT") HEST Section 18.3.2 (signature == "HEST") == Hardware Error Source Table == - Until further error source types are defined, use only types 6 (AER - Root Port), 7 (AER Endpoint), 8 (AER Bridge), or 9 (Generic Hardware - Error Source). Firmware first error handling is possible if and only - if Trusted Firmware is being used on arm64. + ARM-specific error sources have been defined; please use those or the + PCI types such as type 6 (AER Root Port), 7 (AER Endpoint), or 8 (AER + Bridge), or use type 9 (Generic Hardware Error Source). Firmware first + error handling is possible if and only if Trusted Firmware is being + used on arm64. Must be supplied if RAS support is provided by the platform. It is recommended this table be supplied. @@ -149,20 +152,27 @@ IBFT Signature Reserved (signature == "IBFT") == iSCSI Boot Firmware Table == Microsoft defined table, support TBD. +IORT Signature Reserved (signature == "IORT") + == Input Output Remapping Table == + arm64 only table, required in order to describe IO topology, SMMUs, + and GIC ITSs, and how those various components are connected together, + such as identifying which components are behind which SMMUs/ITSs. + IVRS Signature Reserved (signature == "IVRS") == I/O Virtualization Reporting Structure == x86_64 (AMD) only table, will not be supported. LPIT Signature Reserved (signature == "LPIT") == Low Power Idle Table == - x86 only table as of ACPI 5.1; future versions have been adapted for - use with ARM and will be recommended in order to support ACPI power - management. + x86 only table as of ACPI 5.1; starting with ACPI 6.0, processor + descriptions and power states on ARM platforms should use the DSDT + and define processor container devices (_HID ACPI0010, Section 8.4, + and more specifically 8.4.3 and and 8.4.4). MADT Section 5.2.12 (signature == "APIC") == Multiple APIC Description Table == Required for arm64. Only the GIC interrupt controller structures - should be used (types 0xA - 0xE). + should be used (types 0xA - 0xF). MCFG Signature Reserved (signature == "MCFG") == Memory-mapped ConFiGuration space == @@ -176,14 +186,38 @@ MPST Section 5.2.21 (signature == "MPST") == Memory Power State Table == Optional, not currently supported. +MSCT Section 5.2.19 (signature == "MSCT") + == Maximum System Characteristic Table == + Optional, not currently supported. + MSDM Signature Reserved (signature == "MSDM") == Microsoft Data Management table == Microsoft only table, will not be supported. -MSCT Section 5.2.19 (signature == "MSCT") - == Maximum System Characteristic Table == +NFIT Section 5.2.25 (signature == "NFIT") + == NVDIMM Firmware Interface Table == Optional, not currently supported. +OEMx Signature of "OEMx" only + == OEM Specific Tables == + All tables starting with a signature of "OEM" are reserved for OEM + use. Since these are not meant to be of general use but are limited + to very specific end users, they are not recommended for use and are + not supported by the kernel for arm64. + +PCCT Section 14.1 (signature == "PCCT) + == Platform Communications Channel Table == + Recommend for use on arm64, and required when using CPPC to control + power on the platform. + +PMTT Section 5.2.21.12 (signature == "PMTT") + == Platform Memory Topology Table == + Optional, but useful, but not currently supported. + +PSDT Section 5.2.11.3 (signature == "PSDT") + == Persistent System Description Table == + Obsolete table, will not be supported. + RASF Section 5.2.20 (signature == "RASF") == RAS Feature table == Optional, not currently supported. @@ -195,7 +229,7 @@ RSDP Section 5.2.5 (signature == "RSD PTR") RSDT Section 5.2.7 (signature == "RSDT") == Root System Description Table == Since this table can only provide 32-bit addresses, it is deprecated - on arm64, and will not be used. + on arm64, and will not be used. If provided, it will be ignored. SBST Section 5.2.14 (signature == "SBST") == Smart Battery Subsystem Table == @@ -207,7 +241,7 @@ SLIC Signature Reserved (signature == "SLIC") SLIT Section 5.2.17 (signature == "SLIT") == System Locality distance Information Table == - Optional in general, but required for NUMA systems. + Optional in general, but required for arm64 NUMA systems. SPCR Signature Reserved (signature == "SPCR") == Serial Port Console Redirection table == @@ -220,7 +254,7 @@ SPMI Signature Reserved (signature == "SPMI") SRAT Section 5.2.16 (signature == "SRAT") == System Resource Affinity Table == Optional, but if used, only the GICC Affinity structures are read. - To support NUMA, this table is required. + To support arm64 NUMA, this table is required. SSDT Section 5.2.11.2 (signature == "SSDT") == Secondary System Description Table == @@ -235,6 +269,11 @@ SSDT Section 5.2.11.2 (signature == "SSDT") These tables are optional, however. ACPI tables should contain only one DSDT but can contain many SSDTs. +STAO Signature Reserved (signature == "STAO") + == _STA Override table == + Optional, but only necessary in virtualized environments in order to + hide devices from guest OSs. + TCPA Signature Reserved (signature == "TCPA") == Trusted Computing Platform Alliance table == Optional, not currently supported, and may need changes to fully @@ -266,6 +305,10 @@ WPBT Signature Reserved (signature == "WPBT") == Windows Platform Binary Table == Microsoft only table, will not be supported. +XENV Signature Reserved (signature == "XENV") + == Xen project table == + Optional, used only by Xen at present. + XSDT Section 5.2.8 (signature == "XSDT") == eXtended System Description Table == Required for arm64. @@ -273,31 +316,57 @@ XSDT Section 5.2.8 (signature == "XSDT") ACPI Objects ------------ -The expectations on individual ACPI objects are discussed in the list that -follows: +The expectations on individual ACPI objects that are likely to be used are +shown in the list that follows: Name Section Usage for ARMv8 Linux ---- ------------ ------------------------------------------------- +_ACx 11.4.1 Use as needed. + _ADR 6.1.1 Use as needed. +_ALx 11.4.2 Use as needed. + +_ART 11.4.3 Use as needed. + _BBN 6.5.5 Use as needed; PCI-specific. -_BDN 6.5.3 Optional; not likely to be used on arm64. +_CCA 6.2.17 This method must be defined for all bus masters + on arm64 -- there are no assumptions made about + whether such devices are cache coherent or not. + The _CCA value is inherited by all descendants of + these devices so it does not need to be repeated. + Without _CCA on arm64, the kernel does not know what + to do about setting up DMA for the device. -_CCA 6.2.17 This method should be defined for all bus masters - on arm64. While cache coherency is assumed, making - it explicit ensures the kernel will set up DMA as - it should. + NB: this method provides default cache coherency + attributes; the presence of an SMMU can be used to + modify that, however. For example, a master could + default to non-coherent, but be made coherent with + the appropriate SMMU configuration (see Table 17 of + the IORT specification, ARM Document DEN 0049B). -_CDM 6.2.1 Optional, to be used only for processor devices. +_CDM 6.2.1 Use as needed, to be used only for processor devices. -_CID 6.1.2 Use as needed. +_CID 6.1.2 Use as needed, see also _HID. -_CLS 6.1.3 Use as needed. +_CLS 6.1.3 Use as needed, see also _HID. + +_CPC 8.4.7.1 Use as needed; power management specific. CPPC is + recommended on arm64. + +_CR3 11.4.5 Use as needed. _CRS 6.2.2 Required on arm64. -_DCK 6.5.2 Optional; not likely to be used on arm64. +_CRT 11.4.4 Use as needed. + +_CSD 8.4.2.2 Use as needed, used only in conjuction with _CST. + +_CST 8.4.2.1 Low power idle states (8.4.4) are recommended instead + of C-states. + +_CWS 9.18.6 Use as needed. _DDN 6.1.4 This field can be used for a device name. However, it is meant for DOS device names (e.g., COM1), so be @@ -305,11 +374,11 @@ _DDN 6.1.4 This field can be used for a device name. However, _DEP 6.5.8 Use as needed. -_DIS 6.2.3 Optional, for power management use. +_DIS 6.2.3 Use as needed, for power management use. -_DLM 5.7.5 Optional. +_DLM 5.7.5 Use as needed. -_DMA 6.2.4 Optional. +_DMA 6.2.4 Use as needed. _DSD 6.2.5 To be used with caution. If this object is used, try to use it within the constraints already defined by the @@ -325,19 +394,29 @@ _DSD 6.2.5 To be used with caution. If this object is used, try with the UEFI Forum; this may cause some iteration as more than one OS will be registering entries. -_DSM Do not use this method. It is not standardized, the +_DSM 9.1.1 Do not use this method. It is not standardized, the return values are not well documented, and it is currently a frequent source of error. -_DSW 7.2.1 Use as needed; power management specific. +_DSW 7.3.1 Use as needed; power management specific. -_EDL 6.3.1 Optional. +_DTI 11.4.6 Use as needed. -_EJD 6.3.2 Optional. +_EDL 6.3.1 Use as needed. -_EJx 6.3.3 Optional. +_EJD 6.3.2 Use as needed. -_FIX 6.2.7 x86 specific, not used on arm64. +_EJx 6.3.3 Use as needed. + +_FIF 11.3.1.1 Use as needed. + +_FPS 11.3.1.2 Use as needed. + +_FSL 11.3.1.3 Use as needed. + +_FST 11.3.1.4 Use as needed. + +_GCP 9.18.2 Use as needed. \_GL 5.7.1 This object is not to be used in hardware reduced mode, and therefore should not be used on arm64. @@ -349,35 +428,57 @@ _GLK 6.5.7 This object requires a global lock be defined; there \_GPE 5.3.1 This namespace is for x86 use only. Do not use it on arm64. -_GSB 6.2.7 Optional. +_GRT 9.18.3 Use as needed. + +_GSB 6.2.7 Use as needed. + +_GTF 9.9.1.1 Use as needed. + +_GWS 9.18.5 Use as needed. _HID 6.1.5 Use as needed. This is the primary object to use in device probing, though _CID and _CLS may also be used. -_HPP 6.2.8 Optional, PCI specific. +_HOT 11.4.7 Use as needed. + +_HPP 6.2.8 Use as needed, PCI specific. -_HPX 6.2.9 Optional, PCI specific. +_HPX 6.2.9 Use as needed, PCI specific. -_HRV 6.1.6 Optional, use as needed to clarify device behavior; in - some cases, this may be easier to use than _DSD. +_HRV 6.1.6 Use as needed, use as needed to clarify device + behavior; in some cases, this may be easier to use + than _DSD. _INI 6.5.1 Not required, but can be useful in setting up devices when UEFI leaves them in a state that may not be what the driver expects before it starts probing. -_IRC 7.2.15 Use as needed; power management specific. +_IRC 7.3.15 Use as needed; power management specific. + +_LCK 6.3.4 Use as needed. + +_LPI 8.4.4.3 Use as needed, but recommended for use with processor + definitions (_HID ACPI0010) on arm64. -_LCK 6.3.4 Optional. +_MAT 6.2.10 Use as needed; see also the MADT. -_MAT 6.2.10 Optional; see also the MADT. +_MBM 9.13.2.1 Use as needed. -_MLS 6.1.7 Optional, but highly recommended for use in +_MLS 6.1.7 Use as needed, but highly recommended for use in internationalization. -_OFF 7.1.2 It is recommended to define this method for any device +_MSG 9.2.2 Use as needed. + +_MSM 9.13.2.2 Use as needed. + +_MTL 11.4.8 Use as needed. + +_NTT 11.4.9 Use as needed. + +_OFF 7.2.2 It is recommended to define this method for any device that can be turned on or off. -_ON 7.1.3 It is recommended to define this method for any device +_ON 7.2.3 It is recommended to define this method for any device that can be turned on or off. \_OS 5.7.3 This method will return "Linux" by default (this is @@ -405,115 +506,219 @@ _OSC 6.2.11 This method can be a global method in ACPI (i.e., being used or what functionality is provided. The _OSC method is to be used instead. -_OST 6.3.5 Optional. +_OST 6.3.5 Use as needed. + +_PCT 8.4.6.1 Use as needed; power management specific. _PDC 8.4.1 Deprecated, do not use on arm64. +_PDL 8.4.6.2 Use as needed; power management specific. + \_PIC 5.8.1 The method should not be used. On arm64, the only interrupt model available is GIC. -_PLD 6.1.8 Optional. +_PLD 6.1.8 Use as needed. + +_PPC 8.4.6.3 Use as needed; power management specific. + +_PPE 8.4.8 Use as needed. \_PR 5.3.1 This namespace is for x86 use only on legacy systems. Do not use it on arm64. -_PRS 6.2.12 Optional. +_PRE 7.3.12 Use as needed; power management specific. + +_PRR 7.3.26 Use as needed; power management specific. + +_PRS 6.2.12 Use as needed. _PRT 6.2.13 Required as part of the definition of all PCI root devices. -_PRW 7.2.13 Use as needed; power management specific. +_PRW 7.3.13 Use as needed; power management specific. -_PRx 7.2.8-11 Use as needed; power management specific. If _PR0 is +_PRx 7.3.8-11 Use as needed; power management specific. If _PR0 is defined, _PR3 must also be defined. -_PSC 7.2.6 Use as needed; power management specific. +_PSC 7.3.6 Use as needed; power management specific. + +_PSD 8.4.6.5 Use as needed; power management specific. -_PSE 7.2.7 Use as needed; power management specific. +_PSE 7.3.7 Use as needed; power management specific. -_PSW 7.2.14 Use as needed; power management specific. +_PSL 11.4.10 Use as needed. -_PSx 7.2.2-5 Use as needed; power management specific. If _PS0 is +_PSS 8.4.6.2 Use as needed; power management specific. + +_PSV 11.4.11 Use as needed. + +_PSW 7.3.14 Use as needed; power management specific. + +_PSx 7.3.2-5 Use as needed; power management specific. If _PS0 is defined, _PS3 must also be defined. If clocks or regulators need adjusting to be consistent with power usage, change them in these methods. -\_PTS 7.3.1 Use as needed; power management specific. +_PTC 8.4.5.1 Use as needed; power management specific. + +\_PTS 7.4.1 Use as needed; power management specific. + +_PUR 8.5.1.1 Use as needed. + +_PXM 6.2.14 Use as needed. -_PXM 6.2.14 Optional. +_RDI 8.4.4.4 Use as needed, but recommended for use with processor + definitions (_HID ACPI0010) on arm64. _REG 6.5.4 Use as needed. \_REV 5.7.4 Always returns the latest version of ACPI supported. -_RMV 6.3.6 Optional. +_RMV 6.3.6 Use as needed. + +_RST 7.3.25 Use as needed; power management specific. + +_RTV 11.4.12 Use as needed. \_SB 5.3.1 Required on arm64; all devices must be defined in this namespace. +_SCP 11.4.13 Use as needed. + +_SDD 9.9.3.3.1 Use as needed. + _SEG 6.5.6 Use as needed; PCI-specific. -\_SI 5.3.1, Optional. - 9.1 +\_SI 5.3.1, Use as needed. + 9.2 + +_SLI 6.2.15 Use as needed; recommended when SLIT table is in use. -_SLI 6.2.15 Optional; recommended when SLIT table is in use. +_SRT 9.18.4 Use as needed. _STA 6.3.7, It is recommended to define this method for any device - 7.1.4 that can be turned on or off. + 7.2.4 that can be turned on or off. See also the STAO table + that provides overrides to hide devices in virtualized + environments. -_SRS 6.2.16 Optional; see also _PRS. +_SRS 6.2.16 Use as needed; see also _PRS. + +_SST 9.2.1 Use as needed. _STR 6.1.10 Recommended for conveying device names to end users; this is preferred over using _DDN. +_SST 9.2.1 Use as needed. + +_STP 9.18.7 Use as needed. + +_STV 9.18.8 Use as needed. + _SUB 6.1.9 Use as needed; _HID or _CID are preferred. -_SUN 6.1.11 Optional. +_SUN 6.1.11 Use as needed, but recommended. -\_Sx 7.3.2 Use as needed; power management specific. +\_Sx 7.4.2 Use as needed; power management specific. -_SxD 7.2.16-19 Use as needed; power management specific. +_SxD 7.3.16-19 Use as needed; power management specific. -_SxW 7.2.20-24 Use as needed; power management specific. +_SxW 7.3.20-24 Use as needed; power management specific. -_SWS 7.3.3 Use as needed; power management specific; this may +_SWS 7.4.3 Use as needed; power management specific; this may require specification changes for use on arm64. -\_TTS 7.3.4 Use as needed; power management specific. +_TC1 11.4.14 Use as needed. + +_TC2 11.4.15 Use as needed. + +_TDL 8.4.5.5 Use as needed; power management specific. + +_TFP 11.4.16 Use as needed. + +_TIP 9.18.9 Use as needed. + +_TIV 9.18.10 Use as needed. + +_TMP 11.4.17 Use as needed. + +_TPC 8.4.5.3 Use as needed; power management specific. -\_TZ 5.3.1 Optional. +_TPT 11.4.18 Use as needed. + +_TRT 11.4.19 Use as needed. + +_TSD 8.4.5.4 Use as needed; power management specific. + +_TSN 11.4.20 Use as needed. + +_TSP 11.4.21 Use as needed. + +_TSS 8.4.5.2 Use as needed; power management specific. + +_TST 11.4.22 Use as needed. + +\_TTS 7.4.4 Use as needed; power management specific. + +\_TZ 5.3.1 Use as needed. + +_TZD 11.4.23 Use as needed. + +_TZM 11.4.24 Use as needed. + +_TZP 11.4.25 Use as needed. _UID 6.1.12 Recommended for distinguishing devices of the same class; define it if at all possible. -\_WAK 7.3.5 Use as needed; power management specific. +_UPC 9.14 Use as needed. + +\_WAK 7.4.5 Use as needed; power management specific. + + ACPI Event Model ---------------- Do not use GPE block devices; these are not supported in the hardware reduced profile used by arm64. Since there are no GPE blocks defined for use on ARM -platforms, GPIO-signaled interrupts should be used for creating system events. +platforms, ACPI events must be signaled differently. + +There are two options: GPIO-signaled interrupts (Section 5.6.5), and +interrupt-signaled events (Section 5.6.9). Interrupt-signaled events are a +new feature in the ACPI 6.1 specification. Either -- or both -- can be used +on a given platform, and which to use may be dependent of limitations in any +given SoC. If possible, interrupt-signaled events are recommended. ACPI Processor Control ---------------------- -Section 8 of the ACPI specification is currently undergoing change that -should be completed in the 6.0 version of the specification. Processor -performance control will be handled differently for arm64 at that point -in time. Processor aggregator devices (section 8.5) will not be used, -for example, but another similar mechanism instead. - -While UEFI constrains what we can say until the release of 6.0, it is -recommended that CPPC (8.4.5) be used as the primary model. This will -still be useful into the future. C-states and P-states will still be -provided, but most of the current design work appears to favor CPPC. +Section 8 of the ACPI specification changed significantly in version 6.0. +Processors should now be defined as Device objects with _HID ACPI0007; do +not use the deprecated Processor statement in ASL. All multiprocessor systems +should also define a hierarchy of processors, done with Processor Container +Devices (see Section 8.4.3.1, _HID ACPI0010); do not use processor aggregator +devices (Section 8.5) to describe processor topology. Section 8.4 of the +specification describes the semantics of these object definitions and how +they interrelate. + +Most importantly, the processor hierarchy defined also defines the low power +idle states that are available to the platform, along with the rules for +determining which processors can be turned on or off and the circumstances +that control that. Without this information, the processors will run in +whatever power state they were left in by UEFI. + +Note too, that the processor Device objects defined and the entries in the +MADT for GICs are expected to be in sychronization. The _UID of the Device +object must correspond to processor IDs used in the MADT. + +It is recommended that CPPC (8.4.5) be used as the primary model for processor +performance control on arm64. C-states and P-states may become available at +some point in the future, but most current design work appears to favor CPPC. Further, it is essential that the ARMv8 SoC provide a fully functional implementation of PSCI; this will be the only mechanism supported by ACPI -to control CPU power state (including secondary CPU booting). - -More details will be provided on the release of the ACPI 6.0 specification. +to control CPU power state. Booting of secondary CPUs may be possible using +parking protocol, but only PSCI is to be used for ARM servers. ACPI System Address Map Interfaces @@ -535,21 +740,25 @@ used to indicate fatal errors that cannot be corrected, and require immediate attention. Since there is no direct equivalent of the x86 SCI or NMI, arm64 handles -these slightly differently. The SCI is handled as a normal GPIO-signaled -interrupt; given that these are corrected (or correctable) errors being -reported, this is sufficient. The NMI is emulated as the highest priority -GPIO-signaled interrupt possible. This implies some caution must be used -since there could be interrupts at higher privilege levels or even interrupts -at the same priority as the emulated NMI. In Linux, this should not be the -case but one should be aware it could happen. +these slightly differently. The SCI is handled as a high priority interrupt; +given that these are corrected (or correctable) errors being reported, this +is sufficient. The NMI is emulated as the highest priority interrupt +possible. This implies some caution must be used since there could be +interrupts at higher privilege levels or even interrupts at the same priority +as the emulated NMI. In Linux, this should not be the case but one should +be aware it could happen. ACPI Objects Not Supported on ARM64 ----------------------------------- While this may change in the future, there are several classes of objects that can be defined, but are not currently of general interest to ARM servers. +Some of these objects have x86 equivalents, and may actually make sense in ARM +servers. However, there is either no hardware available at present, or there +may not even be a non-ARM implementation yet. Hence, they are not currently +supported. -These are not supported: +The following classes of objects are not supported: -- Section 9.2: ambient light sensor devices @@ -571,16 +780,6 @@ These are not supported: -- Section 9.18: time and alarm devices (see 9.15) - -ACPI Objects Not Yet Implemented --------------------------------- -While these objects have x86 equivalents, and they do make some sense in ARM -servers, there is either no hardware available at present, or in some cases -there may not yet be a non-ARM implementation. Hence, they are currently not -implemented though that may change in the future. - -Not yet implemented are: - -- Section 10: power source and power meter devices -- Section 11: thermal management @@ -589,5 +788,31 @@ Not yet implemented are: -- Section 13: SMBus interfaces - -- Section 17: NUMA support (prototypes have been submitted for - review) + +This also mean that there is no support for the following objects: + +Name Section Name Section +---- ------------ ---- ------------ +_ALC 9.3.4 _FDM 9.10.3 +_ALI 9.3.2 _FIX 6.2.7 +_ALP 9.3.6 _GAI 10.4.5 +_ALR 9.3.5 _GHL 10.4.7 +_ALT 9.3.3 _GTM 9.9.2.1.1 +_BCT 10.2.2.10 _LID 9.5.1 +_BDN 6.5.3 _PAI 10.4.4 +_BIF 10.2.2.1 _PCL 10.3.2 +_BIX 10.2.2.1 _PIF 10.3.3 +_BLT 9.2.3 _PMC 10.4.1 +_BMA 10.2.2.4 _PMD 10.4.8 +_BMC 10.2.2.12 _PMM 10.4.3 +_BMD 10.2.2.11 _PRL 10.3.4 +_BMS 10.2.2.5 _PSR 10.3.1 +_BST 10.2.2.6 _PTP 10.4.2 +_BTH 10.2.2.7 _SBS 10.1.3 +_BTM 10.2.2.9 _SHL 10.4.6 +_BTP 10.2.2.8 _STM 9.9.2.1.1 +_DCK 6.5.2 _UPD 9.16.1 +_EC 12.12 _UPP 9.16.2 +_FDE 9.10.1 _WPC 10.5.2 +_FDI 9.10.2 _WPP 10.5.3 + diff --git a/Documentation/arm64/arm-acpi.txt b/Documentation/arm64/arm-acpi.txt index 570a4f8..12381c1 100644 --- a/Documentation/arm64/arm-acpi.txt +++ b/Documentation/arm64/arm-acpi.txt @@ -57,11 +57,11 @@ The short form of the rationale for ACPI on ARM is: -- The new ACPI governance process works well and Linux is now at the same table as hardware vendors and other OS vendors. In fact, there is no - longer any reason to feel that ACPI is only belongs to Windows or that + longer any reason to feel that ACPI only belongs to Windows or that Linux is in any way secondary to Microsoft in this arena. The move of ACPI governance into the UEFI forum has significantly opened up the specification development process, and currently, a large portion of the - changes being made to ACPI is being driven by Linux. + changes being made to ACPI are being driven by Linux. Key to the use of ACPI is the support model. For servers in general, the responsibility for hardware behaviour cannot solely be the domain of the @@ -159,7 +159,7 @@ Further, the ACPI core will only use the 64-bit address fields in the FADT (Fixed ACPI Description Table). Any 32-bit address fields in the FADT will be ignored on arm64. -Hardware reduced mode (see Section 4.1 of the ACPI 5.1 specification) will +Hardware reduced mode (see Section 4.1 of the ACPI 6.1 specification) will be enforced by the ACPI core on arm64. Doing so allows the ACPI core to run less complex code since it no longer has to provide support for legacy hardware from other architectures. Any fields that are not to be used for @@ -167,7 +167,7 @@ hardware reduced mode must be set to zero. For the ACPI core to operate properly, and in turn provide the information the kernel needs to configure devices, it expects to find the following -tables (all section numbers refer to the ACPI 5.1 specfication): +tables (all section numbers refer to the ACPI 6.1 specfication): -- RSDP (Root System Description Pointer), section 5.2.5 @@ -185,9 +185,22 @@ tables (all section numbers refer to the ACPI 5.1 specfication): -- If PCI is supported, the MCFG (Memory mapped ConFiGuration Table), section 5.2.6, specifically Table 5-31. + -- If booting without a console=<device> kernel parameter is + supported, the SPCR (Serial Port Console Redirection table), + section 5.2.6, specifically Table 5-31. + + -- If virtualization is supported, the IORT (Input Output Remapping + Table, section 5.2.6, specifically Table 5-31. + + -- If NUMA is supported, the SRAT (System Resource Affinity Table) + and SLIT (System Locality distance Information Table), sections + 5.2.16 and 5.2.17, respectively. + If the above tables are not all present, the kernel may or may not be able to boot properly since it may not be able to configure all of the -devices available. +devices available. This list of tables is not meant to be all inclusive; +in some environments other tables may be needed (e.g., any of the APEI +tables from section 18) to support specific functionality. ACPI Detection @@ -233,7 +246,7 @@ that looks like this: Name(KEY0, "value0"). An ACPI device driver would then retrieve the value of the property by evaluating the KEY0 object. However, using Name() this way has multiple problems: (1) ACPI limits names ("KEY0") to four characters unlike DT; (2) there is no industry -wide registry that maintains a list of names, minimzing re-use; (3) +wide registry that maintains a list of names, minimizing re-use; (3) there is also no registry for the definition of property values ("value0"), again making re-use difficult; and (4) how does one maintain backward compatibility as new hardware comes out? The _DSD method was created @@ -434,7 +447,8 @@ The ACPI specification changes regularly. During the year 2014, for instance, version 5.1 was released and version 6.0 substantially completed, with most of the changes being driven by ARM-specific requirements. Proposed changes are presented and discussed in the ASWG (ACPI Specification Working Group) which -is a part of the UEFI Forum. +is a part of the UEFI Forum. The current version of the ACPI specification +is 6.1 release in January 2016. Participation in this group is open to all UEFI members. Please see http://www.uefi.org/workinggroup for details on group membership. -- 2.5.0

9 years, 2 months

1
0
0 0

[PATCH V3 0/4] acpi: cppc optimization patches

by Prashanth Prakash

Changes in V3: Addressed the review comments from Alexey, Ashwin and Timur Changes in V2: Fixed compilation error on i386 This series introduces changes to reduce the time required to send a frequency transition requests to the platform while using the cppc-cpufreq driver. With these changes we see significant improvement in the average time to send freq. transition request to the platform. Profiling on an ARM platform showed that the average transaction time per request reduced from 200us to under 20us. Ashwin Chaugule (1): ACPI / CPPC: Optimize PCC Read Write operations Prashanth Prakash (3): acpi: cppc: optimized cpc_read and cpc_write mailbox: pcc: optimized pcc_send_data acpi: cppc: replace writeX/readX to PCC with relaxed version drivers/acpi/cppc_acpi.c | 183 +++++++++++++++++++++++++++++++++++------------ drivers/mailbox/pcc.c | 111 ++++++++++++++++++++++++++-- 2 files changed, 241 insertions(+), 53 deletions(-) -- Qualcomm Technologies, Inc. on behalf of the Qualcomm Innovation Center, Inc. The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum, a Linux Foundation Collaborative Project.

9 years, 2 months

7
15
0 0

[PATCH v12 0/4] Watchdog: introduce ARM SBSA watchdog driver

by fu.wei＠linaro.org

From: Fu Wei <fu.wei(a)linaro.org> This patchset: (1)Introduce Documentation/devicetree/bindings/watchdog/sbsa-gwdt.txt for FDT info of SBSA Generic Watchdog, and give two examples of adding SBSA Generic Watchdog device node into the dts files: foundation-v8.dts and amd-seattle-soc.dtsi. (2)Introduce ARM SBSA watchdog driver: a.Use linux kernel watchdog framework; b.Work with FDT on ARM64; c.Support getting timeout from parameter and FDT at the driver init stage. d.The driver works in two modes: (1) single stage timeout (ignore WS0 interrupt) (2) two stages timeout (register WS0 interrupt, do panic in routine) e.User can config working mode by module parameter "action". This patchset has been tested with watchdog daemon (ACPI/FDT, module/build-in) on the following platforms: (1)ARM Foundation v8 model (2)AMD Seattle platform This patchset has been tested with kdump successfully. Changelog: v12:Fix a dev_warn message typo Remove unnecessary "status" in dts Add more *ed-by in commit message. v11:https://lkml.org/lkml/2016/2/9/577 Merge patch 4 and 5. Improve some comments. The driver works in two modes, it's configured by "action"(instead of panic_enabled). Improve the initialization of the timeout limits. Feeding dog by writing "0" to WRR. v10:https://lkml.org/lkml/2016/2/3/817 Delete pretimeout support. Separate the driver to two parts: (1) single stage timeout driver(ignore WS0 interrupt); (2) register WS0 interrupt for the half timeout panic. timeout == (enable --> WS1). v9: https://lkml.org/lkml/2015/11/9/57 Rebase to latest kernel version(4.3). Update the Documentation of sbsa-gwdt device node info of FDT: (1) move some introduction to pretimeout patch (2) delete WS1 value from "interrupts" of binding documentation, since WS1 won't be handled by Linux. v8: https://lkml.org/lkml/2015/10/27/466 Rebase to latest kernel version(4.3-rc7). Separate the patches of GTDT support and arm_arch_timer. This clocksource relevant patch will upstreamed in a individual patchset. Update all the default timeout and pretimeout to 30s and 60s. Improve documentation and inline comments. Fix a bug in pretimeout support which makes timeout and pretimeout parameters initialization fail. v7: https://lkml.org/lkml/2015/8/24/611 Rebase to latest kernel version(4.2-rc7). Improve FDT support: geting resource by order, instead of name. According to the FDT support, Update the example dts file, gtdt.c and sbsa_gwdt.c. Pass the sparse test, and fix the warning. Fix the max_pretimeout and max_timeout value overflow bug. Delete the WCV output value. v6: https://lkml.org/lkml/2015/6/23/359 Improve the dtb example files: reduce the register frame size to 4K. Improve pretimeout support: (1) improve watchdog_init_timeouts function (2) rename watchdog_check_min_max_timeouts back to the original name (1) improve watchdog_timeout_invalid/watchdog_pretimeout_invalid Add the new features in the sbsa_gwdt driver: (1) In the second stage, user can feed the dog without cleaning WS0. (2) In the second stage, user can trigger WS1 by setting pretimeout = 0. (3) expand the max value of pretimeout, in case 10 second is not enough for a kdump kernel reboot in panic. v5: https://lkml.org/lkml/2015/6/10/357 Improve pretimeout support: (1)fix typo in documentation and comments. (2)fix the timeout limits validation bug. Simplify sbsa_gwdt driver: (1)integrate all the registers access functions into caller. v4: https://lkml.org/lkml/2015/6/2/4 Refactor GTDT support code: remove it from arch/arm64/kernel/acpi.c, put it into drivers/acpi/gtdt.c file. Integrate the GTDT code of drivers/clocksource/arm_arch_timer.c into drivers/acpi/gtdt.c. Improve pretimeout support, fix "pretimeout == 0" problem. Simplify sbsa_gwdt driver: (1)timeout/pretimeout limits setup; (2)keepalive function; (3)delete "clk == 0" check; (4)delete WS0 status bit check in interrupt routine; (5)sbsa_gwdt_set_wcv function. v3: https://lkml.org/lkml/2015/5/25/111 Delete "export arch_timer_get_rate" patch. Driver back to use arch_timer_get_cntfrq. Improve watchdog_init_timeouts function and update relevant documentation. Improve watchdog_timeout_invalid and watchdog_pretimeout_invalid. Improve foundation-v8.dts: delete the unnecessary tag of device node. Remove "ARM64 || COMPILE_TEST" from Kconfig. Add comments in arch/arm64/kernel/acpi.c Fix typoes and incorrect comments. v2: https://lkml.org/lkml/2015/5/21/172 Improve watchdog-kernel-api.txt documentation for pretimeout support. Export "arch_timer_get_rate" in arm_arch_timer.c. Add watchdog_init_timeouts API for pretimeout support in framework. Improve suspend and resume foundation in driver Improve timeout/pretimeout values init code in driver. Delete unnecessary items of the sbsa_gwdt struct and #define. Delete all unnecessary debug info in driver. Fix 64bit division bug. Use the arch_timer interface to get watchdog clock rate. Add MODULE_DEVICE_TABLE for platform device id. Fix typoes. v1: https://lkml.org/lkml/2015/5/15/279 The first version upstream patchset to linux mailing list. Fu Wei (4): Documentation: add sbsa-gwdt driver documentation ARM64: add SBSA Generic Watchdog device node in foundation-v8.dts ARM64: add SBSA Generic Watchdog device node in amd-seattle-soc.dtsi Watchdog: introduce ARM SBSA watchdog driver .../devicetree/bindings/watchdog/sbsa-gwdt.txt | 31 ++ Documentation/watchdog/watchdog-parameters.txt | 7 + arch/arm64/boot/dts/amd/amd-seattle-soc.dtsi | 8 + arch/arm64/boot/dts/arm/foundation-v8.dts | 7 + drivers/watchdog/Kconfig | 20 + drivers/watchdog/Makefile | 1 + drivers/watchdog/sbsa_gwdt.c | 403 +++++++++++++++++++++ 7 files changed, 477 insertions(+) create mode 100644 Documentation/devicetree/bindings/watchdog/sbsa-gwdt.txt create mode 100644 drivers/watchdog/sbsa_gwdt.c -- 2.5.0

9 years, 2 months

4
13
0 0

[PATCH] ARM64: ACPI: Update documentation for latest specification version

by al.stone＠linaro.org

From: Al Stone <al.stone(a)linaro.org> The ACPI 6.1 specification was recently released at the end of January 2016, but the arm64 kernel documentation for the use of ACPI was written for the 5.1 version of the spec. There were significant additions to the spec that had not yet been mentioned -- for example, the 6.0 mechanisms added to make it easier to define processors and low power idle states, as well as the 6.1 addition allowing regular interrupts (not just from GPIO) be used to signal ACPI general purpose events. This patch reflects going back through and examining the specs in detail and updating content appropriately. Whilst there, a few odds and ends of typos were caught as well. This brings the documentation up to date with ACPI 6.1 for arm64. Signed-off-by: Al Stone <al.stone(a)linaro.org> --- Documentation/arm64/acpi_object_usage.txt | 433 ++++++++++++++++++++++-------- Documentation/arm64/arm-acpi.txt | 28 +- 2 files changed, 346 insertions(+), 115 deletions(-) diff --git a/Documentation/arm64/acpi_object_usage.txt b/Documentation/arm64/acpi_object_usage.txt index a6e1a18..e321235 100644 --- a/Documentation/arm64/acpi_object_usage.txt +++ b/Documentation/arm64/acpi_object_usage.txt @@ -13,13 +13,14 @@ For ACPI on arm64, tables also fall into the following categories: -- Required: DSDT, FADT, GTDT, MADT, MCFG, RSDP, SPCR, XSDT - -- Recommended: BERT, EINJ, ERST, HEST, SSDT + -- Recommended: BERT, EINJ, ERST, HEST, IORT, PCCT, SSDT - -- Optional: BGRT, CPEP, CSRT, DRTM, ECDT, FACS, FPDT, MCHI, MPST, - MSCT, RASF, SBST, SLIT, SPMI, SRAT, TCPA, TPM2, UEFI + -- Optional: BGRT, CPEP, CSRT, DBG2, DRTM, ECDT, FACS, FPDT, MCHI, + MPST, MSCT, NFIT, PMTT, RASF, SBST, SLIT, SPMI, SRAT, STAO, TCPA, + TPM2, UEFI, XENV - -- Not supported: BOOT, DBG2, DBGP, DMAR, ETDT, HPET, IBFT, IVRS, - LPIT, MSDM, RSDT, SLIC, WAET, WDAT, WDRT, WPBT + -- Not supported: BOOT, DBGP, DMAR, ETDT, HPET, IBFT, IVRS, LPIT, + MSDM, OEMx, PSDT, RSDT, SLIC, WAET, WDAT, WDRT, WPBT Table Usage for ARMv8 Linux @@ -50,7 +51,9 @@ CSRT Signature Reserved (signature == "CSRT") DBG2 Signature Reserved (signature == "DBG2") == DeBuG port table 2 == - Microsoft only table, will not be supported. + License has changed and should be usable. Patches are available as of + this writing, but they have not been accepted into the kernel. Optional + if used instead of earlycon=<device> on the command line. DBGP Signature Reserved (signature == "DBGP") == DeBuG Port table == @@ -133,10 +136,11 @@ GTDT Section 5.2.24 (signature == "GTDT") HEST Section 18.3.2 (signature == "HEST") == Hardware Error Source Table == - Until further error source types are defined, use only types 6 (AER - Root Port), 7 (AER Endpoint), 8 (AER Bridge), or 9 (Generic Hardware - Error Source). Firmware first error handling is possible if and only - if Trusted Firmware is being used on arm64. + ARM-specific error sources have been defined; please use those or the + PCI types such as type 6 (AER Root Port), 7 (AER Endpoint), or 8 (AER + Bridge), or use type 9 (Generic Hardware Error Source). Firmware first + error handling is possible if and only if Trusted Firmware is being + used on arm64. Must be supplied if RAS support is provided by the platform. It is recommended this table be supplied. @@ -149,20 +153,26 @@ IBFT Signature Reserved (signature == "IBFT") == iSCSI Boot Firmware Table == Microsoft defined table, support TBD. +IORT Signature Reserved (signature == "IORT") + == Input Output Remapping Table == + arm64 only table, required in order to describe the SMMU and/or ITS + when it is provided by the platform. + IVRS Signature Reserved (signature == "IVRS") == I/O Virtualization Reporting Structure == x86_64 (AMD) only table, will not be supported. LPIT Signature Reserved (signature == "LPIT") == Low Power Idle Table == - x86 only table as of ACPI 5.1; future versions have been adapted for - use with ARM and will be recommended in order to support ACPI power - management. + x86 only table as of ACPI 5.1; starting with ACPI 6.0, processor + descriptions and power states on ARM platforms should use the DSDT + and define processor container devices (_HID ACPI0010, Section 8.4, + and more specifically 8.4.3 and and 8.4.4). MADT Section 5.2.12 (signature == "APIC") == Multiple APIC Description Table == Required for arm64. Only the GIC interrupt controller structures - should be used (types 0xA - 0xE). + should be used (types 0xA - 0xF). MCFG Signature Reserved (signature == "MCFG") == Memory-mapped ConFiGuration space == @@ -176,14 +186,38 @@ MPST Section 5.2.21 (signature == "MPST") == Memory Power State Table == Optional, not currently supported. +MSCT Section 5.2.19 (signature == "MSCT") + == Maximum System Characteristic Table == + Optional, not currently supported. + MSDM Signature Reserved (signature == "MSDM") == Microsoft Data Management table == Microsoft only table, will not be supported. -MSCT Section 5.2.19 (signature == "MSCT") - == Maximum System Characteristic Table == +NFIT Section 5.2.25 (signature == "NFIT") + == NVDIMM Firmware Interface Table == Optional, not currently supported. +OEMx Signature of "OEMx" only + == OEM Specific Tables == + All tables starting with a signature of "OEM" are reserved for OEM + use. Since these are not meant to be of general use but are limited + to very specific end users, they are not recommended for use and are + not supported by the kernel for arm64. + +PCCT Section 14.1 (signature == "PCCT) + == Platform Communications Channel Table == + Recommend for use on arm64, and required when using CPPC to control + power on the platform. + +PMTT Section 5.2.21.12 (signature == "PMTT") + == Platform Memory Topology Table == + Optional, but useful, but not currently supported. + +PSDT Section 5.2.11.3 (signature == "PSDT") + == Persistent System Description Table == + Obsolete table, will not be supported. + RASF Section 5.2.20 (signature == "RASF") == RAS Feature table == Optional, not currently supported. @@ -195,7 +229,7 @@ RSDP Section 5.2.5 (signature == "RSD PTR") RSDT Section 5.2.7 (signature == "RSDT") == Root System Description Table == Since this table can only provide 32-bit addresses, it is deprecated - on arm64, and will not be used. + on arm64, and will not be used. If provided, it will be ignored. SBST Section 5.2.14 (signature == "SBST") == Smart Battery Subsystem Table == @@ -207,7 +241,7 @@ SLIC Signature Reserved (signature == "SLIC") SLIT Section 5.2.17 (signature == "SLIT") == System Locality distance Information Table == - Optional in general, but required for NUMA systems. + Optional in general, but required for arm64 NUMA systems. SPCR Signature Reserved (signature == "SPCR") == Serial Port Console Redirection table == @@ -220,7 +254,7 @@ SPMI Signature Reserved (signature == "SPMI") SRAT Section 5.2.16 (signature == "SRAT") == System Resource Affinity Table == Optional, but if used, only the GICC Affinity structures are read. - To support NUMA, this table is required. + To support arm64 NUMA, this table is required. SSDT Section 5.2.11.2 (signature == "SSDT") == Secondary System Description Table == @@ -235,6 +269,11 @@ SSDT Section 5.2.11.2 (signature == "SSDT") These tables are optional, however. ACPI tables should contain only one DSDT but can contain many SSDTs. +STAO Signature Reserved (signature == "STAO") + == _STA Override table == + Optional, but only necessary in virtualized environments in order to + hide devices from guest OSs. + TCPA Signature Reserved (signature == "TCPA") == Trusted Computing Platform Alliance table == Optional, not currently supported, and may need changes to fully @@ -266,6 +305,10 @@ WPBT Signature Reserved (signature == "WPBT") == Windows Platform Binary Table == Microsoft only table, will not be supported. +XENV Signature Reserved (signature == "XENV") + == Xen project table == + Optional, used only by Xen at present. + XSDT Section 5.2.8 (signature == "XSDT") == eXtended System Description Table == Required for arm64. @@ -273,31 +316,50 @@ XSDT Section 5.2.8 (signature == "XSDT") ACPI Objects ------------ -The expectations on individual ACPI objects are discussed in the list that -follows: +The expectations on individual ACPI objects that are likely to be used are +shown in the list that follows: Name Section Usage for ARMv8 Linux ---- ------------ ------------------------------------------------- +_ACx 11.4.1 Use as needed. + _ADR 6.1.1 Use as needed. +_ALx 11.4.2 Use as needed. + +_ART 11.4.3 Use as needed. + _BBN 6.5.5 Use as needed; PCI-specific. -_BDN 6.5.3 Optional; not likely to be used on arm64. +_CCA 6.2.17 This method must be defined for all bus masters + on arm64 -- there are no assumptions made about + whether such devices are cache coherent or not. + The _CCA value is inherited by all descendants of + these devices so it does not need to be repeated. + Without _CCA on arm64, the kernel does not know what + to do about setting up DMA for the device. + +_CDM 6.2.1 Use as needed, to be used only for processor devices. -_CCA 6.2.17 This method should be defined for all bus masters - on arm64. While cache coherency is assumed, making - it explicit ensures the kernel will set up DMA as - it should. +_CID 6.1.2 Use as needed, see also _HID. -_CDM 6.2.1 Optional, to be used only for processor devices. +_CLS 6.1.3 Use as needed, see also _HID. -_CID 6.1.2 Use as needed. +_CPC 8.4.7.1 Use as needed; power management specific. CPPC is + recommended on arm64. -_CLS 6.1.3 Use as needed. +_CR3 11.4.5 Use as needed. _CRS 6.2.2 Required on arm64. -_DCK 6.5.2 Optional; not likely to be used on arm64. +_CRT 11.4.4 Use as needed. + +_CSD 8.4.2.2 Use as needed, used only in conjuction with _CST. + +_CST 8.4.2.1 Low power idle states (8.4.4) are recommended instead + of C-states. + +_CWS 9.18.6 Use as needed. _DDN 6.1.4 This field can be used for a device name. However, it is meant for DOS device names (e.g., COM1), so be @@ -305,11 +367,11 @@ _DDN 6.1.4 This field can be used for a device name. However, _DEP 6.5.8 Use as needed. -_DIS 6.2.3 Optional, for power management use. +_DIS 6.2.3 Use as needed, for power management use. -_DLM 5.7.5 Optional. +_DLM 5.7.5 Use as needed. -_DMA 6.2.4 Optional. +_DMA 6.2.4 Use as needed. _DSD 6.2.5 To be used with caution. If this object is used, try to use it within the constraints already defined by the @@ -325,19 +387,29 @@ _DSD 6.2.5 To be used with caution. If this object is used, try with the UEFI Forum; this may cause some iteration as more than one OS will be registering entries. -_DSM Do not use this method. It is not standardized, the +_DSM 9.1.1 Do not use this method. It is not standardized, the return values are not well documented, and it is currently a frequent source of error. -_DSW 7.2.1 Use as needed; power management specific. +_DSW 7.3.1 Use as needed; power management specific. -_EDL 6.3.1 Optional. +_DTI 11.4.6 Use as needed. -_EJD 6.3.2 Optional. +_EDL 6.3.1 Use as needed. -_EJx 6.3.3 Optional. +_EJD 6.3.2 Use as needed. -_FIX 6.2.7 x86 specific, not used on arm64. +_EJx 6.3.3 Use as needed. + +_FIF 11.3.1.1 Use as needed. + +_FPS 11.3.1.2 Use as needed. + +_FSL 11.3.1.3 Use as needed. + +_FST 11.3.1.4 Use as needed. + +_GCP 9.18.2 Use as needed. \_GL 5.7.1 This object is not to be used in hardware reduced mode, and therefore should not be used on arm64. @@ -349,35 +421,56 @@ _GLK 6.5.7 This object requires a global lock be defined; there \_GPE 5.3.1 This namespace is for x86 use only. Do not use it on arm64. -_GSB 6.2.7 Optional. +_GRT 9.18.3 Use as needed. + +_GSB 6.2.7 Use as needed. + +_GTF 9.9.1.1 Use as needed. + +_GWS 9.18.5 Use as needed. _HID 6.1.5 Use as needed. This is the primary object to use in device probing, though _CID and _CLS may also be used. -_HPP 6.2.8 Optional, PCI specific. +_HOT 11.4.7 Use as needed. + +_HPP 6.2.8 Use as needed, PCI specific. -_HPX 6.2.9 Optional, PCI specific. +_HPX 6.2.9 Use as needed, PCI specific. -_HRV 6.1.6 Optional, use as needed to clarify device behavior; in +_HRV 6.1.6 Use as needed, use as needed to clarify device behavior; in some cases, this may be easier to use than _DSD. _INI 6.5.1 Not required, but can be useful in setting up devices when UEFI leaves them in a state that may not be what the driver expects before it starts probing. -_IRC 7.2.15 Use as needed; power management specific. +_IRC 7.3.15 Use as needed; power management specific. + +_LCK 6.3.4 Use as needed. + +_LPI 8.4.4.3 Use as needed, but recommended for use with processor + definitions (_HID ACPI0010) on arm64. -_LCK 6.3.4 Optional. +_MAT 6.2.10 Use as needed; see also the MADT. -_MAT 6.2.10 Optional; see also the MADT. +_MBM 9.13.2.1 Use as needed. -_MLS 6.1.7 Optional, but highly recommended for use in +_MLS 6.1.7 Use as needed, but highly recommended for use in internationalization. -_OFF 7.1.2 It is recommended to define this method for any device +_MSG 9.2.2 Use as needed. + +_MSM 9.13.2.2 Use as needed. + +_MTL 11.4.8 Use as needed. + +_NTT 11.4.9 Use as needed. + +_OFF 7.2.2 It is recommended to define this method for any device that can be turned on or off. -_ON 7.1.3 It is recommended to define this method for any device +_ON 7.2.3 It is recommended to define this method for any device that can be turned on or off. \_OS 5.7.3 This method will return "Linux" by default (this is @@ -405,115 +498,219 @@ _OSC 6.2.11 This method can be a global method in ACPI (i.e., being used or what functionality is provided. The _OSC method is to be used instead. -_OST 6.3.5 Optional. +_OST 6.3.5 Use as needed. + +_PCT 8.4.6.1 Use as needed; power management specific. _PDC 8.4.1 Deprecated, do not use on arm64. +_PDL 8.4.6.2 Use as needed; power management specific. + \_PIC 5.8.1 The method should not be used. On arm64, the only interrupt model available is GIC. -_PLD 6.1.8 Optional. +_PLD 6.1.8 Use as needed. + +_PPC 8.4.6.3 Use as needed; power management specific. + +_PPE 8.4.8 Use as needed. \_PR 5.3.1 This namespace is for x86 use only on legacy systems. Do not use it on arm64. -_PRS 6.2.12 Optional. +_PRE 7.3.12 Use as needed; power management specific. + +_PRR 7.3.26 Use as needed; power management specific. + +_PRS 6.2.12 Use as needed. _PRT 6.2.13 Required as part of the definition of all PCI root devices. -_PRW 7.2.13 Use as needed; power management specific. +_PRW 7.3.13 Use as needed; power management specific. -_PRx 7.2.8-11 Use as needed; power management specific. If _PR0 is +_PRx 7.3.8-11 Use as needed; power management specific. If _PR0 is defined, _PR3 must also be defined. -_PSC 7.2.6 Use as needed; power management specific. +_PSC 7.3.6 Use as needed; power management specific. + +_PSD 8.4.6.5 Use as needed; power management specific. -_PSE 7.2.7 Use as needed; power management specific. +_PSE 7.3.7 Use as needed; power management specific. -_PSW 7.2.14 Use as needed; power management specific. +_PSL 11.4.10 Use as needed. -_PSx 7.2.2-5 Use as needed; power management specific. If _PS0 is +_PSS 8.4.6.2 Use as needed; power management specific. + +_PSV 11.4.11 Use as needed. + +_PSW 7.3.14 Use as needed; power management specific. + +_PSx 7.3.2-5 Use as needed; power management specific. If _PS0 is defined, _PS3 must also be defined. If clocks or regulators need adjusting to be consistent with power usage, change them in these methods. -\_PTS 7.3.1 Use as needed; power management specific. +_PTC 8.4.5.1 Use as needed; power management specific. + +\_PTS 7.4.1 Use as needed; power management specific. + +_PUR 8.5.1.1 Use as needed. + +_PXM 6.2.14 Use as needed. -_PXM 6.2.14 Optional. +_RDI 8.4.4.4 Use as needed, but recommended for use with processor + definitions (_HID ACPI0010) on arm64. _REG 6.5.4 Use as needed. \_REV 5.7.4 Always returns the latest version of ACPI supported. -_RMV 6.3.6 Optional. +_RMV 6.3.6 Use as needed. + +_RST 7.3.25 Use as needed; power management specific. + +_RTV 11.4.12 Use as needed. \_SB 5.3.1 Required on arm64; all devices must be defined in this namespace. +_SCP 11.4.13 Use as needed. + +_SDD 9.9.3.3.1 Use as needed. + _SEG 6.5.6 Use as needed; PCI-specific. -\_SI 5.3.1, Optional. - 9.1 +\_SI 5.3.1, Use as needed. + 9.2 + +_SLI 6.2.15 Use as needed; recommended when SLIT table is in use. -_SLI 6.2.15 Optional; recommended when SLIT table is in use. +_SRT 9.18.4 Use as needed. _STA 6.3.7, It is recommended to define this method for any device - 7.1.4 that can be turned on or off. + 7.2.4 that can be turned on or off. See also the STAO table + that provides overrides to hide devices in virtualized + environments. -_SRS 6.2.16 Optional; see also _PRS. +_SRS 6.2.16 Use as needed; see also _PRS. + +_SST 9.2.1 Use as needed. _STR 6.1.10 Recommended for conveying device names to end users; this is preferred over using _DDN. +_SST 9.2.1 Use as needed. + +_STP 9.18.7 Use as needed. + +_STV 9.18.8 Use as needed. + _SUB 6.1.9 Use as needed; _HID or _CID are preferred. -_SUN 6.1.11 Optional. +_SUN 6.1.11 Use as needed, but recommended. -\_Sx 7.3.2 Use as needed; power management specific. +\_Sx 7.4.2 Use as needed; power management specific. -_SxD 7.2.16-19 Use as needed; power management specific. +_SxD 7.3.16-19 Use as needed; power management specific. -_SxW 7.2.20-24 Use as needed; power management specific. +_SxW 7.3.20-24 Use as needed; power management specific. -_SWS 7.3.3 Use as needed; power management specific; this may +_SWS 7.4.3 Use as needed; power management specific; this may require specification changes for use on arm64. -\_TTS 7.3.4 Use as needed; power management specific. +_TC1 11.4.14 Use as needed. + +_TC2 11.4.15 Use as needed. + +_TDL 8.4.5.5 Use as needed; power management specific. + +_TFP 11.4.16 Use as needed. + +_TIP 9.18.9 Use as needed. + +_TIV 9.18.10 Use as needed. + +_TMP 11.4.17 Use as needed. + +_TPC 8.4.5.3 Use as needed; power management specific. -\_TZ 5.3.1 Optional. +_TPT 11.4.18 Use as needed. + +_TRT 11.4.19 Use as needed. + +_TSD 8.4.5.4 Use as needed; power management specific. + +_TSN 11.4.20 Use as needed. + +_TSP 11.4.21 Use as needed. + +_TSS 8.4.5.2 Use as needed; power management specific. + +_TST 11.4.22 Use as needed. + +\_TTS 7.4.4 Use as needed; power management specific. + +\_TZ 5.3.1 Use as needed. + +_TZD 11.4.23 Use as needed. + +_TZM 11.4.24 Use as needed. + +_TZP 11.4.25 Use as needed. _UID 6.1.12 Recommended for distinguishing devices of the same class; define it if at all possible. -\_WAK 7.3.5 Use as needed; power management specific. +_UPC 9.14 Use as needed. + +\_WAK 7.4.5 Use as needed; power management specific. + + ACPI Event Model ---------------- Do not use GPE block devices; these are not supported in the hardware reduced profile used by arm64. Since there are no GPE blocks defined for use on ARM -platforms, GPIO-signaled interrupts should be used for creating system events. +platforms, ACPI events must be signaled differently. + +There are two options: GPIO-signaled interrupts (Section 5.6.5), and +interrupt-signaled events (Section 5.6.9). Interrupt-signaled events are a +new feature in the ACPI 6.1 specification. Either -- or both -- can be used +on a given platform, and which to use may be dependent of limitations in any +given SoC. If possible, interrupt-signaled events are recommended. ACPI Processor Control ---------------------- -Section 8 of the ACPI specification is currently undergoing change that -should be completed in the 6.0 version of the specification. Processor -performance control will be handled differently for arm64 at that point -in time. Processor aggregator devices (section 8.5) will not be used, -for example, but another similar mechanism instead. - -While UEFI constrains what we can say until the release of 6.0, it is -recommended that CPPC (8.4.5) be used as the primary model. This will -still be useful into the future. C-states and P-states will still be -provided, but most of the current design work appears to favor CPPC. +Section 8 of the ACPI specification changed significantly in version 6.0. +Processors should now be defined as Device objects with _HID ACPI0007; do +not use the deprecated Processor statement in ASL. All multiprocessor systems +should also define a hierarchy of processors, done with Processor Container +Devices (see Section 8.4.3.1, _HID ACPI0010); do not use processor aggregator +devices (Section 8.5) to describe processor topology. Section 8.4 of the +specification describes the semantics of these object definitions and how +they interrelate. + +Most importantly, the processor hierarchy defined also defines the low power +idle states that are available to the platform, along with the rules for +determining which processors can be turned on or off and the circumstances +that control that. Without this information, the processors will run in +whatever power state they were left in by UEFI. + +Note too, that the processor Device objects defined and the entries in the +MADT for GICs are expected to be in sychronization. The _UID of the Device +object must correspond to processor IDs used in the MADT. + +It is recommended that CPPC (8.4.5) be used as the primary model for processor +performance control on arm64. C-states and P-states may become available at +some point in the future, but most current design work appears to favor CPPC. Further, it is essential that the ARMv8 SoC provide a fully functional implementation of PSCI; this will be the only mechanism supported by ACPI -to control CPU power state (including secondary CPU booting). - -More details will be provided on the release of the ACPI 6.0 specification. +to control CPU power state. Booting of secondary CPUs may be possible using +parking protocol, but only PSCI is to be used for ARM servers. ACPI System Address Map Interfaces @@ -535,21 +732,25 @@ used to indicate fatal errors that cannot be corrected, and require immediate attention. Since there is no direct equivalent of the x86 SCI or NMI, arm64 handles -these slightly differently. The SCI is handled as a normal GPIO-signaled -interrupt; given that these are corrected (or correctable) errors being -reported, this is sufficient. The NMI is emulated as the highest priority -GPIO-signaled interrupt possible. This implies some caution must be used -since there could be interrupts at higher privilege levels or even interrupts -at the same priority as the emulated NMI. In Linux, this should not be the -case but one should be aware it could happen. +these slightly differently. The SCI is handled as a high priority interrupt; +given that these are corrected (or correctable) errors being reported, this +is sufficient. The NMI is emulated as the highest priority interrupt +possible. This implies some caution must be used since there could be +interrupts at higher privilege levels or even interrupts at the same priority +as the emulated NMI. In Linux, this should not be the case but one should +be aware it could happen. ACPI Objects Not Supported on ARM64 ----------------------------------- While this may change in the future, there are several classes of objects that can be defined, but are not currently of general interest to ARM servers. +Some of these objects have x86 equivalents, and may actually make sense in ARM +servers. However, there is either no hardware available at present, or there +may not even be a non-ARM implementation yet. Hence, they are not currently +supported. -These are not supported: +The following classes of objects are not supported: -- Section 9.2: ambient light sensor devices @@ -571,16 +772,6 @@ These are not supported: -- Section 9.18: time and alarm devices (see 9.15) - -ACPI Objects Not Yet Implemented --------------------------------- -While these objects have x86 equivalents, and they do make some sense in ARM -servers, there is either no hardware available at present, or in some cases -there may not yet be a non-ARM implementation. Hence, they are currently not -implemented though that may change in the future. - -Not yet implemented are: - -- Section 10: power source and power meter devices -- Section 11: thermal management @@ -589,5 +780,31 @@ Not yet implemented are: -- Section 13: SMBus interfaces - -- Section 17: NUMA support (prototypes have been submitted for - review) + +This also mean that there is no support for the following objects: + +Name Section Name Section +---- ------------ ---- ------------ +_ALC 9.3.4 _FDM 9.10.3 +_ALI 9.3.2 _FIX 6.2.7 +_ALP 9.3.6 _GAI 10.4.5 +_ALR 9.3.5 _GHL 10.4.7 +_ALT 9.3.3 _GTM 9.9.2.1.1 +_BCT 10.2.2.10 _LID 9.5.1 +_BDN 6.5.3 _PAI 10.4.4 +_BIF 10.2.2.1 _PCL 10.3.2 +_BIX 10.2.2.1 _PIF 10.3.3 +_BLT 9.2.3 _PMC 10.4.1 +_BMA 10.2.2.4 _PMD 10.4.8 +_BMC 10.2.2.12 _PMM 10.4.3 +_BMD 10.2.2.11 _PRL 10.3.4 +_BMS 10.2.2.5 _PSR 10.3.1 +_BST 10.2.2.6 _PTP 10.4.2 +_BTH 10.2.2.7 _SBS 10.1.3 +_BTM 10.2.2.9 _SHL 10.4.6 +_BTP 10.2.2.8 _STM 9.9.2.1.1 +_DCK 6.5.2 _UPD 9.16.1 +_EC 12.12 _UPP 9.16.2 +_FDE 9.10.1 _WPC 10.5.2 +_FDI 9.10.2 _WPP 10.5.3 + diff --git a/Documentation/arm64/arm-acpi.txt b/Documentation/arm64/arm-acpi.txt index 570a4f8..12381c1 100644 --- a/Documentation/arm64/arm-acpi.txt +++ b/Documentation/arm64/arm-acpi.txt @@ -57,11 +57,11 @@ The short form of the rationale for ACPI on ARM is: -- The new ACPI governance process works well and Linux is now at the same table as hardware vendors and other OS vendors. In fact, there is no - longer any reason to feel that ACPI is only belongs to Windows or that + longer any reason to feel that ACPI only belongs to Windows or that Linux is in any way secondary to Microsoft in this arena. The move of ACPI governance into the UEFI forum has significantly opened up the specification development process, and currently, a large portion of the - changes being made to ACPI is being driven by Linux. + changes being made to ACPI are being driven by Linux. Key to the use of ACPI is the support model. For servers in general, the responsibility for hardware behaviour cannot solely be the domain of the @@ -159,7 +159,7 @@ Further, the ACPI core will only use the 64-bit address fields in the FADT (Fixed ACPI Description Table). Any 32-bit address fields in the FADT will be ignored on arm64. -Hardware reduced mode (see Section 4.1 of the ACPI 5.1 specification) will +Hardware reduced mode (see Section 4.1 of the ACPI 6.1 specification) will be enforced by the ACPI core on arm64. Doing so allows the ACPI core to run less complex code since it no longer has to provide support for legacy hardware from other architectures. Any fields that are not to be used for @@ -167,7 +167,7 @@ hardware reduced mode must be set to zero. For the ACPI core to operate properly, and in turn provide the information the kernel needs to configure devices, it expects to find the following -tables (all section numbers refer to the ACPI 5.1 specfication): +tables (all section numbers refer to the ACPI 6.1 specfication): -- RSDP (Root System Description Pointer), section 5.2.5 @@ -185,9 +185,22 @@ tables (all section numbers refer to the ACPI 5.1 specfication): -- If PCI is supported, the MCFG (Memory mapped ConFiGuration Table), section 5.2.6, specifically Table 5-31. + -- If booting without a console=<device> kernel parameter is + supported, the SPCR (Serial Port Console Redirection table), + section 5.2.6, specifically Table 5-31. + + -- If virtualization is supported, the IORT (Input Output Remapping + Table, section 5.2.6, specifically Table 5-31. + + -- If NUMA is supported, the SRAT (System Resource Affinity Table) + and SLIT (System Locality distance Information Table), sections + 5.2.16 and 5.2.17, respectively. + If the above tables are not all present, the kernel may or may not be able to boot properly since it may not be able to configure all of the -devices available. +devices available. This list of tables is not meant to be all inclusive; +in some environments other tables may be needed (e.g., any of the APEI +tables from section 18) to support specific functionality. ACPI Detection @@ -233,7 +246,7 @@ that looks like this: Name(KEY0, "value0"). An ACPI device driver would then retrieve the value of the property by evaluating the KEY0 object. However, using Name() this way has multiple problems: (1) ACPI limits names ("KEY0") to four characters unlike DT; (2) there is no industry -wide registry that maintains a list of names, minimzing re-use; (3) +wide registry that maintains a list of names, minimizing re-use; (3) there is also no registry for the definition of property values ("value0"), again making re-use difficult; and (4) how does one maintain backward compatibility as new hardware comes out? The _DSD method was created @@ -434,7 +447,8 @@ The ACPI specification changes regularly. During the year 2014, for instance, version 5.1 was released and version 6.0 substantially completed, with most of the changes being driven by ARM-specific requirements. Proposed changes are presented and discussed in the ASWG (ACPI Specification Working Group) which -is a part of the UEFI Forum. +is a part of the UEFI Forum. The current version of the ACPI specification +is 6.1 release in January 2016. Participation in this group is open to all UEFI members. Please see http://www.uefi.org/workinggroup for details on group membership. -- 2.5.0

9 years, 2 months

4
3
0 0

Firmware Test Suite 16.02.00 is released

by ivanhu

FWTS 16.02.00 is released. It is available from: Tar: http://fwts.ubuntu.com/release/fwts-V16.02.00.tar.gz PPA: https://launchpad.net/~firmware-testing-team/+archive/ubuntu/ppa-fwts-stable Release notes: https://wiki.ubuntu.com/FirmwareTestSuite/ReleaseNotes/16.02.00 = Significant Updates = * ACPICA: Update to version 20160212 (LP: #1545099) = New Features = * Full ACPI compliance testing for the FADT * FADT: enable compiling on non-x86 architectures * FADT: non-x86 machines need an FADT but x86 can survive without one * FADT: disable SCI_EN and RESET_REG tests when in reduced hardware mode * FADT: add in code to log basic info about the various FADT flag fields * Add in bit masks for FACS flags. * FADT: move log info out of test2, will provide it elsewhere * ACPI: Add hypervisor ID field to FADT. * FADT: minor cleanup and initial compliance tests * FADT: expand the compliance test for FIRMWARE_CTRL fields * FADT: expand compliance checks for DSDT and X_DSDT fields * FADT: add compliance tests for reserved fields, PM profile, reduced hardware * FADT: restructure test sequence around reduced hardware mode * FADT: expand compliance tests for the SMI_CMD field * FADT: add compliance tests for the ACPI_ENABLE and ACPI_DISABLE fields * FADT: add compliance tests for S4BIOS_REQ and PSTATE_CNT fields * FADT: extend and add PM address block compliance tests * FADT: enhance compliance tests for GPE blocks * FADT: add compliance test for the CST_CNT field * FADT: add in compliance tests for C2/C3 latency fields * FADT: add in SLEEP_CONTROL_REG and SLEEP_STATUS_REG compliance tests * FADT: remove no longer useful variables from test1 * FADT: add safety checks for older versions of FADT * acpi: method: add _PMC test * acpi: method: add _PRT test * acpi: method: add _RDI test * acpi: method: add _LPI test * data: klog.json: update to sync with 4.6 kernel changes = Fixed Bugs = * Start defining FWTS architectures as variables * Define some utility functions for using the fwts_architecture enum * Add mechanism to tell FWTS what architecture is being tested * ACPI: MADT: add in compliance tests for the MADT and subtables * ACPI: Add in MADT subtable description for GIC ITS subtable * ACPI: MADT: add in compliance checks for the GIC ITS subtable * Documentation: add --acpicompliance to man page * Documentation: add --arch to the man page * Update ACPI RSDP tests to be specification compliant * RSDP: minor cleanups to rsdp.c for checkpatch issues * utilities: add a helper function for printing out architecture names * ACPI tables: when bodging up an RSDP, do the right thing for the arch * ACPI RSDP: flesh out the tests to check for full spec compliance. * acpi: method: remove non-method names from the top comments * acpi: fadt: check 32/64 bit PM register addresses for inconsistency (LP: #1536606) * acpi: erst: fix incorrect error message for reserved field * lib: fwts_klog: fix incorrect indentation, detected by gcc-6 * lib: fwts_hwinfo: clean up type punning, fixes warning with gcc-6 * fwts: wakealarm: reset wakealarm timer at end of test (LP: #1534003) * dmi: dmicheck: add some simple sanity checks to table size * lib: fwts_args: use safer strncat than strcat * lib: fwts_acpi_tables: don't do expensive low allocs multiple times * acpi: madt: fix incorrect format specifier for size_t * cpu: microcode: fix a couple of warnings found by cppcheck: * acpi: madt: clean up some minor style issues detected by cppcheck * lib: fwts_acpi_tables: fix warnings found by clang scan-build * lib: fwts_cpu: check for MSR read failures * lib: fwts_klog: handle the case where klog_old is empty list * acpica: fix disassembly on i386 platforms (LP: #1547469) * lib: fwts_arch: i686 arch name is also an X86 arch (LP: #1547554) * Fix null_gass initializer for older versions of gcc (LP: #1549429) = Detail Changelog = To check /usr/share/doc/fwts/changelog.Debian.gz or fwts_16.02.00-0ubuntu1.debian.tar.gz from https://launchpad.net/ubuntu/+source/fwts

9 years, 2 months

1
0
0 0

Fwd: [PATCH] IORT: Add in support for the SMMUv3 subtable

by Al Stone

Whups. I should have sent a copy of this to this list also... -------- Forwarded Message -------- Subject: [PATCH] IORT: Add in support for the SMMUv3 subtable Date: Wed, 24 Feb 2016 18:01:14 -0700 From: Al Stone <al.stone(a)linaro.org> To: devel(a)acpica.org CC: Al Stone <al.stone(a)linaro.org> The most recent version of the IORT specification adds in a definition for a subtable to describe SMMUv3 devices; there is already a subtable for SMMUv1/v2 devices. Add in the definition of the subtable, add in the code to compile it, and add in a template for it. Signed-off-by: Al Stone <al.stone(a)linaro.org> --- source/common/dmtbdump.c | 6 ++++++ source/common/dmtbinfo.c | 19 +++++++++++++++++++ source/compiler/dttable1.c | 17 +++++++++++++++-- source/compiler/dttemplate.h | 15 +++++++++++---- source/include/acdisasm.h | 1 + source/include/actbl2.h | 25 +++++++++++++++++++++++-- 6 files changed, 75 insertions(+), 8 deletions(-) diff --git a/source/common/dmtbdump.c b/source/common/dmtbdump.c index ce3b45b..bf09e58 100644 --- a/source/common/dmtbdump.c +++ b/source/common/dmtbdump.c @@ -1845,6 +1845,12 @@ AcpiDmDumpIort ( IortSmmu = ACPI_ADD_PTR (ACPI_IORT_SMMU, IortNode, NodeOffset); break; + case ACPI_IORT_NODE_SMMU_V3: + + InfoTable = AcpiDmTableInfoIort4; + Length = IortNode->Length - NodeOffset; + break; + default: AcpiOsPrintf ("\n**** Unknown IORT node type 0x%X\n", diff --git a/source/common/dmtbinfo.c b/source/common/dmtbinfo.c index be95f92..5edb8d4 100644 --- a/source/common/dmtbinfo.c +++ b/source/common/dmtbinfo.c @@ -242,6 +242,7 @@ #define ACPI_IORT1_OFFSET(f) (UINT16) ACPI_OFFSET (ACPI_IORT_NAMED_COMPONENT,f) #define ACPI_IORT2_OFFSET(f) (UINT16) ACPI_OFFSET (ACPI_IORT_ROOT_COMPLEX,f) #define ACPI_IORT3_OFFSET(f) (UINT16) ACPI_OFFSET (ACPI_IORT_SMMU,f) +#define ACPI_IORT4_OFFSET(f) (UINT16) ACPI_OFFSET (ACPI_IORT_SMMU_V3,f) #define ACPI_IORTA_OFFSET(f) (UINT16) ACPI_OFFSET (ACPI_IORT_MEMORY_ACCESS,f) #define ACPI_IORTH_OFFSET(f) (UINT16) ACPI_OFFSET (ACPI_IORT_NODE,f) #define ACPI_IORTM_OFFSET(f) (UINT16) ACPI_OFFSET (ACPI_IORT_ID_MAPPING,f) @@ -328,6 +329,7 @@ #define ACPI_GTDT0a_FLAG_OFFSET(f,o) ACPI_FLAG_OFFSET (ACPI_GTDT_TIMER_ENTRY,f,o) #define ACPI_GTDT1_FLAG_OFFSET(f,o) ACPI_FLAG_OFFSET (ACPI_GTDT_WATCHDOG,f,o) #define ACPI_IORT3_FLAG_OFFSET(f,o) ACPI_FLAG_OFFSET (ACPI_IORT_SMMU,f,o) +#define ACPI_IORT4_FLAG_OFFSET(f,o) ACPI_FLAG_OFFSET (ACPI_IORT_SMMU_V3,f,o) #define ACPI_IORTA_FLAG_OFFSET(f,o) ACPI_FLAG_OFFSET (ACPI_IORT_MEMORY_ACCESS,f,o) #define ACPI_IORTM_FLAG_OFFSET(f,o) ACPI_FLAG_OFFSET (ACPI_IORT_ID_MAPPING,f,o) #define ACPI_LPITH_FLAG_OFFSET(f,o) ACPI_FLAG_OFFSET (ACPI_LPIT_HEADER,f,o) @@ -1633,6 +1635,23 @@ ACPI_DMTABLE_INFO AcpiDmTableInfoIort3c[] = ACPI_DMT_TERMINATOR }; +/* 0x04: SMMUv3 */ + +ACPI_DMTABLE_INFO AcpiDmTableInfoIort4[] = +{ + {ACPI_DMT_UINT64, ACPI_IORT4_OFFSET (BaseAddress), "Base Address", 0}, + {ACPI_DMT_UINT32, ACPI_IORT4_OFFSET (Flags), "Flags (decoded below)", 0}, + {ACPI_DMT_FLAG0, ACPI_IORT4_FLAG_OFFSET (Flags, 0), "COHACC Override", 0}, + {ACPI_DMT_FLAG1, ACPI_IORT4_FLAG_OFFSET (Flags, 0), "HTTU Override", 0}, + {ACPI_DMT_UINT32, ACPI_IORT4_OFFSET (Reserved), "Reserved", 0}, + {ACPI_DMT_UINT64, ACPI_IORT4_OFFSET (VatosAddress), "VATOS Address", 0}, + {ACPI_DMT_UINT32, ACPI_IORT4_OFFSET (Model), "Model", 0}, + {ACPI_DMT_UINT32, ACPI_IORT4_OFFSET (EventGsiv), "Event GSIV", 0}, + {ACPI_DMT_UINT32, ACPI_IORT4_OFFSET (PriGsiv), "PRI GSIV", 0}, + {ACPI_DMT_UINT32, ACPI_IORT4_OFFSET (GerrGsiv), "GERR GSIV", 0}, + {ACPI_DMT_UINT32, ACPI_IORT4_OFFSET (SyncGsiv), "Sync GSIV", 0}, + ACPI_DMT_TERMINATOR +}; /******************************************************************************* * diff --git a/source/compiler/dttable1.c b/source/compiler/dttable1.c index ada7fca..cacd9de 100644 --- a/source/compiler/dttable1.c +++ b/source/compiler/dttable1.c @@ -1315,8 +1315,8 @@ DtCompileIort ( DtInsertSubtable (ParentTable, Subtable); /* - * Using ACPI_SUB_PTR, We needn't define a seperate structure. Care - * should be taken to avoid accessing ACPI_TABLE_HADER fields. + * Using ACPI_SUB_PTR, We needn't define a separate structure. Care + * should be taken to avoid accessing ACPI_TABLE_HEADER fields. */ Iort = ACPI_SUB_PTR (ACPI_TABLE_IORT, Subtable->Buffer, sizeof (ACPI_TABLE_HEADER)); @@ -1547,6 +1547,19 @@ DtCompileIort ( IortSmmu->PmuInterruptCount = PmuIrptNumber; break; + case ACPI_IORT_NODE_SMMU_V3: + + Status = DtCompileTable (PFieldList, AcpiDmTableInfoIort4, + &Subtable, TRUE); + if (ACPI_FAILURE (Status)) + { + return (Status); + } + + DtInsertSubtable (ParentTable, Subtable); + NodeLength += Subtable->Length; + break; + default: DtFatal (ASL_MSG_UNKNOWN_SUBTABLE, SubtableStart, "IORT"); diff --git a/source/compiler/dttemplate.h b/source/compiler/dttemplate.h index f27a77a..71f0041 100644 --- a/source/compiler/dttemplate.h +++ b/source/compiler/dttemplate.h @@ -615,11 +615,11 @@ const unsigned char TemplateHpet[] = const unsigned char TemplateIort[] = { - 0x49,0x4F,0x52,0x54,0x0C,0x01,0x00,0x00, /* 00000000 "IORT...." */ - 0x00,0xBC,0x49,0x4E,0x54,0x45,0x4C,0x20, /* 00000008 "..INTEL " */ + 0x49,0x4F,0x52,0x54,0x48,0x01,0x00,0x00, /* 00000000 "IORTH..." */ + 0x00,0x02,0x49,0x4E,0x54,0x45,0x4C,0x20, /* 00000008 "..INTEL " */ 0x54,0x45,0x4D,0x50,0x4C,0x41,0x54,0x45, /* 00000010 "TEMPLATE" */ 0x00,0x00,0x00,0x00,0x49,0x4E,0x54,0x4C, /* 00000018 "....INTL" */ - 0x10,0x04,0x15,0x20,0x04,0x00,0x00,0x00, /* 00000020 "... ...." */ + 0x12,0x02,0x16,0x20,0x05,0x00,0x00,0x00, /* 00000020 "... ...." */ 0x34,0x00,0x00,0x00,0x00,0x00,0x00,0x00, /* 00000028 "4......." */ 0x00,0x00,0x00,0x00,0x00,0x2C,0x00,0x00, /* 00000030 ".....,.." */ 0x00,0x00,0x00,0x00,0x01,0x00,0x00,0x00, /* 00000038 "........" */ @@ -648,7 +648,14 @@ const unsigned char TemplateIort[] = 0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00, /* 000000F0 "........" */ 0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00, /* 000000F8 "........" */ 0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00, /* 00000100 "........" */ - 0x00,0x00,0x00,0x00 /* 00000108 "...." */ + 0x00,0x00,0x00,0x00,0x04,0x3C,0x00,0x00, /* 00000108 ".....<.." */ + 0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00, /* 00000110 "........" */ + 0x3C,0x00,0x00,0x00,0x00,0x00,0x00,0x00, /* 00000118 "<......." */ + 0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00, /* 00000120 "........" */ + 0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00, /* 00000128 "........" */ + 0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00, /* 00000130 "........" */ + 0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00, /* 00000138 "........" */ + 0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00 /* 00000140 "........" */ }; const unsigned char TemplateIvrs[] = diff --git a/source/include/acdisasm.h b/source/include/acdisasm.h index f949a8b..f962370 100644 --- a/source/include/acdisasm.h +++ b/source/include/acdisasm.h @@ -391,6 +391,7 @@ extern ACPI_DMTABLE_INFO AcpiDmTableInfoIort3[]; extern ACPI_DMTABLE_INFO AcpiDmTableInfoIort3a[]; extern ACPI_DMTABLE_INFO AcpiDmTableInfoIort3b[]; extern ACPI_DMTABLE_INFO AcpiDmTableInfoIort3c[]; +extern ACPI_DMTABLE_INFO AcpiDmTableInfoIort4[]; extern ACPI_DMTABLE_INFO AcpiDmTableInfoIortAcc[]; extern ACPI_DMTABLE_INFO AcpiDmTableInfoIortHdr[]; extern ACPI_DMTABLE_INFO AcpiDmTableInfoIortMap[]; diff --git a/source/include/actbl2.h b/source/include/actbl2.h index 1cac3dc..8311e7f 100644 --- a/source/include/actbl2.h +++ b/source/include/actbl2.h @@ -834,7 +834,7 @@ typedef struct acpi_ibft_target * IORT - IO Remapping Table * * Conforms to "IO Remapping Table System Software on ARM Platforms", - * Document number: ARM DEN 0049A, 2015 + * Document number: ARM DEN 0049B, October 2015 * ******************************************************************************/ @@ -870,7 +870,8 @@ enum AcpiIortNodeType ACPI_IORT_NODE_ITS_GROUP = 0x00, ACPI_IORT_NODE_NAMED_COMPONENT = 0x01, ACPI_IORT_NODE_PCI_ROOT_COMPLEX = 0x02, - ACPI_IORT_NODE_SMMU = 0x03 + ACPI_IORT_NODE_SMMU = 0x03, + ACPI_IORT_NODE_SMMU_V3 = 0x04 }; @@ -979,6 +980,26 @@ typedef struct acpi_iort_smmu #define ACPI_IORT_SMMU_COHERENT_WALK (1<<1) +typedef struct acpi_iort_smmu_v3 +{ + UINT64 BaseAddress; /* SMMUv3 base address */ + UINT32 Flags; + UINT32 Reserved; + UINT64 VatosAddress; + UINT32 Model; /* O: generic SMMUv3 */ + UINT32 EventGsiv; + UINT32 PriGsiv; + UINT32 GerrGsiv; + UINT32 SyncGsiv; + +} ACPI_IORT_SMMU_V3; + +/* Masks for Flags field above */ + +#define ACPI_IORT_SMMU_V3_COHACC_OVERRIDE (1) +#define ACPI_IORT_SMMU_V3_HTTU_OVERRIDE (1<<1) + + /******************************************************************************* * * IVRS - I/O Virtualization Reporting Structure -- 2.5.0

9 years, 2 months

1
0
0 0

Re: [Linaro-acpi] [PATCH v3 2/5] ACPI: parse SPCR and enable matching console

by Itaru Kitayama

The updated topic-acpi-console branch kernel with Lorenzo's acpi parking protocol patch applied booted fine on Mustang with the new Beta F/W.

9 years, 2 months

2
1
0 0

[PATCH v3 0/6] acpi, clocksource, kvm: add GTDT and ARM memory-mapped timer support

by fu.wei＠linaro.org

From: Fu Wei <fu.wei(a)linaro.org> This patchset: (1)Introduce ACPI GTDT parser: drivers/acpi/gtdt.c Parse all kinds of timer in GTDT table of ACPI:arch timer, memory-mapped timer and SBSA Generic Watchdog timer. This driver can help to simplify all the relevant timer drivers, and separate all the ACPI GTDT knowledge from them. (2)Simplify ACPI code for arch timer in arm_arch_timer.c (3)Add memory-mapped timer support in arm_arch_timer.c (4)Add arm_arch_timer get ppi from DT and GTDT support for kvm in virt/kvm/arm/arch_timer.c Changelog: v3: Improve GTDT driver code: (1)improve pr_* by defining pr_fmt(fmt) (2)simplify gtdt_sbsa_gwdt_init (3)improve gtdt_arch_timer_data_init, if table is NULL, it will try to get GTDT table. Move enum ppi_nr to arm_arch_timer.h, and add enum spi_nr. Add arm_arch_timer get ppi from DT and GTDT support for kvm. v2: https://lkml.org/lkml/2015/12/2/10 Rebase to latest kernel version(4.4-rc3). Fix the bug about the config problem, use CONFIG_ACPI_GTDT instead of CONFIG_ACPI in arm_arch_timer.c v1: The first upstreaming version: https://lkml.org/lkml/2015/10/28/553 Fu Wei (5): ACPI: add GTDT table parse driver into ACPI driver clocksource: simplify ACPI code in arm_arch_timer.c clocksource: add memory-mapped timer support in arm_arch_timer.c clocksource: move some enums to arm_arch_timer.h kvm: arm64: Add ACPI support for virt arch timer Wei Huang (1): kvm: arm64: wrapping DT support for virt arch timer drivers/acpi/Kconfig | 9 + drivers/acpi/Makefile | 1 + drivers/acpi/gtdt.c | 375 +++++++++++++++++++++++++++++++++++ drivers/clocksource/Kconfig | 1 + drivers/clocksource/arm_arch_timer.c | 191 +++++++++++++----- include/clocksource/arm_arch_timer.h | 33 +++ include/linux/acpi.h | 17 ++ virt/kvm/arm/arch_timer.c | 57 ++++-- 8 files changed, 620 insertions(+), 64 deletions(-) create mode 100644 drivers/acpi/gtdt.c -- 2.5.0

9 years, 2 months

4
9
0 0

[PATCH v2 00/23] Full ACPI compliance testing for the FADT

by Al Stone

This constitutes a major rewrite and restructuring of the FADT tests for ACPI. There is now a compliance test for every field that we can test. Some we cannot test since any possible value in the field is also an allowed value. In some cases, the tests are an extension of existing tests -- for the PM blocks, SMI_CMD and the GPE blocks, for example. In the rest, these are new tests, and all of these are part of what used to be a much smaller test1. The original test2 and test3 are almost entirely intact since they did some solid testing of semantics across several related fields. The largest structural change is around reduced hardware mode. There is now a test specific to that mode verifying that all of the fields in the FADT that are to be ignored are set to zero. Further, tests that are irrelevant to reduced hardware mode are skipped when we have tables in that mode. Some of the patches are simply to enable compiling the FADT tests on non-x86 architectures; they were completely disabled previously. I did attempt to break up the patches into reasonable chunks but some of them still may have ended up fairly large. This has been tested on arm64 and x86-64, using arm64 and x86 ACPI tables. I am sure the testing has not been exhaustive; there are a *lot* of fields in the FADT. Changes for v2: -- Print out the SEALED_CASE flag (Colin Ian King) -- Relax the revision test a little (Alex Hung) -- Simplify/clarify testing of DSDT/X_DSDT fields (Alex Hung) -- New patch: add in safety checks for many of the fields that may not occur in older FADTs (spurred by comments from Alex Hung) -- New patch: update regression tests (Colin Ian King) -- Add in Acked-bys, but only if there were NO changes to the prior version of the patch (patches 4/23, 8/23, 10/23, 22-23/23 are the only ones without Acked-bys). Al Stone (23): FADT: enable compiling on non-x86 architectures FADT: non-x86 machines need an FADT but x86 can survive without one FADT: disable SCI_EN and RESET_REG tests when in reduced hardware mode FADT: add in code to log basic info about the various FADT flag fields Add in bit masks for FACS flags. FADT: move log info out of test2, will provide it elsewhere ACPI: Add hypervisor ID field to FADT. FADT: minor cleanup and initial compliance tests FADT: expand the compliance test for FIRMWARE_CTRL fields FADT: expand compliance checks for DSDT and X_DSDT fields FADT: add compliance tests for reserved fields, PM profile, reduced hardware FADT: restructure test sequence around reduced hardware mode FADT: expand compliance tests for the SMI_CMD field FADT: add compliance tests for the ACPI_ENABLE and ACPI_DISABLE fields FADT: add compliance tests for S4BIOS_REQ and PSTATE_CNT fields FADT: extend and add PM address block compliance tests FADT: enhance compliance tests for GPE blocks FADT: add compliance test for the CST_CNT field FADT: add in compliance tests for C2/C3 latency fields FADT: add in SLEEP_CONTROL_REG and SLEEP_STATUS_REG compliance tests FADT: remove no longer useful variables from test1 FADT: add safety checks for older versions of FADT FADT: update regression tests to incorporate new/changed tests .../arg-show-tests-0001/arg-show-tests-0001.log | 1 + .../arg-show-tests-full-0001.log | 21 +- src/acpi/fadt/fadt.c | 1796 +++++++++++++++++--- src/lib/include/fwts_acpi.h | 35 + 4 files changed, 1595 insertions(+), 258 deletions(-) -- 2.5.0

9 years, 2 months

1
23
0 0

[PATCH v13 0/4] Watchdog: introduce ARM SBSA watchdog driver

by fu.wei＠linaro.org

From: Fu Wei <fu.wei(a)linaro.org> This patchset: (1)Introduce Documentation/devicetree/bindings/watchdog/sbsa-gwdt.txt for FDT info of SBSA Generic Watchdog, and give two examples of adding SBSA Generic Watchdog device node into the dts files: foundation-v8.dts and amd-seattle-soc.dtsi. (2)Introduce ARM SBSA watchdog driver: a.Use linux kernel watchdog framework; b.Work with FDT on ARM64; c.Support getting timeout from parameter and FDT at the driver init stage. d.The driver works in two modes: (1) single stage timeout (ignore WS0 interrupt) (2) two stages timeout (register WS0 interrupt, do panic in routine) e.User can config working mode by module parameter "action". This patchset has been tested with watchdog daemon (ACPI/FDT, module/build-in) on the following platforms: (1)ARM Foundation v8 model (2)AMD Seattle platform This patchset has been tested with kdump successfully. Changelog: v13:Fix a dev_warn message typo"signle"-->"single" Add MODULE_ALIAS Add more *ed-by in commit message. v12:https://lkml.org/lkml/2016/2/16/154 Fix a dev_warn message typo"fall"--"falling" Remove unnecessary "status" in dts Add more *ed-by in commit message. v11:https://lkml.org/lkml/2016/2/9/577 Merge patch 4 and 5. Improve some comments. The driver works in two modes, it's configured by "action"(instead of panic_enabled). Improve the initialization of the timeout limits. Feeding dog by writing "0" to WRR. v10:https://lkml.org/lkml/2016/2/3/817 Delete pretimeout support. Separate the driver to two parts: (1) single stage timeout driver(ignore WS0 interrupt); (2) register WS0 interrupt for the half timeout panic. timeout == (enable --> WS1). v9: https://lkml.org/lkml/2015/11/9/57 Rebase to latest kernel version(4.3). Update the Documentation of sbsa-gwdt device node info of FDT: (1) move some introduction to pretimeout patch (2) delete WS1 value from "interrupts" of binding documentation, since WS1 won't be handled by Linux. v8: https://lkml.org/lkml/2015/10/27/466 Rebase to latest kernel version(4.3-rc7). Separate the patches of GTDT support and arm_arch_timer. This clocksource relevant patch will upstreamed in a individual patchset. Update all the default timeout and pretimeout to 30s and 60s. Improve documentation and inline comments. Fix a bug in pretimeout support which makes timeout and pretimeout parameters initialization fail. v7: https://lkml.org/lkml/2015/8/24/611 Rebase to latest kernel version(4.2-rc7). Improve FDT support: geting resource by order, instead of name. According to the FDT support, Update the example dts file, gtdt.c and sbsa_gwdt.c. Pass the sparse test, and fix the warning. Fix the max_pretimeout and max_timeout value overflow bug. Delete the WCV output value. v6: https://lkml.org/lkml/2015/6/23/359 Improve the dtb example files: reduce the register frame size to 4K. Improve pretimeout support: (1) improve watchdog_init_timeouts function (2) rename watchdog_check_min_max_timeouts back to the original name (1) improve watchdog_timeout_invalid/watchdog_pretimeout_invalid Add the new features in the sbsa_gwdt driver: (1) In the second stage, user can feed the dog without cleaning WS0. (2) In the second stage, user can trigger WS1 by setting pretimeout = 0. (3) expand the max value of pretimeout, in case 10 second is not enough for a kdump kernel reboot in panic. v5: https://lkml.org/lkml/2015/6/10/357 Improve pretimeout support: (1)fix typo in documentation and comments. (2)fix the timeout limits validation bug. Simplify sbsa_gwdt driver: (1)integrate all the registers access functions into caller. v4: https://lkml.org/lkml/2015/6/2/4 Refactor GTDT support code: remove it from arch/arm64/kernel/acpi.c, put it into drivers/acpi/gtdt.c file. Integrate the GTDT code of drivers/clocksource/arm_arch_timer.c into drivers/acpi/gtdt.c. Improve pretimeout support, fix "pretimeout == 0" problem. Simplify sbsa_gwdt driver: (1)timeout/pretimeout limits setup; (2)keepalive function; (3)delete "clk == 0" check; (4)delete WS0 status bit check in interrupt routine; (5)sbsa_gwdt_set_wcv function. v3: https://lkml.org/lkml/2015/5/25/111 Delete "export arch_timer_get_rate" patch. Driver back to use arch_timer_get_cntfrq. Improve watchdog_init_timeouts function and update relevant documentation. Improve watchdog_timeout_invalid and watchdog_pretimeout_invalid. Improve foundation-v8.dts: delete the unnecessary tag of device node. Remove "ARM64 || COMPILE_TEST" from Kconfig. Add comments in arch/arm64/kernel/acpi.c Fix typoes and incorrect comments. v2: https://lkml.org/lkml/2015/5/21/172 Improve watchdog-kernel-api.txt documentation for pretimeout support. Export "arch_timer_get_rate" in arm_arch_timer.c. Add watchdog_init_timeouts API for pretimeout support in framework. Improve suspend and resume foundation in driver Improve timeout/pretimeout values init code in driver. Delete unnecessary items of the sbsa_gwdt struct and #define. Delete all unnecessary debug info in driver. Fix 64bit division bug. Use the arch_timer interface to get watchdog clock rate. Add MODULE_DEVICE_TABLE for platform device id. Fix typoes. v1: https://lkml.org/lkml/2015/5/15/279 The first version upstream patchset to linux mailing list. Fu Wei (4): Documentation: add sbsa-gwdt driver documentation ARM64: add SBSA Generic Watchdog device node in foundation-v8.dts ARM64: add SBSA Generic Watchdog device node in amd-seattle-soc.dtsi Watchdog: introduce ARM SBSA watchdog driver .../devicetree/bindings/watchdog/sbsa-gwdt.txt | 31 ++ Documentation/watchdog/watchdog-parameters.txt | 7 + arch/arm64/boot/dts/amd/amd-seattle-soc.dtsi | 8 + arch/arm64/boot/dts/arm/foundation-v8.dts | 7 + drivers/watchdog/Kconfig | 20 + drivers/watchdog/Makefile | 1 + drivers/watchdog/sbsa_gwdt.c | 404 +++++++++++++++++++++ 7 files changed, 478 insertions(+) create mode 100644 Documentation/devicetree/bindings/watchdog/sbsa-gwdt.txt create mode 100644 drivers/watchdog/sbsa_gwdt.c -- 2.5.0

9 years, 2 months

2
5
0 0

[PATCH 00/21] Full ACPI compliance testing for the FADT

by Al Stone

This constitutes a major rewrite and restructuring of the FADT tests for ACPI. There is now a compliance test for every field that we can test. Some we cannot test since any possible value in the field is also an allowed value. In some cases, the tests are an extension of existing tests -- for the PM blocks, SMI_CMD and the GPE blocks, for example. In the rest, these are new tests, and all of these are part of what used to be a much smaller test1. The original test2 and test3 are almost entirely intact since they did some solid testing of semantics across several related fields. The largest structural change is around reduced hardware mode. There is now a test specific to that mode verifying that all of the fields in the FADT that are to be ignored are set to zero. Further, tests that are irrelevant to reduced hardware mode are skipped when we have tables in that mode. Some of the patches are simply to enable compiling the FADT tests on non-x86 architectures; they were completely disabled previously. I did attempt to break up the patches into reasonable chunks but some of them still may have ended up fairly large. This has been tested on arm64 and x86-64, using arm64 and x86 ACPI tables. I am sure the testing has not been exhaustive; there are a *lot* of fields in the FADT. Al Stone (21): FADT: enable compiling on non-x86 architectures FADT: non-x86 machines need an FADT but x86 can survive without one FADT: disable SCI_EN and RESET_REG tests when in reduced hardware mode FADT: add in code to log basic info about the various FADT flag fields Add in bit masks for FACS flags. FADT: move log info out of test2, will provide it elsewhere ACPI: Add hypervisor ID field to FADT. FADT: minor cleanup and initial compliance tests FADT: expand the compliance test for FIRMWARE_CTRL fields FADT: expand compliance checks for DSDT and X_DSDT fields FADT: add compliance tests for reserved fields, PM profile, reduced hardware FADT: restructure test sequence around reduced hardware mode FADT: expand compliance tests for the SMI_CMD field FADT: add compliance tests for the ACPI_ENABLE and ACPI_DISABLE fields FADT: add compliance tests for S4BIOS_REQ and PSTATE_CNT fields FADT: extend and add PM address block compliance tests FADT: enhance compliance tests for GPE blocks FADT: add compliance test for the CST_CNT field FADT: add in compliance tests for C2/C3 latency fields FADT: add in SLEEP_CONTROL_REG and SLEEP_STATUS_REG compliance tests FADT: remove no longer useful variables from test1 src/acpi/fadt/fadt.c | 1718 ++++++++++++++++++++++++++++++++++++------- src/lib/include/fwts_acpi.h | 35 + 2 files changed, 1499 insertions(+), 254 deletions(-) -- 2.5.0

9 years, 2 months

3
48
0 0

leg-kernel tag leg-20160216.0 released

by Graeme Gregory

The leg-kernel release has been made and tagged as leg-201600216.0 This is based on mainline kernel v4.5-rc4 Repository : http://git.linaro.org/leg/acpi/leg-kernel.git Direct Link: https://git.linaro.org/leg/acpi/leg-kernel.git/commit/be063f18ad780f20de7f1… Topic Branches :- http://git.linaro.org/leg/acpi/acpi.git - topic-pci [topic-pci-20160215.0] - topic-numa [topic-numa-20160216.0] - topic-amba-probing [topic-amba-probing-20160216.0] - topic-acpi-console [topic-acpi-console-20160215.0] - topic-gtdt-wakeup-timer [topic-gtdt-wakeup-timer-20160216.0] - topic-fvp [topic-fvp-20160216.0] - topic-kvm-acpi [topic-kvm-acpi-20160216.0] - topic-sbsa-watchdog [topic-sbsa-watchdog-20160216.0] - topic-apei [topic-apei-20160216.0] http://git.linaro.org/leg/acpi/leg-kernel.git - leg-configs [leg-configs-20150216.0] NOTES:-

9 years, 2 months

1
0
0 0

[PATCH v11 0/4] Watchdog: introduce ARM SBSA watchdog driver

by fu.wei＠linaro.org

From: Fu Wei <fu.wei(a)linaro.org> This patchset: (1)Introduce Documentation/devicetree/bindings/watchdog/sbsa-gwdt.txt for FDT info of SBSA Generic Watchdog, and give two examples of adding SBSA Generic Watchdog device node into the dts files: foundation-v8.dts and amd-seattle-soc.dtsi. (2)Introduce ARM SBSA watchdog driver: a.Use linux kernel watchdog framework; b.Work with FDT on ARM64; c.Support getting timeout from parameter and FDT at the driver init stage. d.The driver works in two modes: (1) single stage timeout (ignore WS0 interrupt) (2) two stages timeout (register WS0 interrupt, do panic in routine) e.User can config working mode by module parameter "action". This patchset has been tested with watchdog daemon (ACPI/FDT, module/build-in) on the following platforms: (1)ARM Foundation v8 model (2)AMD Seattle platform This patchset has been tested with kdump successfully. Changelog: v11:Merge patch 4 and 5. Improve some comments. The driver works in two modes, it's configured by "action"(instead of panic_enabled). Improve the initialization of the timeout limits. Feeding dog by writing "0" to WRR. v10:https://lkml.org/lkml/2016/2/3/817 Delete pretimeout support. Separate the driver to two parts: (1) single stage timeout driver(ignore WS0 interrupt); (2) register WS0 interrupt for the half timeout panic. timeout == (enable --> WS1). v9: https://lkml.org/lkml/2015/11/9/57 Rebase to latest kernel version(4.3). Update the Documentation of sbsa-gwdt device node info of FDT: (1) move some introduction to pretimeout patch (2) delete WS1 value from "interrupts" of binding documentation, since WS1 won't be handled by Linux. v8: https://lkml.org/lkml/2015/10/27/466 Rebase to latest kernel version(4.3-rc7). Separate the patches of GTDT support and arm_arch_timer. This clocksource relevant patch will upstreamed in a individual patchset. Update all the default timeout and pretimeout to 30s and 60s. Improve documentation and inline comments. Fix a bug in pretimeout support which makes timeout and pretimeout parameters initialization fail. v7: https://lkml.org/lkml/2015/8/24/611 Rebase to latest kernel version(4.2-rc7). Improve FDT support: geting resource by order, instead of name. According to the FDT support, Update the example dts file, gtdt.c and sbsa_gwdt.c. Pass the sparse test, and fix the warning. Fix the max_pretimeout and max_timeout value overflow bug. Delete the WCV output value. v6: https://lkml.org/lkml/2015/6/23/359 Improve the dtb example files: reduce the register frame size to 4K. Improve pretimeout support: (1) improve watchdog_init_timeouts function (2) rename watchdog_check_min_max_timeouts back to the original name (1) improve watchdog_timeout_invalid/watchdog_pretimeout_invalid Add the new features in the sbsa_gwdt driver: (1) In the second stage, user can feed the dog without cleaning WS0. (2) In the second stage, user can trigger WS1 by setting pretimeout = 0. (3) expand the max value of pretimeout, in case 10 second is not enough for a kdump kernel reboot in panic. v5: https://lkml.org/lkml/2015/6/10/357 Improve pretimeout support: (1)fix typo in documentation and comments. (2)fix the timeout limits validation bug. Simplify sbsa_gwdt driver: (1)integrate all the registers access functions into caller. v4: https://lkml.org/lkml/2015/6/2/4 Refactor GTDT support code: remove it from arch/arm64/kernel/acpi.c, put it into drivers/acpi/gtdt.c file. Integrate the GTDT code of drivers/clocksource/arm_arch_timer.c into drivers/acpi/gtdt.c. Improve pretimeout support, fix "pretimeout == 0" problem. Simplify sbsa_gwdt driver: (1)timeout/pretimeout limits setup; (2)keepalive function; (3)delete "clk == 0" check; (4)delete WS0 status bit check in interrupt routine; (5)sbsa_gwdt_set_wcv function. v3: https://lkml.org/lkml/2015/5/25/111 Delete "export arch_timer_get_rate" patch. Driver back to use arch_timer_get_cntfrq. Improve watchdog_init_timeouts function and update relevant documentation. Improve watchdog_timeout_invalid and watchdog_pretimeout_invalid. Improve foundation-v8.dts: delete the unnecessary tag of device node. Remove "ARM64 || COMPILE_TEST" from Kconfig. Add comments in arch/arm64/kernel/acpi.c Fix typoes and incorrect comments. v2: https://lkml.org/lkml/2015/5/21/172 Improve watchdog-kernel-api.txt documentation for pretimeout support. Export "arch_timer_get_rate" in arm_arch_timer.c. Add watchdog_init_timeouts API for pretimeout support in framework. Improve suspend and resume foundation in driver Improve timeout/pretimeout values init code in driver. Delete unnecessary items of the sbsa_gwdt struct and #define. Delete all unnecessary debug info in driver. Fix 64bit division bug. Use the arch_timer interface to get watchdog clock rate. Add MODULE_DEVICE_TABLE for platform device id. Fix typoes. v1: https://lkml.org/lkml/2015/5/15/279 The first version upstream patchset to linux mailing list. Fu Wei (4): Documentation: add sbsa-gwdt driver documentation ARM64: add SBSA Generic Watchdog device node in foundation-v8.dts ARM64: add SBSA Generic Watchdog device node in amd-seattle-soc.dtsi Watchdog: introduce ARM SBSA watchdog driver .../devicetree/bindings/watchdog/sbsa-gwdt.txt | 35 ++ Documentation/watchdog/watchdog-parameters.txt | 7 + arch/arm64/boot/dts/amd/amd-seattle-soc.dtsi | 9 + arch/arm64/boot/dts/arm/foundation-v8.dts | 8 + drivers/watchdog/Kconfig | 20 + drivers/watchdog/Makefile | 1 + drivers/watchdog/sbsa_gwdt.c | 403 +++++++++++++++++++++ 7 files changed, 483 insertions(+) create mode 100644 Documentation/devicetree/bindings/watchdog/sbsa-gwdt.txt create mode 100644 drivers/watchdog/sbsa_gwdt.c -- 2.5.0

9 years, 2 months

5
10
0 0

[PATCH v2 0/5] Update ACPI RSDP tests to be specification compliant

by Al Stone

Add in several tests that extend the testing done on the RSDP. If these tests are all passed, the RSDP being examined should be compliant with the ACPI 6.0 spec. As part of that, when creating a dummy RSDP to substitute for one that cannot be read or found, use either RsdtAddress or XsdtAddress as described in the spec. For non-arm64, either can be used, but for arm64, only the XsdtAddress is to be used. Finally, update the regression tests for RSDP. Changes for v2: -- Clean up failure messages to be more like expected messages (per Alex Hung) -- Bodge up both RSDT and XSDT pointers on x86 (Alex Hung) Al Stone (5): RSDP: minor cleanups to rsdp.c for checkpatch issues utilities: add a helper function for printing out architecture names ACPI tables: when bodging up an RSDP, do the right thing for the arch ACPI RSDP: flesh out the tests to check for full spec compliance. Update regression test rsdp-0001/test-0001.sh fwts-test/rsdp-0001/rsdp.log | 17 ++++- src/acpi/rsdp/rsdp.c | 158 +++++++++++++++++++++++++++++++++++++---- src/lib/include/fwts_arch.h | 1 + src/lib/src/fwts_acpi_tables.c | 25 ++++--- src/lib/src/fwts_arch.c | 18 +++++ 5 files changed, 195 insertions(+), 24 deletions(-) -- 2.5.0

9 years, 2 months

2
6
0 0

[RFC PATCH] ARM64: ACPI: Update documentation for latest specification version

by Al Stone

NB: I'm only sending this to a small audience for now to get some initial feedback. If I've missed someone you think might be useful, feel free to pass this on. The ACPI 6.1 specification was recently released at the end of January 2016, but the arm64 kernel documentation for the use of ACPI was written for the 5.1 version of the spec. There were significant additions to the spec that had not yet been mentioned -- for example, the 6.0 mechanisms added to make it easier to define processors and low power idle states, as well as the 6.1 addition allowing regular interrupts (not just from GPIO) be used to signal ACPI general purpose events. This patch reflects going back through and examining the specs in detail and updating content appropriately. Whilst there, a few odds and ends of typos were caught as well. This brings the documentation up to date with ACPI 6.1 for arm64. Signed-off-by: Al Stone <al.stone(a)linaro.org> --- Documentation/arm64/acpi_object_usage.txt | 433 ++++++++++++++++++++++-------- Documentation/arm64/arm-acpi.txt | 28 +- 2 files changed, 346 insertions(+), 115 deletions(-) diff --git a/Documentation/arm64/acpi_object_usage.txt b/Documentation/arm64/acpi_object_usage.txt index a6e1a18..e321235 100644 --- a/Documentation/arm64/acpi_object_usage.txt +++ b/Documentation/arm64/acpi_object_usage.txt @@ -13,13 +13,14 @@ For ACPI on arm64, tables also fall into the following categories: -- Required: DSDT, FADT, GTDT, MADT, MCFG, RSDP, SPCR, XSDT - -- Recommended: BERT, EINJ, ERST, HEST, SSDT + -- Recommended: BERT, EINJ, ERST, HEST, IORT, PCCT, SSDT - -- Optional: BGRT, CPEP, CSRT, DRTM, ECDT, FACS, FPDT, MCHI, MPST, - MSCT, RASF, SBST, SLIT, SPMI, SRAT, TCPA, TPM2, UEFI + -- Optional: BGRT, CPEP, CSRT, DBG2, DRTM, ECDT, FACS, FPDT, MCHI, + MPST, MSCT, NFIT, PMTT, RASF, SBST, SLIT, SPMI, SRAT, STAO, TCPA, + TPM2, UEFI, XENV - -- Not supported: BOOT, DBG2, DBGP, DMAR, ETDT, HPET, IBFT, IVRS, - LPIT, MSDM, RSDT, SLIC, WAET, WDAT, WDRT, WPBT + -- Not supported: BOOT, DBGP, DMAR, ETDT, HPET, IBFT, IVRS, LPIT, + MSDM, OEMx, PSDT, RSDT, SLIC, WAET, WDAT, WDRT, WPBT Table Usage for ARMv8 Linux @@ -50,7 +51,9 @@ CSRT Signature Reserved (signature == "CSRT") DBG2 Signature Reserved (signature == "DBG2") == DeBuG port table 2 == - Microsoft only table, will not be supported. + License has changed and should be usable. Patches are available as of + this writing, but they have not been accepted into the kernel. Optional + if used instead of earlycon=<device> on the command line. DBGP Signature Reserved (signature == "DBGP") == DeBuG Port table == @@ -133,10 +136,11 @@ GTDT Section 5.2.24 (signature == "GTDT") HEST Section 18.3.2 (signature == "HEST") == Hardware Error Source Table == - Until further error source types are defined, use only types 6 (AER - Root Port), 7 (AER Endpoint), 8 (AER Bridge), or 9 (Generic Hardware - Error Source). Firmware first error handling is possible if and only - if Trusted Firmware is being used on arm64. + ARM-specific error sources have been defined; please use those or the + PCI types such as type 6 (AER Root Port), 7 (AER Endpoint), or 8 (AER + Bridge), or use type 9 (Generic Hardware Error Source). Firmware first + error handling is possible if and only if Trusted Firmware is being + used on arm64. Must be supplied if RAS support is provided by the platform. It is recommended this table be supplied. @@ -149,20 +153,26 @@ IBFT Signature Reserved (signature == "IBFT") == iSCSI Boot Firmware Table == Microsoft defined table, support TBD. +IORT Signature Reserved (signature == "IORT") + == Input Output Remapping Table == + arm64 only table, required in order to describe the SMMU and/or ITS + when it is provided by the platform. + IVRS Signature Reserved (signature == "IVRS") == I/O Virtualization Reporting Structure == x86_64 (AMD) only table, will not be supported. LPIT Signature Reserved (signature == "LPIT") == Low Power Idle Table == - x86 only table as of ACPI 5.1; future versions have been adapted for - use with ARM and will be recommended in order to support ACPI power - management. + x86 only table as of ACPI 5.1; starting with ACPI 6.0, processor + descriptions and power states on ARM platforms should use the DSDT + and define processor container devices (_HID ACPI0010, Section 8.4, + and more specifically 8.4.3 and and 8.4.4). MADT Section 5.2.12 (signature == "APIC") == Multiple APIC Description Table == Required for arm64. Only the GIC interrupt controller structures - should be used (types 0xA - 0xE). + should be used (types 0xA - 0xF). MCFG Signature Reserved (signature == "MCFG") == Memory-mapped ConFiGuration space == @@ -176,14 +186,38 @@ MPST Section 5.2.21 (signature == "MPST") == Memory Power State Table == Optional, not currently supported. +MSCT Section 5.2.19 (signature == "MSCT") + == Maximum System Characteristic Table == + Optional, not currently supported. + MSDM Signature Reserved (signature == "MSDM") == Microsoft Data Management table == Microsoft only table, will not be supported. -MSCT Section 5.2.19 (signature == "MSCT") - == Maximum System Characteristic Table == +NFIT Section 5.2.25 (signature == "NFIT") + == NVDIMM Firmware Interface Table == Optional, not currently supported. +OEMx Signature of "OEMx" only + == OEM Specific Tables == + All tables starting with a signature of "OEM" are reserved for OEM + use. Since these are not meant to be of general use but are limited + to very specific end users, they are not recommended for use and are + not supported by the kernel for arm64. + +PCCT Section 14.1 (signature == "PCCT) + == Platform Communications Channel Table == + Recommend for use on arm64, and required when using CPPC to control + power on the platform. + +PMTT Section 5.2.21.12 (signature == "PMTT") + == Platform Memory Topology Table == + Optional, but useful, but not currently supported. + +PSDT Section 5.2.11.3 (signature == "PSDT") + == Persistent System Description Table == + Obsolete table, will not be supported. + RASF Section 5.2.20 (signature == "RASF") == RAS Feature table == Optional, not currently supported. @@ -195,7 +229,7 @@ RSDP Section 5.2.5 (signature == "RSD PTR") RSDT Section 5.2.7 (signature == "RSDT") == Root System Description Table == Since this table can only provide 32-bit addresses, it is deprecated - on arm64, and will not be used. + on arm64, and will not be used. If provided, it will be ignored. SBST Section 5.2.14 (signature == "SBST") == Smart Battery Subsystem Table == @@ -207,7 +241,7 @@ SLIC Signature Reserved (signature == "SLIC") SLIT Section 5.2.17 (signature == "SLIT") == System Locality distance Information Table == - Optional in general, but required for NUMA systems. + Optional in general, but required for arm64 NUMA systems. SPCR Signature Reserved (signature == "SPCR") == Serial Port Console Redirection table == @@ -220,7 +254,7 @@ SPMI Signature Reserved (signature == "SPMI") SRAT Section 5.2.16 (signature == "SRAT") == System Resource Affinity Table == Optional, but if used, only the GICC Affinity structures are read. - To support NUMA, this table is required. + To support arm64 NUMA, this table is required. SSDT Section 5.2.11.2 (signature == "SSDT") == Secondary System Description Table == @@ -235,6 +269,11 @@ SSDT Section 5.2.11.2 (signature == "SSDT") These tables are optional, however. ACPI tables should contain only one DSDT but can contain many SSDTs. +STAO Signature Reserved (signature == "STAO") + == _STA Override table == + Optional, but only necessary in virtualized environments in order to + hide devices from guest OSs. + TCPA Signature Reserved (signature == "TCPA") == Trusted Computing Platform Alliance table == Optional, not currently supported, and may need changes to fully @@ -266,6 +305,10 @@ WPBT Signature Reserved (signature == "WPBT") == Windows Platform Binary Table == Microsoft only table, will not be supported. +XENV Signature Reserved (signature == "XENV") + == Xen project table == + Optional, used only by Xen at present. + XSDT Section 5.2.8 (signature == "XSDT") == eXtended System Description Table == Required for arm64. @@ -273,31 +316,50 @@ XSDT Section 5.2.8 (signature == "XSDT") ACPI Objects ------------ -The expectations on individual ACPI objects are discussed in the list that -follows: +The expectations on individual ACPI objects that are likely to be used are +shown in the list that follows: Name Section Usage for ARMv8 Linux ---- ------------ ------------------------------------------------- +_ACx 11.4.1 Use as needed. + _ADR 6.1.1 Use as needed. +_ALx 11.4.2 Use as needed. + +_ART 11.4.3 Use as needed. + _BBN 6.5.5 Use as needed; PCI-specific. -_BDN 6.5.3 Optional; not likely to be used on arm64. +_CCA 6.2.17 This method must be defined for all bus masters + on arm64 -- there are no assumptions made about + whether such devices are cache coherent or not. + The _CCA value is inherited by all descendants of + these devices so it does not need to be repeated. + Without _CCA on arm64, the kernel does not know what + to do about setting up DMA for the device. + +_CDM 6.2.1 Use as needed, to be used only for processor devices. -_CCA 6.2.17 This method should be defined for all bus masters - on arm64. While cache coherency is assumed, making - it explicit ensures the kernel will set up DMA as - it should. +_CID 6.1.2 Use as needed, see also _HID. -_CDM 6.2.1 Optional, to be used only for processor devices. +_CLS 6.1.3 Use as needed, see also _HID. -_CID 6.1.2 Use as needed. +_CPC 8.4.7.1 Use as needed; power management specific. CPPC is + recommended on arm64. -_CLS 6.1.3 Use as needed. +_CR3 11.4.5 Use as needed. _CRS 6.2.2 Required on arm64. -_DCK 6.5.2 Optional; not likely to be used on arm64. +_CRT 11.4.4 Use as needed. + +_CSD 8.4.2.2 Use as needed, used only in conjuction with _CST. + +_CST 8.4.2.1 Low power idle states (8.4.4) are recommended instead + of C-states. + +_CWS 9.18.6 Use as needed. _DDN 6.1.4 This field can be used for a device name. However, it is meant for DOS device names (e.g., COM1), so be @@ -305,11 +367,11 @@ _DDN 6.1.4 This field can be used for a device name. However, _DEP 6.5.8 Use as needed. -_DIS 6.2.3 Optional, for power management use. +_DIS 6.2.3 Use as needed, for power management use. -_DLM 5.7.5 Optional. +_DLM 5.7.5 Use as needed. -_DMA 6.2.4 Optional. +_DMA 6.2.4 Use as needed. _DSD 6.2.5 To be used with caution. If this object is used, try to use it within the constraints already defined by the @@ -325,19 +387,29 @@ _DSD 6.2.5 To be used with caution. If this object is used, try with the UEFI Forum; this may cause some iteration as more than one OS will be registering entries. -_DSM Do not use this method. It is not standardized, the +_DSM 9.1.1 Do not use this method. It is not standardized, the return values are not well documented, and it is currently a frequent source of error. -_DSW 7.2.1 Use as needed; power management specific. +_DSW 7.3.1 Use as needed; power management specific. -_EDL 6.3.1 Optional. +_DTI 11.4.6 Use as needed. -_EJD 6.3.2 Optional. +_EDL 6.3.1 Use as needed. -_EJx 6.3.3 Optional. +_EJD 6.3.2 Use as needed. -_FIX 6.2.7 x86 specific, not used on arm64. +_EJx 6.3.3 Use as needed. + +_FIF 11.3.1.1 Use as needed. + +_FPS 11.3.1.2 Use as needed. + +_FSL 11.3.1.3 Use as needed. + +_FST 11.3.1.4 Use as needed. + +_GCP 9.18.2 Use as needed. \_GL 5.7.1 This object is not to be used in hardware reduced mode, and therefore should not be used on arm64. @@ -349,35 +421,56 @@ _GLK 6.5.7 This object requires a global lock be defined; there \_GPE 5.3.1 This namespace is for x86 use only. Do not use it on arm64. -_GSB 6.2.7 Optional. +_GRT 9.18.3 Use as needed. + +_GSB 6.2.7 Use as needed. + +_GTF 9.9.1.1 Use as needed. + +_GWS 9.18.5 Use as needed. _HID 6.1.5 Use as needed. This is the primary object to use in device probing, though _CID and _CLS may also be used. -_HPP 6.2.8 Optional, PCI specific. +_HOT 11.4.7 Use as needed. + +_HPP 6.2.8 Use as needed, PCI specific. -_HPX 6.2.9 Optional, PCI specific. +_HPX 6.2.9 Use as needed, PCI specific. -_HRV 6.1.6 Optional, use as needed to clarify device behavior; in +_HRV 6.1.6 Use as needed, use as needed to clarify device behavior; in some cases, this may be easier to use than _DSD. _INI 6.5.1 Not required, but can be useful in setting up devices when UEFI leaves them in a state that may not be what the driver expects before it starts probing. -_IRC 7.2.15 Use as needed; power management specific. +_IRC 7.3.15 Use as needed; power management specific. + +_LCK 6.3.4 Use as needed. + +_LPI 8.4.4.3 Use as needed, but recommended for use with processor + definitions (_HID ACPI0010) on arm64. -_LCK 6.3.4 Optional. +_MAT 6.2.10 Use as needed; see also the MADT. -_MAT 6.2.10 Optional; see also the MADT. +_MBM 9.13.2.1 Use as needed. -_MLS 6.1.7 Optional, but highly recommended for use in +_MLS 6.1.7 Use as needed, but highly recommended for use in internationalization. -_OFF 7.1.2 It is recommended to define this method for any device +_MSG 9.2.2 Use as needed. + +_MSM 9.13.2.2 Use as needed. + +_MTL 11.4.8 Use as needed. + +_NTT 11.4.9 Use as needed. + +_OFF 7.2.2 It is recommended to define this method for any device that can be turned on or off. -_ON 7.1.3 It is recommended to define this method for any device +_ON 7.2.3 It is recommended to define this method for any device that can be turned on or off. \_OS 5.7.3 This method will return "Linux" by default (this is @@ -405,115 +498,219 @@ _OSC 6.2.11 This method can be a global method in ACPI (i.e., being used or what functionality is provided. The _OSC method is to be used instead. -_OST 6.3.5 Optional. +_OST 6.3.5 Use as needed. + +_PCT 8.4.6.1 Use as needed; power management specific. _PDC 8.4.1 Deprecated, do not use on arm64. +_PDL 8.4.6.2 Use as needed; power management specific. + \_PIC 5.8.1 The method should not be used. On arm64, the only interrupt model available is GIC. -_PLD 6.1.8 Optional. +_PLD 6.1.8 Use as needed. + +_PPC 8.4.6.3 Use as needed; power management specific. + +_PPE 8.4.8 Use as needed. \_PR 5.3.1 This namespace is for x86 use only on legacy systems. Do not use it on arm64. -_PRS 6.2.12 Optional. +_PRE 7.3.12 Use as needed; power management specific. + +_PRR 7.3.26 Use as needed; power management specific. + +_PRS 6.2.12 Use as needed. _PRT 6.2.13 Required as part of the definition of all PCI root devices. -_PRW 7.2.13 Use as needed; power management specific. +_PRW 7.3.13 Use as needed; power management specific. -_PRx 7.2.8-11 Use as needed; power management specific. If _PR0 is +_PRx 7.3.8-11 Use as needed; power management specific. If _PR0 is defined, _PR3 must also be defined. -_PSC 7.2.6 Use as needed; power management specific. +_PSC 7.3.6 Use as needed; power management specific. + +_PSD 8.4.6.5 Use as needed; power management specific. -_PSE 7.2.7 Use as needed; power management specific. +_PSE 7.3.7 Use as needed; power management specific. -_PSW 7.2.14 Use as needed; power management specific. +_PSL 11.4.10 Use as needed. -_PSx 7.2.2-5 Use as needed; power management specific. If _PS0 is +_PSS 8.4.6.2 Use as needed; power management specific. + +_PSV 11.4.11 Use as needed. + +_PSW 7.3.14 Use as needed; power management specific. + +_PSx 7.3.2-5 Use as needed; power management specific. If _PS0 is defined, _PS3 must also be defined. If clocks or regulators need adjusting to be consistent with power usage, change them in these methods. -\_PTS 7.3.1 Use as needed; power management specific. +_PTC 8.4.5.1 Use as needed; power management specific. + +\_PTS 7.4.1 Use as needed; power management specific. + +_PUR 8.5.1.1 Use as needed. + +_PXM 6.2.14 Use as needed. -_PXM 6.2.14 Optional. +_RDI 8.4.4.4 Use as needed, but recommended for use with processor + definitions (_HID ACPI0010) on arm64. _REG 6.5.4 Use as needed. \_REV 5.7.4 Always returns the latest version of ACPI supported. -_RMV 6.3.6 Optional. +_RMV 6.3.6 Use as needed. + +_RST 7.3.25 Use as needed; power management specific. + +_RTV 11.4.12 Use as needed. \_SB 5.3.1 Required on arm64; all devices must be defined in this namespace. +_SCP 11.4.13 Use as needed. + +_SDD 9.9.3.3.1 Use as needed. + _SEG 6.5.6 Use as needed; PCI-specific. -\_SI 5.3.1, Optional. - 9.1 +\_SI 5.3.1, Use as needed. + 9.2 + +_SLI 6.2.15 Use as needed; recommended when SLIT table is in use. -_SLI 6.2.15 Optional; recommended when SLIT table is in use. +_SRT 9.18.4 Use as needed. _STA 6.3.7, It is recommended to define this method for any device - 7.1.4 that can be turned on or off. + 7.2.4 that can be turned on or off. See also the STAO table + that provides overrides to hide devices in virtualized + environments. -_SRS 6.2.16 Optional; see also _PRS. +_SRS 6.2.16 Use as needed; see also _PRS. + +_SST 9.2.1 Use as needed. _STR 6.1.10 Recommended for conveying device names to end users; this is preferred over using _DDN. +_SST 9.2.1 Use as needed. + +_STP 9.18.7 Use as needed. + +_STV 9.18.8 Use as needed. + _SUB 6.1.9 Use as needed; _HID or _CID are preferred. -_SUN 6.1.11 Optional. +_SUN 6.1.11 Use as needed, but recommended. -\_Sx 7.3.2 Use as needed; power management specific. +\_Sx 7.4.2 Use as needed; power management specific. -_SxD 7.2.16-19 Use as needed; power management specific. +_SxD 7.3.16-19 Use as needed; power management specific. -_SxW 7.2.20-24 Use as needed; power management specific. +_SxW 7.3.20-24 Use as needed; power management specific. -_SWS 7.3.3 Use as needed; power management specific; this may +_SWS 7.4.3 Use as needed; power management specific; this may require specification changes for use on arm64. -\_TTS 7.3.4 Use as needed; power management specific. +_TC1 11.4.14 Use as needed. + +_TC2 11.4.15 Use as needed. + +_TDL 8.4.5.5 Use as needed; power management specific. + +_TFP 11.4.16 Use as needed. + +_TIP 9.18.9 Use as needed. + +_TIV 9.18.10 Use as needed. + +_TMP 11.4.17 Use as needed. + +_TPC 8.4.5.3 Use as needed; power management specific. -\_TZ 5.3.1 Optional. +_TPT 11.4.18 Use as needed. + +_TRT 11.4.19 Use as needed. + +_TSD 8.4.5.4 Use as needed; power management specific. + +_TSN 11.4.20 Use as needed. + +_TSP 11.4.21 Use as needed. + +_TSS 8.4.5.2 Use as needed; power management specific. + +_TST 11.4.22 Use as needed. + +\_TTS 7.4.4 Use as needed; power management specific. + +\_TZ 5.3.1 Use as needed. + +_TZD 11.4.23 Use as needed. + +_TZM 11.4.24 Use as needed. + +_TZP 11.4.25 Use as needed. _UID 6.1.12 Recommended for distinguishing devices of the same class; define it if at all possible. -\_WAK 7.3.5 Use as needed; power management specific. +_UPC 9.14 Use as needed. + +\_WAK 7.4.5 Use as needed; power management specific. + + ACPI Event Model ---------------- Do not use GPE block devices; these are not supported in the hardware reduced profile used by arm64. Since there are no GPE blocks defined for use on ARM -platforms, GPIO-signaled interrupts should be used for creating system events. +platforms, ACPI events must be signaled differently. + +There are two options: GPIO-signaled interrupts (Section 5.6.5), and +interrupt-signaled events (Section 5.6.9). Interrupt-signaled events are a +new feature in the ACPI 6.1 specification. Either -- or both -- can be used +on a given platform, and which to use may be dependent of limitations in any +given SoC. If possible, interrupt-signaled events are recommended. ACPI Processor Control ---------------------- -Section 8 of the ACPI specification is currently undergoing change that -should be completed in the 6.0 version of the specification. Processor -performance control will be handled differently for arm64 at that point -in time. Processor aggregator devices (section 8.5) will not be used, -for example, but another similar mechanism instead. - -While UEFI constrains what we can say until the release of 6.0, it is -recommended that CPPC (8.4.5) be used as the primary model. This will -still be useful into the future. C-states and P-states will still be -provided, but most of the current design work appears to favor CPPC. +Section 8 of the ACPI specification changed significantly in version 6.0. +Processors should now be defined as Device objects with _HID ACPI0007; do +not use the deprecated Processor statement in ASL. All multiprocessor systems +should also define a hierarchy of processors, done with Processor Container +Devices (see Section 8.4.3.1, _HID ACPI0010); do not use processor aggregator +devices (Section 8.5) to describe processor topology. Section 8.4 of the +specification describes the semantics of these object definitions and how +they interrelate. + +Most importantly, the processor hierarchy defined also defines the low power +idle states that are available to the platform, along with the rules for +determining which processors can be turned on or off and the circumstances +that control that. Without this information, the processors will run in +whatever power state they were left in by UEFI. + +Note too, that the processor Device objects defined and the entries in the +MADT for GICs are expected to be in sychronization. The _UID of the Device +object must correspond to processor IDs used in the MADT. + +It is recommended that CPPC (8.4.5) be used as the primary model for processor +performance control on arm64. C-states and P-states may become available at +some point in the future, but most current design work appears to favor CPPC. Further, it is essential that the ARMv8 SoC provide a fully functional implementation of PSCI; this will be the only mechanism supported by ACPI -to control CPU power state (including secondary CPU booting). - -More details will be provided on the release of the ACPI 6.0 specification. +to control CPU power state. Booting of secondary CPUs may be possible using +parking protocol, but only PSCI is to be used for ARM servers. ACPI System Address Map Interfaces @@ -535,21 +732,25 @@ used to indicate fatal errors that cannot be corrected, and require immediate attention. Since there is no direct equivalent of the x86 SCI or NMI, arm64 handles -these slightly differently. The SCI is handled as a normal GPIO-signaled -interrupt; given that these are corrected (or correctable) errors being -reported, this is sufficient. The NMI is emulated as the highest priority -GPIO-signaled interrupt possible. This implies some caution must be used -since there could be interrupts at higher privilege levels or even interrupts -at the same priority as the emulated NMI. In Linux, this should not be the -case but one should be aware it could happen. +these slightly differently. The SCI is handled as a high priority interrupt; +given that these are corrected (or correctable) errors being reported, this +is sufficient. The NMI is emulated as the highest priority interrupt +possible. This implies some caution must be used since there could be +interrupts at higher privilege levels or even interrupts at the same priority +as the emulated NMI. In Linux, this should not be the case but one should +be aware it could happen. ACPI Objects Not Supported on ARM64 ----------------------------------- While this may change in the future, there are several classes of objects that can be defined, but are not currently of general interest to ARM servers. +Some of these objects have x86 equivalents, and may actually make sense in ARM +servers. However, there is either no hardware available at present, or there +may not even be a non-ARM implementation yet. Hence, they are not currently +supported. -These are not supported: +The following classes of objects are not supported: -- Section 9.2: ambient light sensor devices @@ -571,16 +772,6 @@ These are not supported: -- Section 9.18: time and alarm devices (see 9.15) - -ACPI Objects Not Yet Implemented --------------------------------- -While these objects have x86 equivalents, and they do make some sense in ARM -servers, there is either no hardware available at present, or in some cases -there may not yet be a non-ARM implementation. Hence, they are currently not -implemented though that may change in the future. - -Not yet implemented are: - -- Section 10: power source and power meter devices -- Section 11: thermal management @@ -589,5 +780,31 @@ Not yet implemented are: -- Section 13: SMBus interfaces - -- Section 17: NUMA support (prototypes have been submitted for - review) + +This also mean that there is no support for the following objects: + +Name Section Name Section +---- ------------ ---- ------------ +_ALC 9.3.4 _FDM 9.10.3 +_ALI 9.3.2 _FIX 6.2.7 +_ALP 9.3.6 _GAI 10.4.5 +_ALR 9.3.5 _GHL 10.4.7 +_ALT 9.3.3 _GTM 9.9.2.1.1 +_BCT 10.2.2.10 _LID 9.5.1 +_BDN 6.5.3 _PAI 10.4.4 +_BIF 10.2.2.1 _PCL 10.3.2 +_BIX 10.2.2.1 _PIF 10.3.3 +_BLT 9.2.3 _PMC 10.4.1 +_BMA 10.2.2.4 _PMD 10.4.8 +_BMC 10.2.2.12 _PMM 10.4.3 +_BMD 10.2.2.11 _PRL 10.3.4 +_BMS 10.2.2.5 _PSR 10.3.1 +_BST 10.2.2.6 _PTP 10.4.2 +_BTH 10.2.2.7 _SBS 10.1.3 +_BTM 10.2.2.9 _SHL 10.4.6 +_BTP 10.2.2.8 _STM 9.9.2.1.1 +_DCK 6.5.2 _UPD 9.16.1 +_EC 12.12 _UPP 9.16.2 +_FDE 9.10.1 _WPC 10.5.2 +_FDI 9.10.2 _WPP 10.5.3 + diff --git a/Documentation/arm64/arm-acpi.txt b/Documentation/arm64/arm-acpi.txt index 570a4f8..12381c1 100644 --- a/Documentation/arm64/arm-acpi.txt +++ b/Documentation/arm64/arm-acpi.txt @@ -57,11 +57,11 @@ The short form of the rationale for ACPI on ARM is: -- The new ACPI governance process works well and Linux is now at the same table as hardware vendors and other OS vendors. In fact, there is no - longer any reason to feel that ACPI is only belongs to Windows or that + longer any reason to feel that ACPI only belongs to Windows or that Linux is in any way secondary to Microsoft in this arena. The move of ACPI governance into the UEFI forum has significantly opened up the specification development process, and currently, a large portion of the - changes being made to ACPI is being driven by Linux. + changes being made to ACPI are being driven by Linux. Key to the use of ACPI is the support model. For servers in general, the responsibility for hardware behaviour cannot solely be the domain of the @@ -159,7 +159,7 @@ Further, the ACPI core will only use the 64-bit address fields in the FADT (Fixed ACPI Description Table). Any 32-bit address fields in the FADT will be ignored on arm64. -Hardware reduced mode (see Section 4.1 of the ACPI 5.1 specification) will +Hardware reduced mode (see Section 4.1 of the ACPI 6.1 specification) will be enforced by the ACPI core on arm64. Doing so allows the ACPI core to run less complex code since it no longer has to provide support for legacy hardware from other architectures. Any fields that are not to be used for @@ -167,7 +167,7 @@ hardware reduced mode must be set to zero. For the ACPI core to operate properly, and in turn provide the information the kernel needs to configure devices, it expects to find the following -tables (all section numbers refer to the ACPI 5.1 specfication): +tables (all section numbers refer to the ACPI 6.1 specfication): -- RSDP (Root System Description Pointer), section 5.2.5 @@ -185,9 +185,22 @@ tables (all section numbers refer to the ACPI 5.1 specfication): -- If PCI is supported, the MCFG (Memory mapped ConFiGuration Table), section 5.2.6, specifically Table 5-31. + -- If booting without a console=<device> kernel parameter is + supported, the SPCR (Serial Port Console Redirection table), + section 5.2.6, specifically Table 5-31. + + -- If virtualization is supported, the IORT (Input Output Remapping + Table, section 5.2.6, specifically Table 5-31. + + -- If NUMA is supported, the SRAT (System Resource Affinity Table) + and SLIT (System Locality distance Information Table), sections + 5.2.16 and 5.2.17, respectively. + If the above tables are not all present, the kernel may or may not be able to boot properly since it may not be able to configure all of the -devices available. +devices available. This list of tables is not meant to be all inclusive; +in some environments other tables may be needed (e.g., any of the APEI +tables from section 18) to support specific functionality. ACPI Detection @@ -233,7 +246,7 @@ that looks like this: Name(KEY0, "value0"). An ACPI device driver would then retrieve the value of the property by evaluating the KEY0 object. However, using Name() this way has multiple problems: (1) ACPI limits names ("KEY0") to four characters unlike DT; (2) there is no industry -wide registry that maintains a list of names, minimzing re-use; (3) +wide registry that maintains a list of names, minimizing re-use; (3) there is also no registry for the definition of property values ("value0"), again making re-use difficult; and (4) how does one maintain backward compatibility as new hardware comes out? The _DSD method was created @@ -434,7 +447,8 @@ The ACPI specification changes regularly. During the year 2014, for instance, version 5.1 was released and version 6.0 substantially completed, with most of the changes being driven by ARM-specific requirements. Proposed changes are presented and discussed in the ASWG (ACPI Specification Working Group) which -is a part of the UEFI Forum. +is a part of the UEFI Forum. The current version of the ACPI specification +is 6.1 release in January 2016. Participation in this group is open to all UEFI members. Please see http://www.uefi.org/workinggroup for details on group membership. -- 2.5.0

9 years, 2 months

1
0
0 0

[PATCH 0/3] rasdaemon: minor fixes from Debian packaging

by Al Stone

In order to get rasdaemon packaging to work well in Debian, I had to make a few minor fixes -- a printf missing a "%s", a manpage in the wrong section, and a dependency on having system logging running before starting the daemon itself. These are the patches for those fixes (they're already in the 0.5.6 Debian package). Al Stone (3): rasdaemon: correct a printf that was missing a field to print to rasdaemon: the man page should be section 8 not 1 rasdaemon: make sure daemon does not start until after logging does configure.ac | 2 +- man/Makefile.am | 2 +- man/rasdaemon.1.in | 67 ----------------------------------------------- man/rasdaemon.8.in | 67 +++++++++++++++++++++++++++++++++++++++++++++++ mce-intel-p4-p6.c | 2 +- misc/rasdaemon.service.in | 1 - 6 files changed, 70 insertions(+), 71 deletions(-) delete mode 100644 man/rasdaemon.1.in create mode 100644 man/rasdaemon.8.in -- 2.5.0

9 years, 3 months

1
3
0 0

[PATCH v10 0/5] Watchdog: introduce ARM SBSA watchdog driver

by fu.wei＠linaro.org

From: Fu Wei <fu.wei(a)linaro.org> This patchset: (1)Introduce Documentation/devicetree/bindings/watchdog/sbsa-gwdt.txt for FDT info of SBSA Generic Watchdog, and give two examples of adding SBSA Generic Watchdog device node into the dts files: foundation-v8.dts and amd-seattle-soc.dtsi. (2)Introduce ARM SBSA watchdog driver: a.Use linux kernel watchdog framework; b.Work with FDT on ARM64; c.Support getting timeout from parameter and FDT at the driver init stage. d.Separate the driver to two parts: (1) single stage timeout driver(ignore WS0 interrupt) (2) register WS0 interrupt for the half timeout panic e.Timeout is from watchdog enabled to WS1 triggered. User can disable "half timeout panic" by kernel config or module parameter panic_enabled. Changelog: v10:Delete pretimeout support Separate the driver to two parts: (1) single stage timeout driver(ignore WS0 interrupt) (2) register WS0 interrupt for the half timeout panic timeout == (enable --> WS1) v9: https://lkml.org/lkml/2015/11/9/57 Rebase to latest kernel version(4.3). Update the Documentation of sbsa-gwdt device node info of FDT: (1) move some introduction to pretimeout patch (2) delete WS1 value from "interrupts" of binding documentation, since WS1 won't be handled by Linux. v8: https://lkml.org/lkml/2015/10/27/466 Rebase to latest kernel version(4.3-rc7). Separate the patches of GTDT support and arm_arch_timer. This clocksource relevant patch will upstreamed in a individual patchset. Update all the default timeout and pretimeout to 30s and 60s. Improve documentation and inline comments. Fix a bug in pretimeout support which makes timeout and pretimeout parameters initialization fail. v7: https://lkml.org/lkml/2015/8/24/611 Rebase to latest kernel version(4.2-rc7). Improve FDT support: geting resource by order, instead of name. According to the FDT support, Update the example dts file, gtdt.c and sbsa_gwdt.c. Pass the sparse test, and fix the warning. Fix the max_pretimeout and max_timeout value overflow bug. Delete the WCV output value. v6: https://lkml.org/lkml/2015/6/23/359 Improve the dtb example files: reduce the register frame size to 4K. Improve pretimeout support: (1) improve watchdog_init_timeouts function (2) rename watchdog_check_min_max_timeouts back to the original name (1) improve watchdog_timeout_invalid/watchdog_pretimeout_invalid Add the new features in the sbsa_gwdt driver: (1) In the second stage, user can feed the dog without cleaning WS0. (2) In the second stage, user can trigger WS1 by setting pretimeout = 0. (3) expand the max value of pretimeout, in case 10 second is not enough for a kdump kernel reboot in panic. v5: https://lkml.org/lkml/2015/6/10/357 Improve pretimeout support: (1)fix typo in documentation and comments. (2)fix the timeout limits validation bug. Simplify sbsa_gwdt driver: (1)integrate all the registers access functions into caller. v4: https://lkml.org/lkml/2015/6/2/4 Refactor GTDT support code: remove it from arch/arm64/kernel/acpi.c, put it into drivers/acpi/gtdt.c file. Integrate the GTDT code of drivers/clocksource/arm_arch_timer.c into drivers/acpi/gtdt.c. Improve pretimeout support, fix "pretimeout == 0" problem. Simplify sbsa_gwdt driver: (1)timeout/pretimeout limits setup; (2)keepalive function; (3)delete "clk == 0" check; (4)delete WS0 status bit check in interrupt routine; (5)sbsa_gwdt_set_wcv function. v3: https://lkml.org/lkml/2015/5/25/111 Delete "export arch_timer_get_rate" patch. Driver back to use arch_timer_get_cntfrq. Improve watchdog_init_timeouts function and update relevant documentation. Improve watchdog_timeout_invalid and watchdog_pretimeout_invalid. Improve foundation-v8.dts: delete the unnecessary tag of device node. Remove "ARM64 || COMPILE_TEST" from Kconfig. Add comments in arch/arm64/kernel/acpi.c Fix typoes and incorrect comments. v2: https://lkml.org/lkml/2015/5/21/172 Improve watchdog-kernel-api.txt documentation for pretimeout support. Export "arch_timer_get_rate" in arm_arch_timer.c. Add watchdog_init_timeouts API for pretimeout support in framework. Improve suspend and resume foundation in driver Improve timeout/pretimeout values init code in driver. Delete unnecessary items of the sbsa_gwdt struct and #define. Delete all unnecessary debug info in driver. Fix 64bit division bug. Use the arch_timer interface to get watchdog clock rate. Add MODULE_DEVICE_TABLE for platform device id. Fix typoes. v1: https://lkml.org/lkml/2015/5/15/279 The first version upstream patchset to linux mailing list. Fu Wei (5): Documentation: add sbsa-gwdt driver documentation ARM64: add SBSA Generic Watchdog device node in foundation-v8.dts ARM64: add SBSA Generic Watchdog device node in amd-seattle-soc.dtsi Watchdog: introduce ARM SBSA watchdog driver Watchdog: ARM SBSA Generic Watchdog half timeout panic support .../devicetree/bindings/watchdog/sbsa-gwdt.txt | 35 ++ Documentation/watchdog/watchdog-parameters.txt | 6 + arch/arm64/boot/dts/amd/amd-seattle-soc.dtsi | 9 + arch/arm64/boot/dts/arm/foundation-v8.dts | 8 + drivers/watchdog/Kconfig | 27 ++ drivers/watchdog/Makefile | 1 + drivers/watchdog/sbsa_gwdt.c | 366 +++++++++++++++++++++ 7 files changed, 452 insertions(+) create mode 100644 Documentation/devicetree/bindings/watchdog/sbsa-gwdt.txt create mode 100644 drivers/watchdog/sbsa_gwdt.c -- 2.5.0

9 years, 3 months

7
45
0 0

Re: [Linaro-acpi] [PATCH v5] acpi, apei, arm64: APEI initial support for aarch64.

by Fu Wei

Hi Tyler, On 4 February 2016 at 05:24, Baicar, Tyler <tbaicar(a)codeaurora.org> wrote: > Hello Fu, > > Tested-by: Tyler Baicar<tbaicar(a)codeaurora.org> > > on a 4.5 kernel. I wasn't on the ACPI mailing list when this patch was sent > out, so I couldn't respond to the original thread. NP, great thanks for your help, I will add you in the cc list :-) > > Thanks, > Tyler > -- Best regards, Fu Wei Software Engineer Red Hat Software (Beijing) Co.,Ltd.Shanghai Branch Ph: +86 21 61221326(direct) Ph: +86 186 2020 4684 (mobile) Room 1512, Regus One Corporate Avenue,Level 15, One Corporate Avenue,222 Hubin Road,Huangpu District, Shanghai,China 200021

9 years, 3 months

1
0
0 0

[PATCH V2 0/4] acpi: cppc optimization patches

by Prashanth Prakash

Changes in V2: Fixed compilation error on i386 This series introduces changes to reduce the time required to send a frequency transition requests to the platform while using the cppc-cpufreq driver. With these changes we see significant improvement in the average time to send freq. transition request to the platform. Profiling on an ARM platform showed that the average transaction time per request reduced from 200us to under 20us. Ashwin Chaugule (1): ACPI / CPPC: Optimize PCC Read Write operations Prashanth Prakash (3): acpi: cppc: optimized cpc_read and cpc_write mailbox: pcc: optimized pcc_send_data acpi: cppc: replace writeX/readX to PCC with relaxed version drivers/acpi/cppc_acpi.c | 186 +++++++++++++++++++++++++++++++++++------------ drivers/mailbox/pcc.c | 111 ++++++++++++++++++++++++++-- 2 files changed, 244 insertions(+), 53 deletions(-) -- Qualcomm Technologies, Inc. on behalf of the Qualcomm Innovation Center, Inc. The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum, a Linux Foundation Collaborative Project.

9 years, 3 months

5
14
0 0

[PATCH V3 00/21] MMCONFIG refactoring and support for ARM64 PCI hostbridge init based on ACPI

by Tomasz Nowicki

>From the functionality point of view this series might be split into the following logic parts: 1. Make MMCONFIG code arch-agnostic which allows all architectures to collect PCI config regions and used when necessary. 2. Move non-arch specific bits to the core code. 3. Use MMCONFIG code and implement generic ACPI based PCI host controller driver. 4. Enable above driver on ARM64 Patches has been built on top of 4.4 and can be found here: git@github.com:semihalf-nowicki-tomasz/linux.git (pci-acpi-v3) NOTE, this patch set depends on Matthew's patches: http://www.spinics.net/lists/linux-pci/msg45950.html https://github.com/Vality/linux/tree/pci-fixes This has been tested on Cavium ThunderX server and QEMU. Any help in reviewing and testing is very appreciated. v2 -> v3 - fix legacy IRQ assigning and IO ports registration - remove reference to arch specific companion device for ia64 - move ACPI PCI host controller driver to pci_root.c - drop generic domain assignment for x86 and ia64 as I am not able to run all necessary test variants - drop patch which cleaned legacy IRQ assignment since it belongs to Mathew's series: https://patchwork.ozlabs.org/patch/557504/ - extend MCFG quirk code - rebased to 4.4 v1 -> v2 - moved non-arch specific piece of code to dirver/acpi/ directory - fixed IO resource handling - introduced PCI config accessors quirks matching - moved ACPI_COMPANION_SET to generic code Liu Jiang (1): ACPI, PCI: Refine the way to handle translation_offset for ACPI resources Tomasz Nowicki (20): x86, pci: Reorder logic of pci_mmconfig_insert() function x86, pci, acpi: Move arch-agnostic MMCONFIG (aka ECAM) and ACPI code out of arch/x86/ directory pci, acpi, mcfg: Provide generic implementation of MCFG code initialization. x86, pci: mmconfig_{32,64}.c code refactoring - remove code duplication. x86, pci, ecam: mmconfig_64.c becomes default implementation for ECAM driver. XEN / PCI: Remove the dependence on arch x86 when PCI_MMCONFIG=y pci, acpi, mcfg: Provide default RAW ACPI PCI config space accessors. arm64, acpi: Use empty PCI config space accessors from mcfg.c file. pci, acpi, ecam: Add flag to indicate whether ECAM region was hot added or not. x86, pci: Cleanup platform specific MCFG data using previously added ECAM hot_added flag. pci, acpi: Move ACPI host bridge device companion assignment to core code. x86, ia64, pci: Remove ACPI companion device from platform specific data. pci, acpi: Provide generic way to assign bus domain number. x86, ia64: Include acpi_pci_{add|remove}_bus to the default pcibios_{add|remove}_bus implementation. acpi, mcfg: Implement two calls that might be used to inject/remove MCFG region. x86, acpi, pci: Use equivalent function introduced in previous patch. acpi, mcfg: Add default PCI config accessors implementation and initial support for related quirks. pci, acpi: Support for ACPI based generic PCI host controller init pci, acpi: Match PCI config space accessors against platfrom specific quirks. arm64, pci, acpi: Start using ACPI based PCI host bridge driver for ARM64. arch/arm64/Kconfig | 7 ++ arch/arm64/kernel/pci.c | 25 ---- arch/ia64/hp/common/sba_iommu.c | 2 +- arch/ia64/include/asm/pci.h | 1 - arch/ia64/pci/pci.c | 52 +++----- arch/ia64/sn/kernel/io_acpi_init.c | 4 +- arch/x86/Kconfig | 4 + arch/x86/include/asm/pci.h | 3 - arch/x86/include/asm/pci_x86.h | 28 +---- arch/x86/pci/acpi.c | 41 ++---- arch/x86/pci/common.c | 10 -- arch/x86/pci/irq.c | 10 -- arch/x86/pci/mmconfig-shared.c | 250 ++++++------------------------------- arch/x86/pci/mmconfig_32.c | 11 +- arch/x86/pci/mmconfig_64.c | 67 +--------- arch/x86/pci/numachip.c | 1 + drivers/acpi/Kconfig | 5 + drivers/acpi/Makefile | 1 + drivers/acpi/mcfg.c | 201 +++++++++++++++++++++++++++++ drivers/acpi/pci_root.c | 136 +++++++++++++++++++- drivers/acpi/resource.c | 12 +- drivers/pci/Kconfig | 10 ++ drivers/pci/Makefile | 5 + drivers/pci/ecam.c | 234 ++++++++++++++++++++++++++++++++++ drivers/pci/pci.c | 29 ++++- drivers/pci/probe.c | 5 + drivers/xen/pci.c | 7 +- include/acpi/acpi_bus.h | 1 + include/asm-generic/vmlinux.lds.h | 7 ++ include/linux/acpi.h | 2 + include/linux/ecam.h | 62 +++++++++ include/linux/pci-acpi.h | 17 +++ 32 files changed, 802 insertions(+), 448 deletions(-) create mode 100644 drivers/acpi/mcfg.c create mode 100644 drivers/pci/ecam.c create mode 100644 include/linux/ecam.h -- 1.9.1

9 years, 3 months

12
78
0 0

leg-kernel tag leg-20160201.0 released

by Graeme Gregory

The leg-kernel release has been made and tagged as leg-201600201.0 This is based on mainline kernel v4.4 Repository : http://git.linaro.org/leg/acpi/leg-kernel.git Direct Link: http://git.linaro.org/leg/acpi/leg-kernel.git/commit/adca6ee4e1e1581ff1612e… Topic Branches :- http://git.linaro.org/leg/acpi/acpi.git - topic-pci [topic-pci-20160122.0] - topic-numa [topic-numa-20160122.0] - topic-amba-probing [topic-amba-probing-20160122.0] - topic-acpi-console [topic-acpi-console-20160201.0] - topic-gtdt-wakeup-timer [topic-gtdt-wakeup-timer-20160201.0] - topic-fvp [topic-fvp-20160122.0] - topic-kvm-acpi [topic-kvm-acpi-20160122.0] - topic-sbsa-watchdog [topic-acpi-watchdog-20160122.0] - topic-apei [topic-apei-20160122.0] http://git.linaro.org/leg/acpi/leg-kernel.git - leg-configs [leg-configs-20160122.0] NOTES:-

9 years, 3 months

1
0
0 0

topic-pci branch on Mustang

by Itaru Kitayama

Hi, Has anyone successfully brought up the topic-pci branch kernel with acpi=force on Mustang? The boot is stalled in the middle of it. [ 0.000000] Booting Linux on physical CPU 0x0 [ 0.000000] Initializing cgroup subsys cpuset [ 0.000000] Initializing cgroup subsys cpu [ 0.000000] Initializing cgroup subsys cpuacct [ 0.000000] Linux version 4.4.0-rc1+ (itaru.kitayama(a)localhost.localdomain) (gcc version 5.3.1 20151207 (Red Hat 5.3.1-2) (GCC) ) #1 SMP Sun Jan 24 19:22:32 CST 2016 [ 0.000000] Boot CPU: AArch64 Processor [500f0001] [ 0.000000] earlycon: Early serial console at MMIO32 0x1c020000 (options '') [ 0.000000] bootconsole [uart0] enabled [ 0.000000] efi: Getting EFI parameters from FDT: [ 0.000000] EFI v2.40 by X-Gene Mustang Board EFI Nov 24 2015 13:22:41 [ 0.000000] efi: ACPI=0x47fa869000 ACPI 2.0=0x47fa869014 SMBIOS 3.0=0x47fa867000 [ 0.000000] cma: Reserved 512 MiB at 0x00000040e0000000 [ 0.000000] ACPI: Early table checksum verification disabled [ 0.000000] ACPI: RSDP 0x00000047FA869014 000024 (v02 APM ) [ 0.000000] ACPI: XSDT 0x00000047FA8680E8 00006C (v01 APM XGENE 00000003 01000013) [ 0.000000] ACPI: FACP 0x00000047FA85F000 00010C (v05 APM XGENE 00000003 INTL 20140724) [ 0.000000] ACPI: DSDT 0x00000047FA860000 00495F (v05 APM APM88xxx 00000001 INTL 20140724) [ 0.000000] ACPI: DBG2 0x00000047FA865000 0000AA (v00 APMC0D XGENEDBG 00000000 INTL 20140724) [ 0.000000] ACPI: GTDT 0x00000047FA85D000 0000E0 (v02 APM XGENE 00000001 INTL 20140724) [ 0.000000] ACPI: MCFG 0x00000047FA85C000 00003C (v01 APM XGENE 00000002 INTL 20140724) [ 0.000000] ACPI: SPCR 0x00000047FA85B000 000050 (v02 APMC0D XGENESPC 00000000 INTL 20140724) [ 0.000000] ACPI: SSDT 0x00000047FA85A000 00002D (v02 APM XGENE 00000001 INTL 20140724) [ 0.000000] ACPI: APIC 0x00000047FA859000 0002A4 (v03 APM XGENE 00000003 01000013) [ 0.000000] ACPI: SSDT 0x00000047FA858000 000078 (v02 REDHAT MACADDRS 00000001 01000013) [ 0.000000] ACPI: SSDT 0x00000047FA857000 000032 (v02 REDHAT UARTCLKS 00000001 01000013) [ 0.000000] psci: is not implemented in ACPI. [ 0.000000] Unsupported ACPI enable-method [ 0.000000] Unsupported ACPI enable-method [ 0.000000] Unsupported ACPI enable-method [ 0.000000] Unsupported ACPI enable-method [ 0.000000] Unsupported ACPI enable-method [ 0.000000] Unsupported ACPI enable-method [ 0.000000] Unsupported ACPI enable-method [ 0.000000] Unsupported ACPI enable-method [ 0.000000] PERCPU: Embedded 2 pages/cpu @fffffe07fff90000 s90496 r8192 d32384 u131072 [ 0.000000] Detected PIPT I-cache on CPU0 [ 0.000000] Built 1 zonelists in Zone order, mobility grouping on. Total pages: 523776 [ 0.000000] Kernel command line: BOOT_IMAGE=/vmlinuz-4.4.0-rc1+ root=UUID=0e305934-49d5-4f66-b10b-23ec6029fab9 ro acpi=force earlycon=uart8250,mmio32,0x1c020000 console=ttyS0,115200 [ 0.000000] PID hash table entries: 4096 (order: -1, 32768 bytes) [ 0.000000] Dentry cache hash table entries: 4194304 (order: 9, 33554432 bytes) [ 0.000000] Inode-cache hash table entries: 2097152 (order: 8, 16777216 bytes) [ 0.000000] software IO TLB [mem 0x40dbff0000-0x40dfff0000] (64MB) mapped at [fffffe00dbff0000-fffffe00dffeffff] [ 0.000000] Memory: 32851584K/33554432K available (7946K kernel code, 1243K rwdata, 5056K rodata, 832K init, 1460K bss, 178560K reserved, 524288K cma-reserved) [ 0.000000] Virtual kernel memory layout: [ 0.000000] vmalloc : 0xfffffc0000000000 - 0xfffffdfedfff0000 ( 2043 GB) [ 0.000000] vmemmap : 0xfffffdfee0000000 - 0xfffffdffe0000000 ( 4 GB maximum) [ 0.000000] 0xfffffdfef0000000 - 0xfffffdfef2000000 ( 32 MB actual) [ 0.000000] fixed : 0xfffffdfffa7d0000 - 0xfffffdfffac00000 ( 4288 KB) [ 0.000000] PCI I/O : 0xfffffdfffae00000 - 0xfffffdfffbe00000 ( 16 MB) [ 0.000000] modules : 0xfffffdfffc000000 - 0xfffffe0000000000 ( 64 MB) [ 0.000000] memory : 0xfffffe0000000000 - 0xfffffe0800000000 ( 32768 MB) [ 0.000000] .init : 0xfffffe0000d50000 - 0xfffffe0000e20000 ( 832 KB) [ 0.000000] .text : 0xfffffe0000080000 - 0xfffffe0000d42bf4 ( 13067 KB) [ 0.000000] .data : 0xfffffe0000e30000 - 0xfffffe0000f66c00 ( 1243 KB) [ 0.000000] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=1, Nodes=1 [ 0.000000] Hierarchical RCU implementation. [ 0.000000] Build-time adjustment of leaf fanout to 64. [ 0.000000] RCU restricting CPUs from NR_CPUS=8 to nr_cpu_ids=1. [ 0.000000] RCU: Adjusting geometry for rcu_fanout_leaf=64, nr_cpu_ids=1 [ 0.000000] NR_IRQS:64 nr_irqs:64 0 [ 0.000000] GIC: Using split EOI/Deactivate mode [ 0.000000] Architected cp15 timer(s) running at 50.00MHz (phys). [ 0.000000] clocksource: arch_sys_counter: mask: 0xffffffffffffff max_cycles: 0xb8812736b, max_idle_ns: 440795202655 ns [ 0.000002] sched_clock: 56 bits at 50MHz, resolution 20ns, wraps every 4398046511100ns [ 0.008541] Console: colour dummy device 80x25 [ 0.013235] Calibrating delay loop (skipped), value calculated using timer frequency.. 100.00 BogoMIPS (lpj=200000) [ 0.024283] pid_max: default: 32768 minimum: 301 [ 0.029180] ACPI: Core revision 20150930 [ 0.040671] ACPI: 4 ACPI AML tables successfully acquired and loaded [ 0.047439] Security Framework initialized [ 0.051756] Yama: becoming mindful. [ 0.055437] SELinux: Initializing. [ 0.059198] Mount-cache hash table entries: 65536 (order: 3, 524288 bytes) [ 0.066486] Mountpoint-cache hash table entries: 65536 (order: 3, 524288 bytes) [ 0.074654] Initializing cgroup subsys io [ 0.078888] Initializing cgroup subsys memory [ 0.083485] Initializing cgroup subsys devices [ 0.088190] Initializing cgroup subsys freezer [ 0.092885] Initializing cgroup subsys net_cls [ 0.097589] Initializing cgroup subsys perf_event [ 0.102552] Initializing cgroup subsys net_prio [ 0.107366] ftrace: allocating 27761 entries in 7 pages [ 0.132043] Remapping and enabling EFI services. [ 0.136940] EFI remap 0x0000000010510000 => 0000000040000000 [ 0.143127] EFI remap 0x0000000010548000 => 0000000040018000 [ 0.149290] EFI remap 0x0000000017000000 => 0000000040020000 [ 0.155453] EFI remap 0x000000001c025000 => 0000000040035000 [ 0.161616] EFI remap 0x000000007c0c0000 => 0000000040040000 [ 0.167779] EFI remap 0x000000007c1c0000 => 0000000040050000 [ 0.173942] EFI remap 0x000000007c2c0000 => 0000000040060000 [ 0.180104] EFI remap 0x000000007c3c0000 => 0000000040070000 [ 0.186266] EFI remap 0x000000007c4c0000 => 0000000040080000 [ 0.192438] EFI remap 0x000000007c5c0000 => 0000000040090000 [ 0.198600] EFI remap 0x000000007c6c0000 => 00000000400a0000 [ 0.204781] EFI remap 0x000000007c7c0000 => 00000000400b0000 [ 0.210961] EFI remap 0x00000047fa856000 => 00000000400c6000 [ 0.217141] EFI remap 0x00000047fa86a000 => 00000000400da000 [ 0.223314] EFI remap 0x00000047ffa12000 => 00000000402c2000 [ 0.229477] EFI remap 0x00000047ffa26000 => 00000000402d6000 [ 0.235646] ASID allocator initialised with 65536 entries [ 0.241999] Brought up 1 CPUs [ 0.245123] SMP: Total of 1 processors activated. [ 0.250087] CPU: All CPU(s) started at EL2 [ 0.254729] devtmpfs: initialized [ 0.258522] SMBIOS 3.0.0 present. [ 0.262069] clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 7645041785100000 ns [ 0.272746] atomic64_test: passed [ 0.276444] NET: Registered protocol family 16 [ 0.281343] PCCT header not found. [ 0.284973] vdso: 2 pages (1 code @ fffffe0000e50000, 1 data @ fffffe0000e40000) [ 0.292807] hw-breakpoint: found 4 breakpoint and 4 watchpoint registers. [ 0.300274] DMA: preallocated 256 KiB pool for atomic allocations [ 0.306735] ACPI: bus type PCI registered [ 0.310955] acpiphp: ACPI Hot Plug PCI Controller Driver version: 0.5 [ 0.317819] Serial: AMBA PL011 UART driver [ 0.324731] ACPI: Added _OSI(Module Device) [ 0.329151] ACPI: Added _OSI(Processor Device) [ 0.333845] ACPI: Added _OSI(3.0 _SCP Extensions) [ 0.338825] ACPI: Added _OSI(Processor Aggregator Device) [ 0.354649] ACPI: Interpreter enabled [ 0.358516] ACPI: Using GIC for interrupt routing [ 0.366406] ACPI: Power Resource [SCVR] (off) [ 0.379267] ACPI: PCI Root Bridge [PCI0] (domain 0000 [bus 00-ff]) [ 0.385823] acpi PNP0A08:00: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI] [ 0.394877] acpi PNP0A08:00: _OSC: OS now controls [PCIeHotplug PME AER PCIeCapability] [ 0.403349] acpi PNP0A08:00: Bus 0000:00 not present in PCI namespace [ 0.410745] vgaarb: loaded [ 0.413725] SCSI subsystem initialized [ 0.417770] ACPI: bus type USB registered [ 0.422021] usbcore: registered new interface driver usbfs [ 0.427843] usbcore: registered new interface driver hub [ 0.433491] usbcore: registered new device driver usb [ 0.439181] NetLabel: Initializing [ 0.442753] NetLabel: domain hash size = 128 [ 0.447352] NetLabel: protocols = UNLABELED CIPSOv4 [ 0.452606] NetLabel: unlabeled traffic allowed by default [ 0.458590] clocksource: Switched to clocksource arch_sys_counter [ 0.481347] pnp: PnP ACPI init [ 0.485318] pnp: PnP ACPI: found 0 devices [ 0.492409] NET: Registered protocol family 2 [ 0.497199] TCP established hash table entries: 262144 (order: 5, 2097152 bytes) [ 0.505681] TCP bind hash table entries: 65536 (order: 4, 1048576 bytes) [ 0.513141] TCP: Hash tables configured (established 262144 bind 65536) [ 0.520153] UDP hash table entries: 16384 (order: 3, 524288 bytes) [ 0.526945] UDP-Lite hash table entries: 16384 (order: 3, 524288 bytes) [ 0.534305] NET: Registered protocol family 1 [ 0.539050] RPC: Registered named UNIX socket transport module. [ 0.545309] RPC: Registered udp transport module. [ 0.550288] RPC: Registered tcp transport module. [ 0.555267] RPC: Registered tcp NFSv4.1 backchannel transport module. [ 0.562172] Unpacking initramfs... [ 0.801177] Freeing initrd memory: 10368K (fffffe07f8bf0000 - fffffe07f9610000) [ 0.809067] kvm [1]: error: no compatible GIC node found [ 0.814743] kvm [1]: error initializing Hyp mode: -19 [ 0.820381] futex hash table entries: 256 (order: -1, 32768 bytes) [ 0.826932] audit: initializing netlink subsys (disabled) [ 0.832659] audit: type=2000 audit(0.004:1): initialized [ 0.838583] HugeTLB registered 512 MB page size, pre-allocated 0 pages [ 0.848211] zbud: loaded [ 0.851033] VFS: Disk quotas dquot_6.6.0 [ 0.855250] VFS: Dquot-cache hash table entries: 8192 (order 0, 65536 bytes) [ 0.863482] NFS: Registering the id_resolver key type [ 0.868844] Key type id_resolver registered [ 0.873261] Key type id_legacy registered [ 0.877503] nfs4filelayout_init: NFSv4 File Layout Driver Registering... [ 0.884797] Key type big_key registered [ 0.892586] NET: Registered protocol family 38 [ 0.897363] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 252) [ 0.905217] io scheduler noop registered [ 0.909351] io scheduler deadline registered [ 0.913910] io scheduler cfq registered (default) [ 0.919094] pci_hotplug: PCI Hot Plug PCI Core version: 0.5 [ 0.924982] pciehp: PCI Express Hot Plug Controller Driver version: 0.4 [ 0.932276] Serial: 8250/16550 driver, 4 ports, IRQ sharing enabled

9 years, 3 months

3
10
0 0

leg-kernel tag leg-20160122.0 released

by Graeme Gregory

The leg-kernel release has been made and tagged as leg-20160122.0 This is based on mainline kernel v4.4 Repository : http://git.linaro.org/leg/acpi/leg-kernel.git Direct Link: http://git.linaro.org/leg/acpi/leg-kernel.git/commit/adca6ee4e1e1581ff1612e… Topic Branches :- http://git.linaro.org/leg/acpi/acpi.git - topic-pci [topic-pci-20160122.0] - topic-numa [topic-numa-20160122.0] - topic-amba-probing [topic-amba-probing-20160122.0] - topic-acpi-console [topic-acpi-console-20160122.0] - topic-gtdt-wakeup-timer [topic-gtdt-wakeup-timer-20160122.0] - topic-fvp [topic-fvp-20160122.0] - topic-kvm-acpi [topic-kvm-acpi-20160122.0] - topic-sbsa-watchdog [topic-acpi-watchdog-20160122.0] - topic-apei [topic-apei-20160122.0] http://git.linaro.org/leg/acpi/leg-kernel.git - leg-configs [leg-configs-20160122.0] NOTES:-

9 years, 3 months

1
0
0 0

[PATCH 0/5] Update ACPI RSDP tests to be specification compliant

by Al Stone

Add in several tests that extend the testing done on the RSDP. If these tests are all passed, the RSDP being examined should be compliant with the ACPI 6.0 spec. As part of that, when creating a dummy RSDP to substitute for one that cannot be read or found, use either RsdtAddress or XsdtAddress as described in the spec. For non-arm64, either can be used, but for arm64, only the XsdtAddress is to be used. Finally, update the regression tests for RSDP. Al Stone (5): RSDP: minor cleanups to rsdp.c for checkpatch issues utilities: add a helper function for printing out architecture names ACPI tables: when bodging up an RSDP, do the right thing for the arch ACPI RSDP: flesh out the tests to check for full spec compliance. Update regression test rsdp-0001/test-0001.sh fwts-test/rsdp-0001/rsdp.log | 16 ++++- src/acpi/rsdp/rsdp.c | 139 ++++++++++++++++++++++++++++++++++++----- src/lib/include/fwts_arch.h | 1 + src/lib/src/fwts_acpi_tables.c | 19 +++--- src/lib/src/fwts_arch.c | 18 ++++++ 5 files changed, 169 insertions(+), 24 deletions(-) -- 2.5.0

9 years, 3 months

1
5
0 0

[PATCH 0/7] Update several regression tests

by Al Stone

I should have added these earlier, but I did not. So, here they are: the updates to the regression tests affected by adding the --arch parameter, and by updating the MADT tests. Al Stone (7): Update the regression test arg-help-0001/test-0001.sh Update regression test for arg-help-0001/test-0002.sh Update regression test for arg-show-tests-0001/test-0001.sh Update regression test arg-show-tests-full-0001/test-0001.sh Update the regression test arg-table-path-0001/test-0001.sh Update the regression test madt-0001/test-0001.sh Update the regression test madt-0001/test-0002.sh fwts-test/arg-help-0001/arg-help-0001.log | 4 + fwts-test/arg-help-0001/arg-help-0002.log | 4 + .../arg-show-tests-0001/arg-show-tests-0001.log | 8 +- .../arg-show-tests-full-0001.log | 26 +- fwts-test/arg-table-path-0001/acpidump-0001.log | 741 +++++++++------------ fwts-test/madt-0001/madt-0001.log | 10 +- fwts-test/madt-0001/madt-0002.log | 33 +- 7 files changed, 344 insertions(+), 482 deletions(-) -- 2.5.0

9 years, 3 months

1
7
0 0

[PATCH v3 0/6] ACPI compliance testing for MADT and its subtables

by Al Stone

This patch series adds in specific ACPI compliance testing for the MADT and all of its various subtables (16, currently). The first three patches add in the idea of host and target architectures -- host being the arch that FWTS is running on, and target the arch whose firmware is being tested. This is needed later in the MADT tests since what is proper changes based on the architecture the firmware supports. The fourth patch adds the detailed tests for the MADT and all but one of the subtables currently defined in ACPI 6.0. The last two patches add in the relatively new GIC ITS subtable and compliance tests for it. There are still multiple TODOs in the compliance checks; these will be added as clarification of the spec becomes available. Changes for v3: -- Add in support for the --arch=<name> parameter to specify the arch for the target firmware (default is that host == target). -- Add in the fwts_architecture typedef plus some helper functions so that tests in the future can adapt their behavior as needed, and so that the MADT tests can set themselves up properly. -- Instead of creating a new sourc file src/acpi/compliance/madt.c, replace the existing src/acpi/madt/madt.c tests since we're providing a superset. -- Various minor style and syntax corrections (from Ian Colin King) Changes for v2: -- Clean up the white space problems -- Fix errors found by checkpatch (minor syntax things) -- Fix one logic error: while MADT and FADT table revisions *should* be in sync, they seldom are, so report this as a test failure and continue to test as much as possible instead of aborting completely, in some of those cases. Al Stone (6): Start defining FWTS architectures as variables Define some utility functions for using the fwts_architecture enum Add mechanism to tell FWTS what architecture is being tested ACPI: MADT: add in compliance tests for the MADT and subtables ACPI: Add in MADT subtable description for GIC ITS subtable ACPI: MADT: add in compliance checks for the GIC ITS subtable src/acpi/madt/madt.c | 1551 +++++++++++++++++++++++++++++++------- src/lib/include/fwts.h | 1 + src/lib/include/fwts_acpi.h | 10 + src/lib/include/fwts_arch.h | 41 + src/lib/include/fwts_framework.h | 3 + src/lib/src/Makefile.am | 1 + src/lib/src/fwts_arch.c | 88 +++ src/lib/src/fwts_framework.c | 25 + 8 files changed, 1460 insertions(+), 260 deletions(-) create mode 100644 src/lib/include/fwts_arch.h create mode 100644 src/lib/src/fwts_arch.c -- 2.5.0

9 years, 3 months

2
10
0 0

[PATCH 0/4] acpi: cppc optimization patches

by Prashanth Prakash

This series introduces changes to reduce the time required to send a frequency transition requests to the platform while using the cppc-cpufreq driver. With these changes we see significant improvement in the average time to send freq. transition request to the platform. Profiling on an ARM platform showed that the average transaction time per request reduced from 200us to under 20us. Ashwin Chaugule (1): ACPI / CPPC: Optimize PCC Read Write operations Prashanth Prakash (3): acpi: cppc: optimized cpc_read and cpc_write mailbox: pcc: optimized pcc_send_data acpi: cppc: replace writeX/readX to PCC with relaxed version drivers/acpi/cppc_acpi.c | 184 +++++++++++++++++++++++++++++++++++------------ drivers/mailbox/pcc.c | 110 ++++++++++++++++++++++++++-- 2 files changed, 241 insertions(+), 53 deletions(-) -- Qualcomm Technologies, Inc. on behalf of the Qualcomm Innovation Center, Inc. The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum, a Linux Foundation Collaborative Project.

9 years, 3 months

4
9
0 0

[PATCH 0/2] fwts man page updates

by Al Stone

Update the fwts man page to include some new parameters. Al Stone (2): Documentation: add --acpicompliance to man page Documentation: add --arch to the man page doc/fwts.1 | 11 +++++++++++ 1 file changed, 11 insertions(+) -- 2.5.0

9 years, 3 months

1
2
0 0

[PATCH v5] acpi, apei: add Boot Error Record Table (BERT) support

by fu.wei＠linaro.org

From: Huang Ying <ying.huang(a)intel.com> ACPI/APEI is designed to verifiy/report H/W errors, like Corrected Error(CE) and Uncorrected Error(UC). It contains four tables: HEST, ERST, EINJ and BERT. The first three tables have been merged for a long time, but because of lacking BIOS support for BERT, the support for BERT is pending until now. Recently on ARM 64 platform it is has been supported. So here we come. Under normal circumstances, when a hardware error occurs, kernel will be notified via NMI, MCE or some other method, then kernel will process the error condition, report it, and recover it if possible. But sometime, the situation is so bad, so that firmware may choose to reset directly without notifying Linux kernel. Linux kernel can use the Boot Error Record Table (BERT) to get the un-notified hardware errors that occurred in a previous boot. In this patch, the error information is reported via printk. For more information about BERT, please refer to ACPI Specification version 6.0, section 18.3.1: http://www.uefi.org/sites/default/files/resources/ACPI_6.0.pdf The following log is a BERT record after system reboot because of hitting a fatal memory error: BERT: Error records from previous boot: [Hardware Error]: It has been corrected by h/w and requires no further action [Hardware Error]: event severity: corrected [Hardware Error]: Error 0, type: recoverable [Hardware Error]: section_type: memory error [Hardware Error]: error_status: 0x0000000000000400 [Hardware Error]: physical_address: 0xffffffffffffffff [Hardware Error]: card: 1 module: 2 bank: 3 row: 1 column: 2 bit_position: 5 [Hardware Error]: error_type: 2, single-bit ECC [Tomasz Nowicki: Clear error status at the end of error handling] [Tony: Applied some cleanups suggested by Fu Wei] [Fu Wei: delete EXPORT_SYMBOL_GPL(bert_disable), improve the code] Signed-off-by: Huang Ying <ying.huang(a)intel.com> Signed-off-by: Tomasz Nowicki <tomasz.nowicki(a)linaro.org> Signed-off-by: Chen, Gong <gong.chen(a)linux.intel.com> Tested-by: Jonathan (Zhixiong) Zhang <zjzhang(a)codeaurora.org> Signed-off-by: Tony Luck <tony.luck(a)intel.com> Signed-off-by: Fu Wei <fu.wei(a)linaro.org> Tested-by: Tyler Baicar <tbaicar(a)codeaurora.org> --- Changelog: v5: Drop some superfluous comments. Use the introduce of BERT in ACPI Specification instead of original one at the head of bert.c. Fix typo in apei-internal.h Simplify the introduce of bert_disable. v4: https://lkml.org/lkml/2016/1/8/382 Fix the "#undef" bug Improve the instruction of "bert_disable", Delete the useless declaration in include/acpi/apei.h. v3: https://lkml.org/lkml/2016/1/7/214 Merge the two patches Do some improvements according to Borislav's suggestion. v2: https://lkml.org/lkml/2015/8/18/336 Delete EXPORT_SYMBOL_GPL(bert_disable), because "bert_disable" is only used in bert.c for now. Do some code-style cleanups. v1: The first upstream version submitted in linux-acpi mailing list: http://www.spinics.net/lists/linux-acpi/msg57384.html Documentation/kernel-parameters.txt | 3 + drivers/acpi/apei/Makefile | 2 +- drivers/acpi/apei/apei-internal.h | 2 +- drivers/acpi/apei/bert.c | 150 ++++++++++++++++++++++++++++++++++++ 4 files changed, 155 insertions(+), 2 deletions(-) diff --git a/Documentation/kernel-parameters.txt b/Documentation/kernel-parameters.txt index 3ea869d..acb772e 100644 --- a/Documentation/kernel-parameters.txt +++ b/Documentation/kernel-parameters.txt @@ -564,6 +564,9 @@ bytes respectively. Such letter suffixes can also be entirely omitted. bootmem_debug [KNL] Enable bootmem allocator debug messages. + bert_disable [ACPI] + Disable BERT OS support on buggy BIOSes. + bttv.card= [HW,V4L] bttv (bt848 + bt878 based grabber cards) bttv.radio= Most important insmod options are available as kernel args too. diff --git a/drivers/acpi/apei/Makefile b/drivers/acpi/apei/Makefile index 5d575a9..e50573d 100644 --- a/drivers/acpi/apei/Makefile +++ b/drivers/acpi/apei/Makefile @@ -3,4 +3,4 @@ obj-$(CONFIG_ACPI_APEI_GHES) += ghes.o obj-$(CONFIG_ACPI_APEI_EINJ) += einj.o obj-$(CONFIG_ACPI_APEI_ERST_DEBUG) += erst-dbg.o -apei-y := apei-base.o hest.o erst.o +apei-y := apei-base.o hest.o erst.o bert.o diff --git a/drivers/acpi/apei/apei-internal.h b/drivers/acpi/apei/apei-internal.h index 16129c7..6e9f14c 100644 --- a/drivers/acpi/apei/apei-internal.h +++ b/drivers/acpi/apei/apei-internal.h @@ -1,6 +1,6 @@ /* * apei-internal.h - ACPI Platform Error Interface internal - * definations. + * definitions. */ #ifndef APEI_INTERNAL_H diff --git a/drivers/acpi/apei/bert.c b/drivers/acpi/apei/bert.c new file mode 100644 index 0000000..a05b5c0 --- /dev/null +++ b/drivers/acpi/apei/bert.c @@ -0,0 +1,150 @@ +/* + * APEI Boot Error Record Table (BERT) support + * + * Copyright 2011 Intel Corp. + * Author: Huang Ying <ying.huang(a)intel.com> + * + * Under normal circumstances, when a hardware error occurs, the error + * handler receives control and processes the error. This gives OSPM a + * chance to process the error condition, report it, and optionally attempt + * recovery. In some cases, the system is unable to process an error. + * For example, system firmware or a management controller may choose to + * reset the system or the system might experience an uncontrolled crash + * or reset.The boot error source is used to report unhandled errors that + * occurred in a previous boot. This mechanism is described in the BERT + * table. + * + * For more information about BERT, please refer to ACPI Specification + * version 4.0, section 17.3.1 + * + * This file is licensed under GPLv2. + * + */ + +#include <linux/kernel.h> +#include <linux/module.h> +#include <linux/init.h> +#include <linux/acpi.h> +#include <linux/io.h> + +#include "apei-internal.h" + +#undef pr_fmt +#define pr_fmt(fmt) "BERT: " fmt + +static int bert_disable; + +static void __init bert_print_all(struct acpi_bert_region *region, + unsigned int region_len) +{ + struct acpi_hest_generic_status *estatus = + (struct acpi_hest_generic_status *)region; + int remain = region_len; + u32 estatus_len; + + if (!estatus->block_status) + return; + + while (remain > sizeof(struct acpi_bert_region)) { + if (cper_estatus_check(estatus)) { + pr_err(FW_BUG "Invalid error record.\n"); + return; + } + + estatus_len = cper_estatus_len(estatus); + if (remain < estatus_len) { + pr_err(FW_BUG "Truncated status block (length: %u).\n", + estatus_len); + return; + } + + pr_info_once("Error records from previous boot:\n"); + + cper_estatus_print(KERN_INFO HW_ERR, estatus); + + /* + * Because the boot error source is "one-time polled" type, + * clear Block Status of current Generic Error Status Block, + * once it's printed. + */ + estatus->block_status = 0; + + estatus = (void *)estatus + estatus_len; + /* No more error records. */ + if (!estatus->block_status) + return; + + remain -= estatus_len; + } +} + +static int __init setup_bert_disable(char *str) +{ + bert_disable = 1; + + return 0; +} +__setup("bert_disable", setup_bert_disable); + +static int __init bert_check_table(struct acpi_table_bert *bert_tab) +{ + if (bert_tab->header.length < sizeof(struct acpi_table_bert) || + bert_tab->region_length < sizeof(struct acpi_bert_region)) + return -EINVAL; + + return 0; +} + +static int __init bert_init(void) +{ + struct acpi_bert_region *boot_error_region; + struct acpi_table_bert *bert_tab; + unsigned int region_len; + acpi_status status; + int rc = 0; + + if (acpi_disabled) + return 0; + + if (bert_disable) { + pr_info("Boot Error Record Table support is disabled.\n"); + return 0; + } + + status = acpi_get_table(ACPI_SIG_BERT, 0, (struct acpi_table_header **)&bert_tab); + if (status == AE_NOT_FOUND) + return 0; + + if (ACPI_FAILURE(status)) { + pr_err("get table failed, %s.\n", acpi_format_exception(status)); + return -EINVAL; + } + + rc = bert_check_table(bert_tab); + if (rc) { + pr_err(FW_BUG "table invalid.\n"); + return rc; + } + + region_len = bert_tab->region_length; + if (!request_mem_region(bert_tab->address, region_len, "APEI BERT")) { + pr_err("Can't request iomem region <%016llx-%016llx>.\n", + (unsigned long long)bert_tab->address, + (unsigned long long)bert_tab->address + region_len - 1); + return -EIO; + } + + boot_error_region = ioremap_cache(bert_tab->address, region_len); + if (boot_error_region) { + bert_print_all(boot_error_region, region_len); + iounmap(boot_error_region); + } else { + rc = -ENOMEM; + } + + release_mem_region(bert_tab->address, region_len); + + return rc; +} + +late_initcall(bert_init); -- 2.5.0

9 years, 3 months

3
3
0 0

[PATCH v4] acpi, apei: add Boot Error Record Table (BERT) support

by fu.wei＠linaro.org

From: Huang Ying <ying.huang(a)intel.com> ACPI/APEI is designed to verifiy/report H/W errors, like Corrected Error(CE) and Uncorrected Error(UC). It contains four tables: HEST, ERST, EINJ and BERT. The first three tables have been merged for a long time, but because of lacking BIOS support for BERT, the support for BERT is pending until now. Recently on ARM 64 platform it is has been supported. So here we come. Under normal circumstances, when a hardware error occurs, kernel will be notified via NMI, MCE or some other method, then kernel will process the error condition, report it, and recover it if possible. But sometime, the situation is so bad, so that firmware may choose to reset directly without notifying Linux kernel. Linux kernel can use the Boot Error Record Table (BERT) to get the un-notified hardware errors that occurred in a previous boot. In this patch, the error information is reported via printk. For more information about BERT, please refer to ACPI Specification version 6.0, section 18.3.1: http://www.uefi.org/sites/default/files/resources/ACPI_6.0.pdf The following log is a BERT record after system reboot because of hitting a fatal memory error: BERT: Error records from previous boot: [Hardware Error]: It has been corrected by h/w and requires no further action [Hardware Error]: event severity: corrected [Hardware Error]: Error 0, type: recoverable [Hardware Error]: section_type: memory error [Hardware Error]: error_status: 0x0000000000000400 [Hardware Error]: physical_address: 0xffffffffffffffff [Hardware Error]: card: 1 module: 2 bank: 3 row: 1 column: 2 bit_position: 5 [Hardware Error]: error_type: 2, single-bit ECC [Tomasz Nowicki: Clear error status at the end of error handling] [Tony: Applied some cleanups suggested by Fu Wei] [Fu Wei: delete EXPORT_SYMBOL_GPL(bert_disable), improve the code] Signed-off-by: Huang Ying <ying.huang(a)intel.com> Signed-off-by: Tomasz Nowicki <tomasz.nowicki(a)linaro.org> Signed-off-by: Chen, Gong <gong.chen(a)linux.intel.com> Tested-by: Jonathan (Zhixiong) Zhang <zjzhang(a)codeaurora.org> Signed-off-by: Tony Luck <tony.luck(a)intel.com> Signed-off-by: Fu Wei <fu.wei(a)linaro.org> Tested-by: Tyler Baicar <tbaicar(a)codeaurora.org> --- Changelog: v4: fix the "#undef" bug Improve the instruction of "bert_disable", delete the useless declaration in include/acpi/apei.h. v3: https://lkml.org/lkml/2016/1/7/214 Merge the two patches Do some improvements according to Borislav's suggestion. v2: https://lkml.org/lkml/2015/8/18/336 Delete EXPORT_SYMBOL_GPL(bert_disable), because "bert_disable" is only used in bert.c for now. Do some code-style cleanups. v1: The first upstream version submitted in linux-acpi mailing list: http://www.spinics.net/lists/linux-acpi/msg57384.html Documentation/kernel-parameters.txt | 6 ++ drivers/acpi/apei/Makefile | 2 +- drivers/acpi/apei/bert.c | 158 ++++++++++++++++++++++++++++++++++++ include/acpi/apei.h | 1 + 4 files changed, 166 insertions(+), 1 deletion(-) create mode 100644 drivers/acpi/apei/bert.c diff --git a/Documentation/kernel-parameters.txt b/Documentation/kernel-parameters.txt index 742f69d..2c527a9 100644 --- a/Documentation/kernel-parameters.txt +++ b/Documentation/kernel-parameters.txt @@ -555,6 +555,12 @@ bytes respectively. Such letter suffixes can also be entirely omitted. bootmem_debug [KNL] Enable bootmem allocator debug messages. + bert_disable [ACPI] + Disable Boot Error Record Table (BERT) support. + Use this if to workaround buggy firmware which produces + the malformed BERT table or incorrect error status + block. + bttv.card= [HW,V4L] bttv (bt848 + bt878 based grabber cards) bttv.radio= Most important insmod options are available as kernel args too. diff --git a/drivers/acpi/apei/Makefile b/drivers/acpi/apei/Makefile index 5d575a9..e50573d 100644 --- a/drivers/acpi/apei/Makefile +++ b/drivers/acpi/apei/Makefile @@ -3,4 +3,4 @@ obj-$(CONFIG_ACPI_APEI_GHES) += ghes.o obj-$(CONFIG_ACPI_APEI_EINJ) += einj.o obj-$(CONFIG_ACPI_APEI_ERST_DEBUG) += erst-dbg.o -apei-y := apei-base.o hest.o erst.o +apei-y := apei-base.o hest.o erst.o bert.o diff --git a/drivers/acpi/apei/bert.c b/drivers/acpi/apei/bert.c new file mode 100644 index 0000000..ffcbf4b --- /dev/null +++ b/drivers/acpi/apei/bert.c @@ -0,0 +1,158 @@ +/* + * APEI Boot Error Record Table (BERT) support + * + * Copyright 2011 Intel Corp. + * Author: Huang Ying <ying.huang(a)intel.com> + * + * Under normal circumstances, when a hardware error occurs, kernel + * will be notified via NMI, MCE or some other method, then kernel + * will process the error condition, report it, and recover it if + * possible. But sometime, the situation is so bad, so that firmware + * may choose to reset directly without notifying Linux kernel. + * + * Linux kernel can use the Boot Error Record Table (BERT) to get the + * un-notified hardware errors that occurred in a previous boot. + * + * For more information about BERT, please refer to ACPI Specification + * version 4.0, section 17.3.1 + * + * This file is licensed under GPLv2. + * + */ + +#include <linux/kernel.h> +#include <linux/module.h> +#include <linux/init.h> +#include <linux/acpi.h> +#include <linux/io.h> + +#include "apei-internal.h" + +#undef pr_fmt +#define pr_fmt(fmt) "BERT: " fmt + +static int bert_disable; + +static void __init bert_print_all(struct acpi_bert_region *region, + unsigned int region_len) +{ + /* + * We use cper_estatus_* which uses struct acpi_hest_generic_status, + * struct acpi_hest_generic_status and acpi_bert_region are the same + * (Generic Error Status Block), so we declare the "estatus" here. + */ + struct acpi_hest_generic_status *estatus = + (struct acpi_hest_generic_status *)region; + int remain = region_len; + u32 estatus_len; + + /* The records have been polled*/ + if (!estatus->block_status) + return; + + while (remain > sizeof(struct acpi_bert_region)) { + /* + * Test Generic Error Status Block first, + * if the data(Offset, Length) is invalid, we just return, + * because we can't trust the length data from this block. + */ + if (cper_estatus_check(estatus)) { + pr_err(FW_BUG "Invalid error record\n"); + return; + } + + estatus_len = cper_estatus_len(estatus); + if (remain < estatus_len) { + pr_err(FW_BUG "Invalid status block length (%u)\n", + estatus_len); + return; + } + + pr_info_once("Error records from previous boot:\n"); + + cper_estatus_print(KERN_INFO HW_ERR, estatus); + + /* + * Because the boot error source is "one-time polled" type, + * clear Block Status of current Generic Error Status Block, + * once it's printed. + */ + estatus->block_status = 0; + + estatus = (void *)estatus + estatus_len; + if (!estatus->block_status) + return; /* No more error records */ + + remain -= estatus_len; + } +} + +static int __init setup_bert_disable(char *str) +{ + bert_disable = 1; + + return 0; +} +__setup("bert_disable", setup_bert_disable); + +static int __init bert_check_table(struct acpi_table_bert *bert_tab) +{ + if (bert_tab->header.length < sizeof(struct acpi_table_bert) || + bert_tab->region_length < sizeof(struct acpi_bert_region)) + return -EINVAL; + + return 0; +} + +static int __init bert_init(void) +{ + struct acpi_bert_region *boot_error_region; + struct acpi_table_bert *bert_tab; + unsigned int region_len; + acpi_status status; + int rc = 0; + + if (acpi_disabled) + return 0; + + if (bert_disable) { + pr_info("Boot Error Record Table support is disabled\n"); + return 0; + } + + status = acpi_get_table(ACPI_SIG_BERT, 0, (struct acpi_table_header **)&bert_tab); + if (status == AE_NOT_FOUND) + return 0; + if (ACPI_FAILURE(status)) { + pr_err("get table failed, %s\n", acpi_format_exception(status)); + return -EINVAL; + } + + rc = bert_check_table(bert_tab); + if (rc) { + pr_err(FW_BUG "table invalid\n"); + return rc; + } + + region_len = bert_tab->region_length; + if (!request_mem_region(bert_tab->address, region_len, "APEI BERT")) { + pr_err("Can't request iomem region <%016llx-%016llx>\n", + (unsigned long long)bert_tab->address, + (unsigned long long)bert_tab->address + region_len - 1); + return -EIO; + } + + boot_error_region = ioremap_cache(bert_tab->address, region_len); + if (boot_error_region) { + bert_print_all(boot_error_region, region_len); + iounmap(boot_error_region); + } else { + rc = -ENOMEM; + } + + release_mem_region(bert_tab->address, region_len); + + return rc; +} + +late_initcall(bert_init); -- 2.5.0

9 years, 3 months

4
7
0 0

[PATCH V2 00/23] MMCONFIG refactoring and support for ARM64 PCI hostbridge init based on ACPI

by Tomasz Nowicki

>From the functionality point of view this series might be split into the following logic parts: 1. Make MMCONFIG code arch-agnostic which allows all architectures to collect PCI config regions and used when necessary. 2. Move non-arch specific bits to the core code. 3. Use MMCONFIG code and implement generic ACPI based PCI host controller driver. 4. Enable above driver on ARM64 Patches has been built on top of 4.4-rc4 and can be found here: git@github.com:semihalf-nowicki-tomasz/linux.git (pci-acpi-v2) NOTE, this patch set depends on Matthew's patches: http://www.spinics.net/lists/linux-pci/msg45950.html https://github.com/Vality/linux/tree/pci-fixes This has been tested on Cavium ThunderX 1 socket server and QEMU. Any help in reviewing and testing is very appreciated. v1 -> v2 - moved non-arch specific piece of code to dirver/acpi/ directory - fixed IO resource handling - introduced PCI config accessors quirks matching - moved ACPI_COMPANION_SET to generic code Liu Jiang (1): ACPI, PCI: Refine the way to handle translation_offset for ACPI resources Tomasz Nowicki (22): x86, pci: Reorder logic of pci_mmconfig_insert() function x86, pci, acpi: Move arch-agnostic MMCONFIG (aka ECAM) and ACPI code out of arch/x86/ directory pci, acpi, mcfg: Provide generic implementation of MCFG code initialization. x86, pci: mmconfig_{32,64}.c code refactoring - remove code duplication. x86, pci, ecam: mmconfig_64.c becomes default implementation for ECAM driver. XEN / PCI: Remove the dependence on arch x86 when PCI_MMCONFIG=y pci, acpi, mcfg: Provide default RAW ACPI PCI config space accessors. arm64, acpi: Use empty PCI config space accessors from mcfg.c file. pci, acpi, ecam: Add flag to indicate whether ECAM region was hot added or not. x86, pci: Cleanup platform specific MCFG data using previously added ECAM hot_added flag. arm64, pci: Remove useless boot time IRQ assignment when booting with DT. pci, acpi: Move ACPI host bridge device companion assignment to core code. x86, ia64, pci: Remove ACPI companion device from platform specific data. pci, acpi: Provide generic way to assign bus domain number. x86, ia64, pci: Convert arches to use PCI_DOMAINS_GENERIC. x86, ia64: Include acpi_pci_{add|remove}_bus to the default pcibios_{add|remove}_bus implementation. acpi, mcfg: Implement two calls that might be used to inject/remove MCFG region. x86, acpi, pci: Use equivalent function introduced in previous patch. acpi, mcfg: Add default PCI config accessors implementation and initial support for related quirks. pci, acpi: Support for ACPI based PCI hostbridge init pci, acpi: Match PCI config space accessors against platfrom specific quirks. arm64, pci, acpi: Start using ACPI based PCI host bridge driver for ARM64. arch/arm64/Kconfig | 10 ++ arch/arm64/kernel/pci.c | 35 ------ arch/ia64/Kconfig | 3 + arch/ia64/include/asm/pci.h | 3 - arch/ia64/pci/pci.c | 53 +++----- arch/x86/Kconfig | 7 ++ arch/x86/include/asm/pci.h | 10 -- arch/x86/include/asm/pci_x86.h | 28 +---- arch/x86/pci/acpi.c | 43 ++----- arch/x86/pci/common.c | 10 -- arch/x86/pci/irq.c | 10 -- arch/x86/pci/mmconfig-shared.c | 250 ++++++-------------------------------- arch/x86/pci/mmconfig_32.c | 11 +- arch/x86/pci/mmconfig_64.c | 67 +--------- arch/x86/pci/numachip.c | 1 + drivers/acpi/Makefile | 1 + drivers/acpi/mcfg.c | 203 +++++++++++++++++++++++++++++++ drivers/acpi/pci_root.c | 5 +- drivers/acpi/resource.c | 12 +- drivers/pci/Kconfig | 10 ++ drivers/pci/Makefile | 5 + drivers/pci/ecam.c | 234 +++++++++++++++++++++++++++++++++++ drivers/pci/host/Kconfig | 6 + drivers/pci/host/Makefile | 1 + drivers/pci/host/pci-host-acpi.c | 138 +++++++++++++++++++++ drivers/pci/pci.c | 29 ++++- drivers/pci/probe.c | 5 + drivers/xen/pci.c | 7 +- include/asm-generic/vmlinux.lds.h | 7 ++ include/linux/acpi.h | 2 + include/linux/ecam.h | 61 ++++++++++ include/linux/pci-acpi.h | 17 +++ 32 files changed, 817 insertions(+), 467 deletions(-) create mode 100644 drivers/acpi/mcfg.c create mode 100644 drivers/pci/ecam.c create mode 100644 drivers/pci/host/pci-host-acpi.c create mode 100644 include/linux/ecam.h -- 1.9.1

9 years, 3 months

14
69
0 0

[RFC 0/5] console/acpi: add DBG2 and SPCR console configuration

by Leif Lindholm

Support for configuring bootconsole and console via the ACPI tables DBG2 (Debug Port Table 2) [1] and SPCR (Serial Port Console Redirection Table) [2], defined by Microsoft, has been discussed on and off over the years. [1] https://msdn.microsoft.com/en-us/library/windows/hardware/dn639131(v=vs.85)… [2] https://msdn.microsoft.com/en-us/library/windows/hardware/dn639132(v=vs.85)… Licensing concerns have prevented this happening in the past, but as of 10 August 2015, these tables have both been released also under OWF 1.0 (http://www.openwebfoundation.org/legal/the-owf-1-0-agreements/owfa-1-0) which is think is noncontroversially GPL-compatible? This set is a first attempt at implementing this. Submitting as an RFC since the SPCR handling currently depends on the console driver being initialized after subsystem initcalls. Workaround to enable testing surrounding infrastructure in 5/5, _really_ not intended to be merged. (Suggestions for acceptable ways of working around this appreciated.) For testing the DBG2 stuff with pl011, you would need: - A patch to unbreak pl011 earlycon, like http://permalink.gmane.org/gmane.linux.ports.arm.kernel/433219 - A QEMU that generates DBG2 tables, like current HEAD with the addition of http://lists.nongnu.org/archive/html/qemu-devel/2015-09/msg01719.html SPCR support is included in QEMU's ARM mach-virt since 2.4 release. DBG2 support has an Intel copyright notice added to it since my starting point was Lv Zheng's 2012 DBGP/DBG2 set (although not much of the original remains - this is quite a cut-down version). Leif Lindholm (4): arm64: move acpi/dt decision earlier in boot process of/serial: move earlycon early_param handling to serial acpi/serial: add DBG2 earlycon support HACK: serial: move pl011 initcall to device_initcall Torez Smith (1): tty/console: use SPCR table to define console arch/arm64/kernel/acpi.c | 55 +++++---- drivers/acpi/Makefile | 1 + drivers/acpi/console.c | 260 +++++++++++++++++++++++++++++++++++++++ drivers/of/fdt.c | 13 +- drivers/tty/serial/amba-pl011.c | 2 +- drivers/tty/serial/earlycon.c | 18 ++- drivers/tty/serial/serial_core.c | 14 ++- include/linux/acpi.h | 13 ++ include/linux/of_fdt.h | 1 + include/linux/serial_core.h | 9 +- 10 files changed, 337 insertions(+), 49 deletions(-) create mode 100644 drivers/acpi/console.c -- 2.1.4

9 years, 3 months

7
21
0 0

[PATCH v2 0/3] ACPI compliance testing for MADT and its subtables

by Al Stone

This patch series adds in specific ACPI compliance testing for the MADT and all of its various subtables (16, currently). The first patch adds tests for the MADT and all subtables currently defined in FWTS. The last two patches add in the relatively new GIC ITS subtable and compliance tests for it. There are still multiple TODOs in the compliance checks; these will be added as clarification of the spec becomes available. Changes for v2: -- Clean up the white space problems -- Fix errors found by checkpatch (minor syntax things) -- Fix one logic error: while MADT and FADT table revisions *should* be in sync, they seldom are, so report this as a test failure and continue to test as much as possible instead of aborting completely, in some of those cases. Al Stone (3): ACPI: MADT: add in compliance tests for the MADT and subtables ACPI: Add in MADT subtable description for GIC ITS subtable ACPI: MADT: add in compliance checks for the GIC ITS subtable src/Makefile.am | 1 + src/acpi/compliance/madt.c | 1372 +++++++++++++++++++++++++++++++++++++++++++ src/lib/include/fwts_acpi.h | 10 + 3 files changed, 1383 insertions(+) create mode 100644 src/acpi/compliance/madt.c -- 2.5.0

9 years, 4 months

1
3
0 0

[PATCH v3] acpi, apei: add Boot Error Record Table (BERT) support

by fu.wei＠linaro.org

From: Huang Ying <ying.huang(a)intel.com> ACPI/APEI is designed to verifiy/report H/W errors, like Corrected Error(CE) and Uncorrected Error(UC). It contains four tables: HEST, ERST, EINJ and BERT. The first three tables have been merged for a long time, but because of lacking BIOS support for BERT, the support for BERT is pending until now. Recently on ARM 64 platform it is has been supported. So here we come. Under normal circumstances, when a hardware error occurs, kernel will be notified via NMI, MCE or some other method, then kernel will process the error condition, report it, and recover it if possible. But sometime, the situation is so bad, so that firmware may choose to reset directly without notifying Linux kernel. Linux kernel can use the Boot Error Record Table (BERT) to get the un-notified hardware errors that occurred in a previous boot. In this patch, the error information is reported via printk. For more information about BERT, please refer to ACPI Specification version 6.0, section 18.3.1: http://www.uefi.org/sites/default/files/resources/ACPI_6.0.pdf The following log is a BERT record after system reboot because of hitting a fatal error. BERT: Obtained BERT iomem region <00000000fe801000-00000000fe802000> for BERT. [Hardware Error]: Error record from previous boot: [Hardware Error]: event severity: fatal [Hardware Error]: Error 0, type: fatal [Hardware Error]: section_type: memory error [Hardware Error]: physical_address: 0x00000000fe800000 [Hardware Error]: physical_address_mask: 0x0000000000000fff [Hardware Error]: card: 0 module: 1 bank: 0 device: 1 row: 1 column: 1 bit_pos [Tomasz Nowicki: Clear error status at the end of error handling] [Tony: Applied some cleanups suggested by Fu Wei] [Fu Wei: delete EXPORT_SYMBOL_GPL(bert_disable), improve the code] Signed-off-by: Huang Ying <ying.huang(a)intel.com> Signed-off-by: Tomasz Nowicki <tomasz.nowicki(a)linaro.org> Signed-off-by: Chen, Gong <gong.chen(a)linux.intel.com> Tested-by: Jonathan (Zhixiong) Zhang <zjzhang(a)codeaurora.org> Signed-off-by: Tony Luck <tony.luck(a)intel.com> Signed-off-by: Fu Wei <fu.wei(a)linaro.org> Tested-by: Tyler Baicar <tbaicar(a)codeaurora.org> --- Changelog: v3: Merge the two patches Do some improvements according to Borislav's suggestion. v2: https://lkml.org/lkml/2015/8/18/336 Delete EXPORT_SYMBOL_GPL(bert_disable), because "bert_disable" is only used in bert.c for now. Do some code-style cleanups. v1: The first upstream version submitted in linux-acpi mailing list: http://www.spinics.net/lists/linux-acpi/msg57384.html Documentation/kernel-parameters.txt | 3 + drivers/acpi/apei/Makefile | 2 +- drivers/acpi/apei/bert.c | 158 ++++++++++++++++++++++++++++++++++++ include/acpi/apei.h | 1 + 4 files changed, 163 insertions(+), 1 deletion(-) create mode 100644 drivers/acpi/apei/bert.c diff --git a/Documentation/kernel-parameters.txt b/Documentation/kernel-parameters.txt index 742f69d..2310e97 100644 --- a/Documentation/kernel-parameters.txt +++ b/Documentation/kernel-parameters.txt @@ -555,6 +555,9 @@ bytes respectively. Such letter suffixes can also be entirely omitted. bootmem_debug [KNL] Enable bootmem allocator debug messages. + bert_disable [ACPI] + Disable Boot Error Record Table (BERT) support. + bttv.card= [HW,V4L] bttv (bt848 + bt878 based grabber cards) bttv.radio= Most important insmod options are available as kernel args too. diff --git a/drivers/acpi/apei/Makefile b/drivers/acpi/apei/Makefile index 5d575a9..e50573d 100644 --- a/drivers/acpi/apei/Makefile +++ b/drivers/acpi/apei/Makefile @@ -3,4 +3,4 @@ obj-$(CONFIG_ACPI_APEI_GHES) += ghes.o obj-$(CONFIG_ACPI_APEI_EINJ) += einj.o obj-$(CONFIG_ACPI_APEI_ERST_DEBUG) += erst-dbg.o -apei-y := apei-base.o hest.o erst.o +apei-y := apei-base.o hest.o erst.o bert.o diff --git a/drivers/acpi/apei/bert.c b/drivers/acpi/apei/bert.c new file mode 100644 index 0000000..6f6ae38 --- /dev/null +++ b/drivers/acpi/apei/bert.c @@ -0,0 +1,158 @@ +/* + * APEI Boot Error Record Table (BERT) support + * + * Copyright 2011 Intel Corp. + * Author: Huang Ying <ying.huang(a)intel.com> + * + * Under normal circumstances, when a hardware error occurs, kernel + * will be notified via NMI, MCE or some other method, then kernel + * will process the error condition, report it, and recover it if + * possible. But sometime, the situation is so bad, so that firmware + * may choose to reset directly without notifying Linux kernel. + * + * Linux kernel can use the Boot Error Record Table (BERT) to get the + * un-notified hardware errors that occurred in a previous boot. + * + * For more information about BERT, please refer to ACPI Specification + * version 4.0, section 17.3.1 + * + * This file is licensed under GPLv2. + * + */ + +#include <linux/kernel.h> +#include <linux/module.h> +#include <linux/init.h> +#include <linux/acpi.h> +#include <linux/io.h> + +#include "apei-internal.h" + +#undef pr_fmt(fmt) +#define pr_fmt(fmt) "BERT: " fmt + +static int bert_disable; + +static void __init bert_print_all(struct acpi_bert_region *region, + unsigned int region_len) +{ + /* + * We use cper_estatus_* which uses struct acpi_hest_generic_status, + * struct acpi_hest_generic_status and acpi_bert_region are the same + * (Generic Error Status Block), so we declare the "estatus" here. + */ + struct acpi_hest_generic_status *estatus = + (struct acpi_hest_generic_status *)region; + int remain = region_len; + u32 estatus_len; + + /* The records have been polled*/ + if (!estatus->block_status) + return; + + while (remain > sizeof(struct acpi_bert_region)) { + /* + * Test Generic Error Status Block first, + * if the data(Offset, Length) is invalid, we just return, + * because we can't trust the length data from this block. + */ + if (cper_estatus_check(estatus)) { + pr_err(FW_BUG "Invalid error record\n"); + return; + } + + estatus_len = cper_estatus_len(estatus); + if (remain < estatus_len) { + pr_err(FW_BUG "Invalid status block length (%u)\n", + estatus_len); + return; + } + + pr_info_once(HW_ERR "Error records from previous boot:\n"); + + cper_estatus_print(KERN_INFO HW_ERR, estatus); + + /* + * Because the boot error source is "one-time polled" type, + * clear Block Status of current Generic Error Status Block, + * once it's printed. + */ + estatus->block_status = 0; + + estatus = (void *)estatus + estatus_len; + if (!estatus->block_status) + return; /* No more error records */ + + remain -= estatus_len; + } +} + +static int __init setup_bert_disable(char *str) +{ + bert_disable = 1; + + return 0; +} +__setup("bert_disable", setup_bert_disable); + +static int __init bert_check_table(struct acpi_table_bert *bert_tab) +{ + if (bert_tab->header.length < sizeof(struct acpi_table_bert) || + bert_tab->region_length < sizeof(struct acpi_bert_region)) + return -EINVAL; + + return 0; +} + +static int __init bert_init(void) +{ + struct acpi_bert_region *boot_error_region; + struct acpi_table_bert *bert_tab; + unsigned int region_len; + acpi_status status; + int rc = 0; + + if (acpi_disabled) + return 0; + + if (bert_disable) { + pr_info("Boot Error Record Table support is disabled\n"); + return 0; + } + + status = acpi_get_table(ACPI_SIG_BERT, 0, (struct acpi_table_header **)&bert_tab); + if (status == AE_NOT_FOUND) + return 0; + if (ACPI_FAILURE(status)) { + pr_err("get table failed, %s\n", acpi_format_exception(status)); + return -EINVAL; + } + + rc = bert_check_table(bert_tab); + if (rc) { + pr_err(FW_BUG "table invalid\n"); + return rc; + } + + region_len = bert_tab->region_length; + if (!request_mem_region(bert_tab->address, region_len, "APEI BERT")) { + pr_err("Can't request iomem region <%016llx-%016llx>\n", + (unsigned long long)bert_tab->address, + (unsigned long long)bert_tab->address + region_len - 1); + return -EIO; + } + + boot_error_region = ioremap_cache(bert_tab->address, region_len); + if (boot_error_region) { + bert_print_all(boot_error_region, region_len); + iounmap(boot_error_region); + } else { + rc = -ENOMEM; + } + + release_mem_region(bert_tab->address, region_len); + + return rc; +} + +late_initcall(bert_init); diff --git a/include/acpi/apei.h b/include/acpi/apei.h index 76284bb..284801a 100644 --- a/include/acpi/apei.h +++ b/include/acpi/apei.h @@ -23,6 +23,7 @@ extern bool ghes_disable; #else #define ghes_disable 1 #endif +extern int bert_disable; #ifdef CONFIG_ACPI_APEI void __init acpi_hest_init(void); -- 2.5.0

9 years, 4 months

5
7
0 0

[PATCH v2 0/2] acpi, apei: add BERT support

by fu.wei＠linaro.org

From: Fu Wei <fu.wei(a)linaro.org> ACPI/APEI is designed to verifiy/report H/W errors, like Corrected Error(CE) and Uncorrected Error(UC). It contains four tables: HEST, ERST, EINJ and BERT. The first three tables have been merged for a long time, but because of lacking BIOS support for BERT, the support for BERT is pending until now. Recently on ARM 64 platform it is has been supported. So here we come. The following log is a BERT record after system reboot because of hitting a fatal error. BERT: Obtained BERT iomem region <00000000fe801000-00000000fe802000> for BERT. [Hardware Error]: Error record from previous boot: [Hardware Error]: event severity: fatal [Hardware Error]: Error 0, type: fatal [Hardware Error]: section_type: memory error [Hardware Error]: physical_address: 0x00000000fe800000 [Hardware Error]: physical_address_mask: 0x0000000000000fff [Hardware Error]: card: 0 module: 1 bank: 0 device: 1 row: 1 column: 1 bit_pos Changelog: v2: Delete EXPORT_SYMBOL_GPL(bert_disable), because "bert_disable" is only used in bert.c for now. Do some code-style cleanups. v1: The first upstream version submitted in linux-acpi mailing list: http://www.spinics.net/lists/linux-acpi/msg57384.html Huang Ying (1): ACPI, APEI, Boot Error Record Table (BERT) support Tomasz Nowicki (1): acpi, apei, bert: Clear error status at the end of error handling Documentation/kernel-parameters.txt | 3 + drivers/acpi/apei/Makefile | 2 +- drivers/acpi/apei/bert.c | 165 ++++++++++++++++++++++++++++++++++++ include/acpi/apei.h | 1 + 4 files changed, 170 insertions(+), 1 deletion(-) create mode 100644 drivers/acpi/apei/bert.c -- 2.4.3

9 years, 4 months

4
8
0 0

[PATCH v2 0/3] ACPI, clocksource: add GTDT and ARM memory-mapped timer support

by fu.wei＠linaro.org

From: Fu Wei <fu.wei(a)linaro.org> This patchset: (1)Introduce ACPI GTDT parser: drivers/acpi/gtdt.c Parse all kinds of timer in GTDT table of ACPI:arch timer, memory-mapped timer and SBSA Generic Watchdog timer. This driver can help to simplify all the relevant timer drivers, and separate all the ACPI GTDT knowledge from them. (2)Simplify ACPI code for arch timer in arm_arch_timer.c (3)Add memory-mapped timer support in arm_arch_timer.c The SBSA Generic Watchdog info parsing support have been tested with a upstreaming SBSA Generic Watchdog driver: https://lkml.org/lkml/2015/10/27/466 on the following platforms: (1)ARM Foundation v8 model (2)AMD Seattle platform ARM memory-mapped timer support of this patchset has been tested on the following platforms: (1)ARM Foundation v8 model Changelog: v2: Rebase to latest kernel version(4.4-rc3). Fix the bug about the config problem, use CONFIG_ACPI_GTDT instead of CONFIG_ACPI in arm_arch_timer.c v1: The first upstreaming version: https://lkml.org/lkml/2015/10/28/553 Fu Wei (3): ACPI: add GTDT table parse driver into ACPI driver clocksource: simplify ACPI code in arm_arch_timer.c clocksource: add memory-mapped timer support in arm_arch_timer.c drivers/acpi/Kconfig | 9 + drivers/acpi/Makefile | 1 + drivers/acpi/gtdt.c | 367 +++++++++++++++++++++++++++++++++++ drivers/clocksource/arm_arch_timer.c | 178 +++++++++++++---- include/clocksource/arm_arch_timer.h | 19 ++ include/linux/acpi.h | 17 ++ 6 files changed, 555 insertions(+), 36 deletions(-) create mode 100644 drivers/acpi/gtdt.c -- 2.5.0

9 years, 4 months

4
6
0 0

[PATCH V1 00/11] MMCONFIG refactoring and ARM64 PCI hostbridge init based on ACPI

by Tomasz Nowicki

>From the functionality point of view this series might be split into two logic parts: 1. Making MMCONFIG code arch-agnostic which allows all architectures to collect PCI config regions and used when necessary. 2. Using generic MMCONFIG code and introducing ACPI based PCI hostbridge initialization for ARM64 Patches has been built on top of: [Patch v7 0/7] Consolidate ACPI PCI root common code into ACPI core https://lkml.org/lkml/2015/10/14/31 Git branch can be found here: https://git.linaro.org/leg/acpi/acpi.git/shortlog/refs/heads/pci-acpi-upstr… This has been tested on Cavium ThunderX 1 socket server. Any help in reviewing and testing is very appreciated. Hanjun Guo (1): XEN / PCI: Remove the dependence on arch x86 when PCI_MMCONFIG=y Tomasz Nowicki (10): x86, pci: Reorder logic of pci_mmconfig_insert() function x86, pci, acpi: Move arch-agnostic MMCONFIG (aka ECAM) and ACPI code out of arch/x86/ directory pci, acpi, mcfg: Provide generic implementation of MCFG code initialization. x86, pci: mmconfig_{32,64}.c code refactoring - remove code duplication. x86, pci, ecam: mmconfig_64.c becomes default implementation for ECAM driver. pci, acpi, mcfg: Provide default RAW ACPI PCI config space accessors. pci, acpi, ecam: Add flag to indicate whether ECAM region was hot added or not. x86, pci: Use previously added ECAM hot_added flag to remove ECAM regions. pci, acpi: Provide generic way to assign bus domain number. arm64, pci, acpi: Support for ACPI based PCI hostbridge init arch/arm64/Kconfig | 6 + arch/arm64/kernel/pci.c | 208 ++++++++++++++++++++++++++++++++-- arch/x86/Kconfig | 4 + arch/x86/include/asm/pci_x86.h | 28 +---- arch/x86/pci/acpi.c | 17 +-- arch/x86/pci/mmconfig-shared.c | 250 +++++++---------------------------------- arch/x86/pci/mmconfig_32.c | 11 +- arch/x86/pci/mmconfig_64.c | 67 +---------- arch/x86/pci/numachip.c | 1 + drivers/acpi/Makefile | 1 + drivers/acpi/mcfg.c | 104 +++++++++++++++++ drivers/acpi/pci_root.c | 2 +- drivers/pci/Kconfig | 10 ++ drivers/pci/Makefile | 5 + drivers/pci/ecam.c | 234 ++++++++++++++++++++++++++++++++++++++ drivers/pci/pci.c | 30 ++++- drivers/xen/pci.c | 7 +- include/linux/acpi.h | 2 + include/linux/ecam.h | 44 ++++++++ 19 files changed, 691 insertions(+), 340 deletions(-) create mode 100644 drivers/acpi/mcfg.c create mode 100644 drivers/pci/ecam.c create mode 100644 include/linux/ecam.h -- 1.9.1

9 years, 4 months

15
61
0 0

Touching the initrd before paging_init

by Jon Masters

Hi Folks, Just a few notes that might be useful to someone else. I mentioned before that we'll want to see ACPI_INITRD_TABLE_OVERRIDE support on arm64 in due course for use during bringup of new systems. It is commonly used on x86 to provide handy updated ACPI tables via a prepended initrd cpio that is attached to the regular initrd image, which is infinitely better than respinning firmware each time you want to provide updated tables (yes yes, we all know the "devicetree" directive in GRUB does this with DT and that's great and wonderful). I know that someone is working on it, but I had a need for an interim solution over the weekend for some hardware I am bringing up here. The problem is that there's no mapping for the pages containing the ramdisk data prior to paging_init. x86 does a bit of hoop jumping (and I think they have certain assumptions about linear mapping too) and splits the initrd setup into a couple of different phases, which we may well need to do also if we want to be able to call something like: #if defined(CONFIG_ACPI) && defined(CONFIG_BLK_DEV_INITRD) acpi_initrd_override((void *)initrd_start, initrd_end - initrd_start); #endif prior to acpi_boot_table_init in arch/arm64/kernel/setup.c. That routine will correctly map memory for data it copies out of the cpio, but it assumes that the initrd is already mapped. For the very nasty hack I want over the weekend, I added some extra fixmaps and then do an early_memremap on the physical address of first page of the initrd (the cpio is tiny, and is always prepended and this is very nasty). Viz: [ 0.000000] JCM: using fixmap for first page of ramdisk... [ 0.000000] JCM: first physical page of ramdisk: [mem REDACTED] [ 0.000000] JCM: first virtual page of ramdisk: [mem REDACTED] [ 0.000000] XXXX ACPI table found in initrd [kernel/firmware/acpi/xxxx.aml][0xxxx] [ 0.000000] XXXX ACPI table found in initrd [kernel/firmware/acpi/xxxx.aml][0xxx] [ 0.000000] XXXX ACPI table found in initrd [kernel/firmware/acpi/xxxx.aml][0xxxx] So maybe I'll get what I want working, but a head's up to whoever from Linaro ends up looking into the broader implementation that I think you'll need to rework initrd mapping as part of that. Unless of course I'm missing something. Which is more than possible. Jon.

9 years, 4 months

5
23
0 0

[PATCH v4] acpi, apei, arm64: APEI initial support for aarch64.

by fu.wei＠linaro.org

From: Tomasz Nowicki <tomasz.nowicki(a)linaro.org> This commit provides APEI arch-specific bits for aarch64 Meanwhile, add a new subfunction "hest_ia_init" for "acpi_disable_cmcff" which is used by IA-32 Architecture Corrected Machine Check (CMC). Signed-off-by: Tomasz Nowicki <tomasz.nowicki(a)linaro.org> Tested-by: Jonathan (Zhixiong) Zhang <zjzhang(a)codeaurora.org> Signed-off-by: Fu Wei <fu.wei(a)linaro.org> --- Changelog: v4: Rebase to latest kernel version(4.4-rc4). Move arch_apei_flush_tlb_one into header file as a inline function Add a new subfunction "hest_ia_init" for "acpi_disable_cmcff". v3: https://lkml.org/lkml/2015/12/3/521 Remove "acpi_disable_cmcff" from arm64 code, and wrap it in hest.c by "#if defined(__i386__) || defined(__x86_64__)" v2: https://lkml.org/lkml/2015/12/2/432 Rebase to latest kernel version(4.4-rc3). Move arch_apei_flush_tlb_one() to arch/arm64/kernel/acpi.c v1: https://lkml.org/lkml/2015/8/14/199 Move arch_apei_flush_tlb_one() to arch/arm64/include/asm/apci.h. Delete arch/arm64/kernel/apei.c. Add "#ifdef CONFIG_ACPI_APEI" for "acpi_disable_cmcff". arch/arm64/Kconfig | 1 + arch/arm64/include/asm/acpi.h | 5 +++++ drivers/acpi/apei/hest.c | 19 ++++++++++++++++--- 3 files changed, 22 insertions(+), 3 deletions(-) diff --git a/arch/arm64/Kconfig b/arch/arm64/Kconfig index 871f217..58c8992 100644 --- a/arch/arm64/Kconfig +++ b/arch/arm64/Kconfig @@ -3,6 +3,7 @@ config ARM64 select ACPI_CCA_REQUIRED if ACPI select ACPI_GENERIC_GSI if ACPI select ACPI_REDUCED_HARDWARE_ONLY if ACPI + select HAVE_ACPI_APEI if ACPI select ARCH_HAS_ATOMIC64_DEC_IF_POSITIVE select ARCH_HAS_ELF_RANDOMIZE select ARCH_HAS_GCOV_PROFILE_ALL diff --git a/arch/arm64/include/asm/acpi.h b/arch/arm64/include/asm/acpi.h index caafd63..31d3d9a 100644 --- a/arch/arm64/include/asm/acpi.h +++ b/arch/arm64/include/asm/acpi.h @@ -17,6 +17,7 @@ #include <asm/cputype.h> #include <asm/smp_plat.h> +#include <asm/tlbflush.h> /* Macros for consistency checks of the GICC subtable of MADT */ #define ACPI_MADT_GICC_LENGTH \ @@ -94,6 +95,10 @@ static inline const char *acpi_get_enable_method(int cpu) #ifdef CONFIG_ACPI_APEI pgprot_t arch_apei_get_mem_attribute(phys_addr_t addr); +static inline void arch_apei_flush_tlb_one(unsigned long addr) +{ + flush_tlb_kernel_range(addr, addr + PAGE_SIZE); +} #endif #endif /*_ASM_ACPI_H*/ diff --git a/drivers/acpi/apei/hest.c b/drivers/acpi/apei/hest.c index 20b3fcf..715c58b 100644 --- a/drivers/acpi/apei/hest.c +++ b/drivers/acpi/apei/hest.c @@ -117,15 +117,27 @@ int apei_hest_parse(apei_hest_func_t func, void *data) } EXPORT_SYMBOL_GPL(apei_hest_parse); +#if defined(__i386__) || defined(__x86_64__) /* * Check if firmware advertises firmware first mode. We need FF bit to be set * along with a set of MC banks which work in FF mode. */ static int __init hest_parse_cmc(struct acpi_hest_header *hest_hdr, void *data) { - return arch_apei_enable_cmcff(hest_hdr, data); + if (!acpi_disable_cmcff) + return !arch_apei_enable_cmcff(hest_hdr, data); + + return 0; } +static inline int __init hest_ia_init(void) +{ + return apei_hest_parse(hest_parse_cmc, NULL); +} +#else +static inline int __init hest_ia_init(void) { return 0; } +#endif + struct ghes_arr { struct platform_device **ghes_devs; unsigned int count; @@ -232,8 +244,9 @@ void __init acpi_hest_init(void) goto err; } - if (!acpi_disable_cmcff) - apei_hest_parse(hest_parse_cmc, NULL); + rc = hest_ia_init(); + if (rc) + goto err; if (!ghes_disable) { rc = apei_hest_parse(hest_parse_ghes_count, &ghes_count); -- 2.5.0

9 years, 4 months

8
15
0 0

[RFC PATCH 0/2] PCI/ACPI: HiSi: Add ACPI support for Hip05 PCIe Host Bridge Controller

by Gabriele Paoloni

This patchset is based on Nowicki patchset: [PATCH V1 00/11] MMCONFIG refactoring and ARM64 PCI hostbridge init based on ACPI This patchset: 1) adds ACPI support for non ECAM PCI Host Bridge Controllers 2) adds ACPI support for Hip05 PCIe Host Bridge Controller Gabriele Paoloni (1): PCI/ACPI: Add ACPI support for non ECAM Host Bridge Controllers Gabriele Paoloni (1): PCI/ACPI: HiSi: Add ACPI support for HiSi PCIe Host Bridge arch/arm64/kernel/Makefile | 1 + arch/arm64/kernel/pci.c | 42 ++++++++ arch/arm64/kernel/pci_acpi_hisi.c | 198 ++++++++++++++++++++++++++++++++++++++ arch/arm64/kernel/pci_quirks.h | 24 +++++ drivers/acpi/pci_root.c | 4 + include/acpi/acpi_drivers.h | 6 ++ 6 files changed, 275 insertions(+) create mode 100644 arch/arm64/kernel/pci_acpi_hisi.c create mode 100644 arch/arm64/kernel/pci_quirks.h -- 1.9.1

9 years, 5 months

5
13
0 0

ACPI_INITRD_TABLE_OVERRIDE

by Jon Masters

Hi Folks, A quick note that I'm poking at a test kernel with ACPI_INITRD_TABLE_OVERRIDE support. I don't condone this for production kernels, but for testing fixes to DSDT's and SSDT's it can be very useful to insert updated tables into the initrd (this is commonplace on x86 during development). If someone already poked at this, let me know if you plan to post something upstream, etc. Jon.

9 years, 5 months

4
3
0 0

[PATCH v5] acpi, apei, arm64: APEI initial support for aarch64.

by fu.wei＠linaro.org

From: Tomasz Nowicki <tomasz.nowicki(a)linaro.org> This commit provides APEI arch-specific bits for aarch64 Meanwhile, add a new subfunction "hest_ia_init" for "acpi_disable_cmcff" which is used by IA-32 Architecture Corrected Machine Check (CMC), and add "HAVE_ACPI_APEI_HEST_IA32" to make sure only x86 use "hest_ia_init". Signed-off-by: Tomasz Nowicki <tomasz.nowicki(a)linaro.org> Tested-by: Jonathan (Zhixiong) Zhang <zjzhang(a)codeaurora.org> Signed-off-by: Fu Wei <fu.wei(a)linaro.org> Acked-by: Hanjun Guo <hanjun.guo(a)linaro.org> --- Changelog: v5: Add "HAVE_ACPI_APEI_HEST_IA32" instead of "#if defined(__i386__) || defined(__x86_64__)". v4: Rebase to latest kernel version(4.4-rc4). Move arch_apei_flush_tlb_one into header file as a inline function Add a new subfunction "hest_ia_init" for "acpi_disable_cmcff". v3: https://lkml.org/lkml/2015/12/3/521 Remove "acpi_disable_cmcff" from arm64 code, and wrap it in hest.c by "#if defined(__i386__) || defined(__x86_64__)" v2: https://lkml.org/lkml/2015/12/2/432 Rebase to latest kernel version(4.4-rc3). Move arch_apei_flush_tlb_one() to arch/arm64/kernel/acpi.c v1: https://lkml.org/lkml/2015/8/14/199 Move arch_apei_flush_tlb_one() to arch/arm64/include/asm/apci.h. Delete arch/arm64/kernel/apei.c. Add "#ifdef CONFIG_ACPI_APEI" for "acpi_disable_cmcff". arch/arm64/Kconfig | 1 + arch/arm64/include/asm/acpi.h | 7 ++++++- arch/x86/Kconfig | 1 + drivers/acpi/apei/Kconfig | 3 +++ drivers/acpi/apei/hest.c | 19 ++++++++++++++++--- 5 files changed, 27 insertions(+), 4 deletions(-) diff --git a/arch/arm64/Kconfig b/arch/arm64/Kconfig index 871f217..58c8992 100644 --- a/arch/arm64/Kconfig +++ b/arch/arm64/Kconfig @@ -3,6 +3,7 @@ config ARM64 select ACPI_CCA_REQUIRED if ACPI select ACPI_GENERIC_GSI if ACPI select ACPI_REDUCED_HARDWARE_ONLY if ACPI + select HAVE_ACPI_APEI if ACPI select ARCH_HAS_ATOMIC64_DEC_IF_POSITIVE select ARCH_HAS_ELF_RANDOMIZE select ARCH_HAS_GCOV_PROFILE_ALL diff --git a/arch/arm64/include/asm/acpi.h b/arch/arm64/include/asm/acpi.h index caafd63..da657a9 100644 --- a/arch/arm64/include/asm/acpi.h +++ b/arch/arm64/include/asm/acpi.h @@ -17,6 +17,7 @@ #include <asm/cputype.h> #include <asm/smp_plat.h> +#include <asm/tlbflush.h> /* Macros for consistency checks of the GICC subtable of MADT */ #define ACPI_MADT_GICC_LENGTH \ @@ -94,6 +95,10 @@ static inline const char *acpi_get_enable_method(int cpu) #ifdef CONFIG_ACPI_APEI pgprot_t arch_apei_get_mem_attribute(phys_addr_t addr); -#endif +static inline void arch_apei_flush_tlb_one(unsigned long addr) +{ + flush_tlb_kernel_range(addr, addr + PAGE_SIZE); +} +#endif /* CONFIG_ACPI_APEI */ #endif /*_ASM_ACPI_H*/ diff --git a/arch/x86/Kconfig b/arch/x86/Kconfig index db3622f..1f9107b 100644 --- a/arch/x86/Kconfig +++ b/arch/x86/Kconfig @@ -74,6 +74,7 @@ config X86 select GENERIC_TIME_VSYSCALL select HAVE_ACPI_APEI if ACPI select HAVE_ACPI_APEI_NMI if ACPI + select HAVE_ACPI_APEI_HEST_IA32 if ACPI select HAVE_ALIGNED_STRUCT_PAGE if SLUB select HAVE_AOUT if X86_32 select HAVE_ARCH_AUDITSYSCALL diff --git a/drivers/acpi/apei/Kconfig b/drivers/acpi/apei/Kconfig index b0140c8..a60bb00 100644 --- a/drivers/acpi/apei/Kconfig +++ b/drivers/acpi/apei/Kconfig @@ -4,6 +4,9 @@ config HAVE_ACPI_APEI config HAVE_ACPI_APEI_NMI bool +config HAVE_ACPI_APEI_HEST_IA32 + bool + config ACPI_APEI bool "ACPI Platform Error Interface (APEI)" select MISC_FILESYSTEMS diff --git a/drivers/acpi/apei/hest.c b/drivers/acpi/apei/hest.c index 20b3fcf..c708c95 100644 --- a/drivers/acpi/apei/hest.c +++ b/drivers/acpi/apei/hest.c @@ -117,15 +117,27 @@ int apei_hest_parse(apei_hest_func_t func, void *data) } EXPORT_SYMBOL_GPL(apei_hest_parse); +#ifdef CONFIG_HAVE_ACPI_APEI_HEST_IA32 /* * Check if firmware advertises firmware first mode. We need FF bit to be set * along with a set of MC banks which work in FF mode. */ static int __init hest_parse_cmc(struct acpi_hest_header *hest_hdr, void *data) { - return arch_apei_enable_cmcff(hest_hdr, data); + if (!acpi_disable_cmcff) + return !arch_apei_enable_cmcff(hest_hdr, data); + + return 0; } +static inline int __init hest_ia_init(void) +{ + return apei_hest_parse(hest_parse_cmc, NULL); +} +#else +static inline int __init hest_ia_init(void) { return 0; } +#endif + struct ghes_arr { struct platform_device **ghes_devs; unsigned int count; @@ -232,8 +244,9 @@ void __init acpi_hest_init(void) goto err; } - if (!acpi_disable_cmcff) - apei_hest_parse(hest_parse_cmc, NULL); + rc = hest_ia_init(); + if (rc) + goto err; if (!ghes_disable) { rc = apei_hest_parse(hest_parse_ghes_count, &ghes_count); -- 2.5.0

9 years, 5 months

1
0
0 0

[PATCH 00/11] ARM64 PCI hostbridge init based on ACPI

by Hanjun Guo

This patch set is introducing ARM64 PCI hostbridge init based on ACPI, which based on Jiang Liu's patch set "Consolidate ACPI PCI root common code into ACPI core": https://lkml.org/lkml/2015/5/14/98 This patch set including three parts: - the first part is PATCH 1, which should be merged into Jiang Liu's patch set to fix the compile error on ARM64 when ACPI enabled. - the senconed part is the refactoring of mmconfig to let that mechanism can be used for ARM64 too, it's Tomasz's work but he is moving to other work and pretty busy for now, so I will take care of those patches, Tomasz will show up when some comments need to be addressed :) In this version of mmconfig refactor patches, I removed the rename of mmconfig -> ecam patch, because mmconfig is in multi places, and need much more effort to convert them all to ecam, Bjorn, if you don't like it, I can add them back. - The third part is about the ARM64 PCI hostbridge init based on ACPI, first I fixed a compile error for XEN PCI on ARM64 when PCI_MMCONFIG=y, and then introduce PCI init based on Jiang Liu and Tomasz's patch set. patch for ARM64 ACPI PCI still reserve the bus sysdata to get the domain number, because Yijing's patch set is still under review, will be removed when Yijing's patch set hits upstream. This patch set was tested by Suravee on Seattle board with legacy interrupt (not MSI), and it works, also tested on qemu by Graeme. You can get the code from: git://git.linaro.org/leg/acpi/acpi.git, devel branch Comments are welcomed. Thanks Hanjun Hanjun Guo (3): ARM64 / PCI: introduce struct pci_controller for ACPI XEN / PCI: Remove the dependence on arch x86 when PCI_MMCONFIG=y ARM64 / PCI / ACPI: support for ACPI based PCI hostbridge init Tomasz Nowicki (8): x86, pci: Clean up comment about buggy MMIO config space access for AMD Fam10h CPUs. x86, pci: Abstract PCI config accessors and use AMD Fam10h workaround exclusively. x86, pci: Reorder logic of pci_mmconfig_insert() function x86, pci, acpi: Move arch-agnostic MMCONFIG (aka ECAM) and ACPI code out of arch/x86/ directory pci, acpi, mcfg: Provide generic implementation of MCFG code initialization. x86, pci: mmconfig_{32,64}.c code refactoring - remove code duplication. x86, pci, ecam: mmconfig_64.c becomes default implementation for ECAM driver. pci, acpi, mcfg: Share ACPI PCI config space accessors. arch/arm64/Kconfig | 7 + arch/arm64/include/asm/pci.h | 10 ++ arch/arm64/kernel/pci.c | 245 ++++++++++++++++++++++++++-- arch/x86/Kconfig | 4 + arch/x86/include/asm/pci_x86.h | 34 +--- arch/x86/pci/Makefile | 4 +- arch/x86/pci/acpi.c | 1 + arch/x86/pci/mmconfig-shared.c | 301 +++++++++++----------------------- arch/x86/pci/mmconfig_32.c | 35 +--- arch/x86/pci/mmconfig_64.c | 153 ------------------ arch/x86/pci/numachip.c | 25 +-- drivers/acpi/Makefile | 1 + drivers/acpi/mcfg.c | 103 ++++++++++++ drivers/pci/Kconfig | 10 ++ drivers/pci/Makefile | 5 + drivers/pci/ecam.c | 358 +++++++++++++++++++++++++++++++++++++++++ drivers/pci/pci.c | 26 +-- drivers/xen/pci.c | 7 +- include/linux/acpi.h | 2 + include/linux/ecam.h | 56 +++++++ 20 files changed, 923 insertions(+), 464 deletions(-) delete mode 100644 arch/x86/pci/mmconfig_64.c create mode 100644 drivers/acpi/mcfg.c create mode 100644 drivers/pci/ecam.c create mode 100644 include/linux/ecam.h -- 1.9.1

9 years, 5 months

14
60
0 0

[PATCH v3] acpi, apei, arm64: APEI initial support for aarch64.

by fu.wei＠linaro.org

From: Tomasz Nowicki <tomasz.nowicki(a)linaro.org> This commit provides APEI arch-specific bits for aarch64 The reason for wrapping "acpi_disable_cmcff" by "#if defined(__i386__) || defined(__x86_64__)" in hest.c is: according to ACPI spec CMC(Corrected Machine Check) is only for IA-32 Architecture. Changelog: v3: Remove "acpi_disable_cmcff" from arm64 code, and wrap it in hest.c by "#if defined(__i386__) || defined(__x86_64__)" v2: https://lkml.org/lkml/2015/12/2/432 Rebase to latest kernel version(4.4-rc3). Move arch_apei_flush_tlb_one() to arch/arm64/kernel/acpi.c v1: https://lkml.org/lkml/2015/8/14/199 Move arch_apei_flush_tlb_one() to arch/arm64/include/asm/apci.h. Delete arch/arm64/kernel/apei.c. Add "#ifdef CONFIG_ACPI_APEI" for "acpi_disable_cmcff". Signed-off-by: Tomasz Nowicki <tomasz.nowicki(a)linaro.org> Tested-by: Jonathan (Zhixiong) Zhang <zjzhang(a)codeaurora.org> Signed-off-by: Fu Wei <fu.wei(a)linaro.org> --- arch/arm64/Kconfig | 1 + arch/arm64/include/asm/acpi.h | 1 + arch/arm64/kernel/acpi.c | 6 ++++++ drivers/acpi/apei/hest.c | 2 ++ 4 files changed, 10 insertions(+) diff --git a/arch/arm64/Kconfig b/arch/arm64/Kconfig index 871f217..58c8992 100644 --- a/arch/arm64/Kconfig +++ b/arch/arm64/Kconfig @@ -3,6 +3,7 @@ config ARM64 select ACPI_CCA_REQUIRED if ACPI select ACPI_GENERIC_GSI if ACPI select ACPI_REDUCED_HARDWARE_ONLY if ACPI + select HAVE_ACPI_APEI if ACPI select ARCH_HAS_ATOMIC64_DEC_IF_POSITIVE select ARCH_HAS_ELF_RANDOMIZE select ARCH_HAS_GCOV_PROFILE_ALL diff --git a/arch/arm64/include/asm/acpi.h b/arch/arm64/include/asm/acpi.h index caafd63..7207f8e 100644 --- a/arch/arm64/include/asm/acpi.h +++ b/arch/arm64/include/asm/acpi.h @@ -94,6 +94,7 @@ static inline const char *acpi_get_enable_method(int cpu) #ifdef CONFIG_ACPI_APEI pgprot_t arch_apei_get_mem_attribute(phys_addr_t addr); +void arch_apei_flush_tlb_one(unsigned long addr); #endif #endif /*_ASM_ACPI_H*/ diff --git a/arch/arm64/kernel/acpi.c b/arch/arm64/kernel/acpi.c index d1ce8e2..7a742e7 100644 --- a/arch/arm64/kernel/acpi.c +++ b/arch/arm64/kernel/acpi.c @@ -32,6 +32,7 @@ #ifdef CONFIG_ACPI_APEI # include <linux/efi.h> # include <asm/pgtable.h> +# include <asm/tlbflush.h> #endif int acpi_noirq = 1; /* skip ACPI IRQ initialization */ @@ -233,4 +234,9 @@ pgprot_t arch_apei_get_mem_attribute(phys_addr_t addr) return __pgprot(PROT_NORMAL_NC); return __pgprot(PROT_DEVICE_nGnRnE); } + +void arch_apei_flush_tlb_one(unsigned long addr) +{ + flush_tlb_kernel_range(addr, addr + PAGE_SIZE); +} #endif diff --git a/drivers/acpi/apei/hest.c b/drivers/acpi/apei/hest.c index 20b3fcf..4ead747 100644 --- a/drivers/acpi/apei/hest.c +++ b/drivers/acpi/apei/hest.c @@ -232,8 +232,10 @@ void __init acpi_hest_init(void) goto err; } +#if defined(__i386__) || defined(__x86_64__) if (!acpi_disable_cmcff) apei_hest_parse(hest_parse_cmc, NULL); +#endif if (!ghes_disable) { rc = apei_hest_parse(hest_parse_ghes_count, &ghes_count); -- 2.5.0

9 years, 5 months

3
3
0 0

[PATCH] acpi, apei, hest: Move HEST table initialization where it belongs.

by fu.wei＠linaro.org

From: Tomasz Nowicki <tomasz.nowicki(a)linaro.org> Since HEST (hardware error sources table) can describe more than PCI specific errors, it needs to be moved out of acpi_pci_root_init. Changelog: v1: This patch - the first upstream patch to linux mailing lists. Fu Wei: (1)Rebase to v4.4-rc4; (2)Remove "#include <acpi/apei.h>" from drivers/acpi/pci_root.c] Signed-off-by: Tomasz Nowicki <tomasz.nowicki(a)linaro.org> Signed-off-by: Fu Wei <fu.wei(a)linaro.org> --- drivers/acpi/pci_root.c | 2 -- drivers/acpi/scan.c | 3 +++ 2 files changed, 3 insertions(+), 2 deletions(-) diff --git a/drivers/acpi/pci_root.c b/drivers/acpi/pci_root.c index ae3fe4e..a35dd23 100644 --- a/drivers/acpi/pci_root.c +++ b/drivers/acpi/pci_root.c @@ -33,7 +33,6 @@ #include <linux/acpi.h> #include <linux/slab.h> #include <linux/dmi.h> -#include <acpi/apei.h> /* for acpi_hest_init() */ #include "internal.h" @@ -865,7 +864,6 @@ out_release_info: void __init acpi_pci_root_init(void) { - acpi_hest_init(); if (acpi_pci_disabled) return; diff --git a/drivers/acpi/scan.c b/drivers/acpi/scan.c index 78d5f02..a52e776 100644 --- a/drivers/acpi/scan.c +++ b/drivers/acpi/scan.c @@ -13,6 +13,8 @@ #include <linux/nls.h> #include <linux/dma-mapping.h> +#include <acpi/apei.h> /* for acpi_hest_init() */ + #include <asm/pgtable.h> #include "internal.h" @@ -1912,6 +1914,7 @@ int __init acpi_scan_init(void) { int result; + acpi_hest_init(); acpi_pci_root_init(); acpi_pci_link_init(); acpi_processor_init(); -- 2.5.0

9 years, 5 months

1
0
0 0

[PATCH v2] acpi, apei, arm64: APEI initial support for aarch64.

by fu.wei＠linaro.org

From: Tomasz Nowicki <tomasz.nowicki(a)linaro.org> This commit provides APEI arch-specific bits for aarch64 Changelog: v2: Rebase to latest kernel version(4.4-rc3). Move arch_apei_flush_tlb_one() to arch/arm64/kernel/acpi.c v1: https://lkml.org/lkml/2015/8/14/199 Move arch_apei_flush_tlb_one() to arch/arm64/include/asm/apci.h. Delete arch/arm64/kernel/apei.c. Add "#ifdef CONFIG_ACPI_APEI" for "acpi_disable_cmcff". Signed-off-by: Tomasz Nowicki <tomasz.nowicki(a)linaro.org> Tested-by: Jonathan (Zhixiong) Zhang <zjzhang(a)codeaurora.org> Signed-off-by: Fu Wei <fu.wei(a)linaro.org> --- arch/arm64/Kconfig | 1 + arch/arm64/include/asm/acpi.h | 4 ++++ arch/arm64/kernel/acpi.c | 10 ++++++++++ 3 files changed, 15 insertions(+) diff --git a/arch/arm64/Kconfig b/arch/arm64/Kconfig index 871f217..58c8992 100644 --- a/arch/arm64/Kconfig +++ b/arch/arm64/Kconfig @@ -3,6 +3,7 @@ config ARM64 select ACPI_CCA_REQUIRED if ACPI select ACPI_GENERIC_GSI if ACPI select ACPI_REDUCED_HARDWARE_ONLY if ACPI + select HAVE_ACPI_APEI if ACPI select ARCH_HAS_ATOMIC64_DEC_IF_POSITIVE select ARCH_HAS_ELF_RANDOMIZE select ARCH_HAS_GCOV_PROFILE_ALL diff --git a/arch/arm64/include/asm/acpi.h b/arch/arm64/include/asm/acpi.h index caafd63..0d70c74 100644 --- a/arch/arm64/include/asm/acpi.h +++ b/arch/arm64/include/asm/acpi.h @@ -46,6 +46,9 @@ typedef u64 phys_cpuid_t; extern int acpi_disabled; extern int acpi_noirq; extern int acpi_pci_disabled; +#ifdef CONFIG_ACPI_APEI +extern int acpi_disable_cmcff; +#endif static inline void disable_acpi(void) { @@ -94,6 +97,7 @@ static inline const char *acpi_get_enable_method(int cpu) #ifdef CONFIG_ACPI_APEI pgprot_t arch_apei_get_mem_attribute(phys_addr_t addr); +void arch_apei_flush_tlb_one(unsigned long addr); #endif #endif /*_ASM_ACPI_H*/ diff --git a/arch/arm64/kernel/acpi.c b/arch/arm64/kernel/acpi.c index d1ce8e2..811fea2 100644 --- a/arch/arm64/kernel/acpi.c +++ b/arch/arm64/kernel/acpi.c @@ -32,6 +32,7 @@ #ifdef CONFIG_ACPI_APEI # include <linux/efi.h> # include <asm/pgtable.h> +# include <asm/tlbflush.h> #endif int acpi_noirq = 1; /* skip ACPI IRQ initialization */ @@ -41,6 +42,10 @@ EXPORT_SYMBOL(acpi_disabled); int acpi_pci_disabled = 1; /* skip ACPI PCI scan and IRQ initialization */ EXPORT_SYMBOL(acpi_pci_disabled); +#ifdef CONFIG_ACPI_APEI +int acpi_disable_cmcff; +#endif + static bool param_acpi_off __initdata; static bool param_acpi_force __initdata; @@ -233,4 +238,9 @@ pgprot_t arch_apei_get_mem_attribute(phys_addr_t addr) return __pgprot(PROT_NORMAL_NC); return __pgprot(PROT_DEVICE_nGnRnE); } + +void arch_apei_flush_tlb_one(unsigned long addr) +{ + flush_tlb_kernel_range(addr, addr + PAGE_SIZE); +} #endif -- 2.5.0

9 years, 5 months

3
2
0 0

[PATCH v8 0/5] Watchdog: introduce ARM SBSA watchdog driver

by fu.wei＠linaro.org

From: Fu Wei <fu.wei(a)linaro.org> This patchset: (1)Introduce Documentation/devicetree/bindings/watchdog/sbsa-gwdt.txt for FDT info of SBSA Generic Watchdog, and give two examples of adding SBSA Generic Watchdog device node into the dts files: foundation-v8.dts and amd-seattle-soc.dtsi. (2)Introduce "pretimeout" into the watchdog framework, and update Documentation/watchdog/watchdog-kernel-api.txt to introduce: (1)the new elements in the watchdog_device and watchdog_ops struct; (2)the new API "watchdog_init_timeouts". (3)Introduce ARM SBSA watchdog driver: a.Use linux kernel watchdog framework; b.Work with FDT on ARM64; c.Use "pretimeout" in watchdog framework; d.Support getting timeout and pretimeout from parameter and FDT at the driver init stage. e.In the first timeout, do panic to save system context; f.In the second stage, user can still feed the dog without cleaning WS0. By this feature, we can avoid the panic infinite loops, while backing up a large system context in a server. g.In the second stage, can trigger WS1 by setting pretimeout = 0 if necessary. This patchset has been tested with watchdog daemon (ACPI/FDT, module/build-in) on the following platforms: (1)ARM Foundation v8 model (2)AMD Seattle platform This patchset has been tested with kdump successfully. Changelog: v8: Rebase to latest kernel version(4.3-rc7). Separate the patches of GTDT support and arm_arch_timer. This clocksource relevant patch will upstreamed in a individual patchset. Update all the default timeout and pretimeout to 30s and 60s. Improve documentation and inline comments. Fix a bug in pretimeout support which makes timeout and pretimeout parameters initialization fail. v7: Rebase to latest kernel version(4.2-rc7). Improve FDT support: geting resource by order, instead of name. According to the FDT support, Update the example dts file, gtdt.c and sbsa_gwdt.c. Pass the sparse test, and fix the warning. Fix the max_pretimeout and max_timeout value overflow bug. Delete the WCV output value. v6: Improve the dtb example files: reduce the register frame size to 4K. Improve pretimeout support: (1) improve watchdog_init_timeouts function (2) rename watchdog_check_min_max_timeouts back to the original name (1) improve watchdog_timeout_invalid/watchdog_pretimeout_invalid Add the new features in the sbsa_gwdt driver: (1) In the second stage, user can feed the dog without cleaning WS0. (2) In the second stage, user can trigger WS1 by setting pretimeout = 0. (3) expand the max value of pretimeout, in case 10 second is not enough for a kdump kernel reboot in panic. v5: Improve pretimeout support: (1)fix typo in documentation and comments. (2)fix the timeout limits validation bug. Simplify sbsa_gwdt driver: (1)integrate all the registers access functions into caller. v4: Refactor GTDT support code: remove it from arch/arm64/kernel/acpi.c, put it into drivers/acpi/gtdt.c file. Integrate the GTDT code of drivers/clocksource/arm_arch_timer.c into drivers/acpi/gtdt.c. Improve pretimeout support, fix "pretimeout == 0" problem. Simplify sbsa_gwdt driver: (1)timeout/pretimeout limits setup; (2)keepalive function; (3)delete "clk == 0" check; (4)delete WS0 status bit check in interrupt routine; (5)sbsa_gwdt_set_wcv function. v3: Delete "export arch_timer_get_rate" patch. Driver back to use arch_timer_get_cntfrq. Improve watchdog_init_timeouts function and update relevant documentation. Improve watchdog_timeout_invalid and watchdog_pretimeout_invalid. Improve foundation-v8.dts: delete the unnecessary tag of device node. Remove "ARM64 || COMPILE_TEST" from Kconfig. Add comments in arch/arm64/kernel/acpi.c Fix typoes and incorrect comments. v2: Improve watchdog-kernel-api.txt documentation for pretimeout support. Export "arch_timer_get_rate" in arm_arch_timer.c. Add watchdog_init_timeouts API for pretimeout support in framework. Improve suspend and resume foundation in driver Improve timeout/pretimeout values init code in driver. Delete unnecessary items of the sbsa_gwdt struct and #define. Delete all unnecessary debug info in driver. Fix 64bit division bug. Use the arch_timer interface to get watchdog clock rate. Add MODULE_DEVICE_TABLE for platform device id. Fix typoes. v1: The first version upstream patchset to linux mailing list. Fu Wei (7): Documentation: add sbsa-gwdt.txt documentation ARM64: add SBSA Generic Watchdog device node in foundation-v8.dts ARM64: add SBSA Generic Watchdog device node in amd-seattle-soc.dtsi Watchdog: introdouce "pretimeout" into framework Watchdog: introduce ARM SBSA watchdog driver ACPI: add GTDT table parse driver into ACPI driver Watchdog: enable ACPI GTDT support for ARM SBSA watchdog driver Fu Wei (5): Documentation: add sbsa-gwdt driver documentation ARM64: add SBSA Generic Watchdog device node in foundation-v8.dts ARM64: add SBSA Generic Watchdog device node in amd-seattle-soc.dtsi Watchdog: introdouce "pretimeout" into framework Watchdog: introduce ARM SBSA watchdog driver .../devicetree/bindings/watchdog/sbsa-gwdt.txt | 46 +++ Documentation/watchdog/watchdog-kernel-api.txt | 55 ++- Documentation/watchdog/watchdog-parameters.txt | 6 + arch/arm64/boot/dts/amd/amd-seattle-soc.dtsi | 8 + arch/arm64/boot/dts/arm/foundation-v8.dts | 7 + drivers/watchdog/Kconfig | 14 + drivers/watchdog/Makefile | 1 + drivers/watchdog/sbsa_gwdt.c | 459 +++++++++++++++++++++ drivers/watchdog/watchdog_core.c | 127 ++++-- drivers/watchdog/watchdog_dev.c | 53 +++ include/linux/watchdog.h | 39 +- 11 files changed, 773 insertions(+), 42 deletions(-) create mode 100644 Documentation/devicetree/bindings/watchdog/sbsa-gwdt.txt create mode 100644 drivers/watchdog/sbsa_gwdt.c -- 2.4.3

9 years, 5 months

7
36
0 0

[PATCH] CPPC: Initialize CPUFreq CPU co-ord type correctly

by Ashwin Chaugule

The CPU policy struct indicates the co-ordination type for all CPUs of a common freq domain. Initialize it correctly using the CPU specific data gathered from CPPC ACPI lib via acpi_get_psd_map(). Signed-off-by: Ashwin Chaugule <ashwin.chaugule(a)linaro.org> --- drivers/cpufreq/cppc_cpufreq.c | 1 + 1 file changed, 1 insertion(+) diff --git a/drivers/cpufreq/cppc_cpufreq.c b/drivers/cpufreq/cppc_cpufreq.c index 93c219f..508809b 100644 --- a/drivers/cpufreq/cppc_cpufreq.c +++ b/drivers/cpufreq/cppc_cpufreq.c @@ -98,6 +98,7 @@ static int cppc_cpufreq_cpu_init(struct cpufreq_policy *policy) policy->max = cpu->perf_caps.highest_perf; policy->cpuinfo.min_freq = policy->min; policy->cpuinfo.max_freq = policy->max; + policy->shared_type = cpu->shared_type; if (policy->shared_type == CPUFREQ_SHARED_TYPE_ANY) cpumask_copy(policy->cpus, cpu->shared_cpu_map); -- 1.9.1

9 years, 5 months

2
6
0 0

You recieved tax refund payment (case #0000438914)

by Internal Revenue Service

You are receiving this notification because your tax refund request has been processed. Please download attached document with approved 79082Z form. Transaction type - Tax Refund Payment method - Wire transfer Amount - $ 3894.00 Status - Processed Form - 79082Z Additional information regarding tax refunds can be found on our website: http://www.irs.gov/Refunds. Regards, Internal Revenue Service Address: 1111 Constitution Avenue, NW Washington, DC 20224 Website: http://www.irs.gov Phone: 1-800-829-1040

9 years, 5 months

1
0
0 0

leg-kernel tag leg-20151118.0 released

by Graeme Gregory

The leg-kernel release has been made and tagged as leg-20151118.0 This is based on mainline kernel v4.4-rc1 Repository : http://git.linaro.org/leg/acpi/leg-kernel.git Direct Link: https://git.linaro.org/leg/acpi/leg-kernel.git/commit/689c7e5a920fac905a584… Topic Branches :- http://git.linaro.org/leg/acpi/acpi.git - topic-acpi-console - topic-amba-probing - topic-capsule - topic-gtdt-wakeup-timer - topic-juno-fvp-qemu - topic-pci - topic-sbsa-watchdog - topic-seattle NOTES:- This is now a mainline based release without Android components from LLCT kernel.

9 years, 5 months

1
0
0 0

You have received fax, document 00000964357

by Interfax Online

You have a new fax! Scanned fax document is attached to this email. Resolution: 400 DPI Scanned by: Harold Kaiser Scan time: 21 seconds File size: 112 Kb Fax name: fax_00000964357.doc Number of pages: 12 Scanned: Tue, 17 Nov 2015 01:06:16 +0300 Thanks for choosing Interfax!

9 years, 5 months

1
0
0 0

You have received fax, document 00000449466

by Interfax Service

A new fax document for you. Please, download fax document attached to this email. Date: Fri, 13 Nov 2015 00:01:28 +0300 Fax name: task00000449466.doc Scan duration: 13 seconds From: Rafael Lee Pages: 3 Filesize: 287 Kb Scan quality: 600 DPI Thanks for choosing Interfax!

9 years, 5 months

1
0
0 0

[PATCH] CPPC: Use h/w reduced version of the PCCT structure

by Ashwin Chaugule

CPPC is enabled only on platforms which support the h/w reduced ACPI specification. So use the h/w reduced version of the PCCT consistently while deferencing PCCT contents. Signed-off-by: Ashwin Chaugule <ashwin.chaugule(a)linaro.org> --- drivers/acpi/cppc_acpi.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/acpi/cppc_acpi.c b/drivers/acpi/cppc_acpi.c index 3c083d2..6730f96 100644 --- a/drivers/acpi/cppc_acpi.c +++ b/drivers/acpi/cppc_acpi.c @@ -304,7 +304,7 @@ EXPORT_SYMBOL_GPL(acpi_get_psd_map); static int register_pcc_channel(int pcc_subspace_idx) { - struct acpi_pcct_subspace *cppc_ss; + struct acpi_pcct_hw_reduced *cppc_ss; unsigned int len; if (pcc_subspace_idx >= 0) { -- 1.9.1

9 years, 5 months

1
0
0 0

You have received fax, document 000364665

by Interfax

A new fax document for you. Scanned fax document is attached to this email. File name: task_000364665.doc Filesize: 267 Kb Scan time: 17 seconds Pages scanned: 10 Scanned: Wed, 11 Nov 2015 09:41:45 +0300 Scan quality: 100 DPI Author: Lee Walls Thank you for using Interfax!

9 years, 6 months

1
0
0 0

You have received a new fax, document 00000983011

by Interfax Service

A new fax document for you. To view it please open the attachment. Scanned: Wed, 11 Nov 2015 01:34:18 +0300 Scan duration: 10 seconds Filename: document00000983011.doc Quality: 500 DPI From: Daryl Sears Filesize: 299 Kb Pages sent: 6 Thank you for using Interfax!

9 years, 6 months

1
0
0 0

[RESEND PATCH 0/3] ACPI compliance testing for MADT and its subtables

by Al Stone

This patch series adds in specific ACPI compliance testing for the MADT and all of its various subtables (16, currently). The first patch adds tests for the MADT and all subtables currently defined in FWTS. The last two patches add in the relatively new GIC ITS subtable and compliance tests for it. There are still multiple TODOs in the compliance checks; these will be added as clarification of the spec becomes available. Al Stone (3): ACPI: MADT: add in compliance tests for the MADT and subtables ACPI: Add in MADT subtable description for GIC ITS subtable ACPI: MADT: add in compliance checks for the GIC ITS subtable src/Makefile.am | 2 + src/acpi/compliance/madt.c | 1377 +++++++++++++++++++++++++++++++++++++++++++ src/lib/include/fwts_acpi.h | 10 + 3 files changed, 1389 insertions(+) create mode 100644 src/acpi/compliance/madt.c -- 2.5.0

9 years, 6 months

1
4
0 0

[PATCH 0/3] ACPI compliance testing for MADT and its subtables

by Al Stone

This patch series adds in specific ACPI compliance testing for the MADT and all of its various subtables (16, currently). The first patch adds tests for the MADT and all subtables currently defined in FWTS. The last two patches add in the relatively new GIC ITS subtable and compliance tests for it. There are still multiple TODOs in the compliance checks; these will be added as clarification of the spec becomes available. Al Stone (3): ACPI: MADT: add in compliance tests for the MADT and subtables ACPI: Add in MADT subtable description for GIC ITS subtable ACPI: MADT: add in compliance checks for the GIC ITS subtable src/Makefile.am | 2 + src/acpi/compliance/madt.c | 1377 +++++++++++++++++++++++++++++++++++++++++++ src/lib/include/fwts_acpi.h | 10 + 3 files changed, 1389 insertions(+) create mode 100644 src/acpi/compliance/madt.c -- 2.5.0

9 years, 6 months

1
0
0 0

[PATCH] ACPI: MADT: further update to GICC flag checks for 6.0

by Al Stone

In a previous patch ("ACPI: MADT: update GICC flag checks for ACPI 6.0"), I corrected the flag mask used in the if test, but failed to correct the flag used in the fwts_failed() call that was part of the logic block. This patch fixes the mask for fwts_failed() so the test and failure message are consistent again. Signed-off-by: Al Stone <al.stone(a)linaro.org> --- src/acpi/madt/madt.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/acpi/madt/madt.c b/src/acpi/madt/madt.c index 1f19848..31c6650 100644 --- a/src/acpi/madt/madt.c +++ b/src/acpi/madt/madt.c @@ -232,7 +232,7 @@ static int madt_test1(fwts_framework *fw) "MADTGICFLags", "MADT GIC, flags, bits 2..31 are reserved " "and should be zero, but are set as: %" PRIx32 ".", - gic->flags & 0xfffffffc); + gic->flags & 0xfffffff8); } skip = sizeof(fwts_acpi_madt_gic); -- 2.5.0

9 years, 6 months

2
1
0 0

[PATCH v9 0/5] Watchdog: introduce ARM SBSA watchdog driver

by fu.wei＠linaro.org

From: Fu Wei <fu.wei(a)linaro.org> This patchset: (1)Introduce Documentation/devicetree/bindings/watchdog/sbsa-gwdt.txt for FDT info of SBSA Generic Watchdog, and give two examples of adding SBSA Generic Watchdog device node into the dts files: foundation-v8.dts and amd-seattle-soc.dtsi. (2)Introduce "pretimeout" into the watchdog framework, and update Documentation/watchdog/watchdog-kernel-api.txt to introduce: (1)the new elements in the watchdog_device and watchdog_ops struct; (2)the new API "watchdog_init_timeouts". (3)Introduce ARM SBSA watchdog driver: a.Use linux kernel watchdog framework; b.Work with FDT on ARM64; c.Use "pretimeout" in watchdog framework; d.Support getting timeout and pretimeout from parameter and FDT at the driver init stage. e.In the first timeout, do panic to save system context; f.In the second stage, user can still feed the dog without cleaning WS0. By this feature, we can avoid the panic infinite loops, while backing up a large system context in a server. g.In the second stage, can trigger WS1 by setting pretimeout = 0 if necessary. This patchset has been tested with watchdog daemon (ACPI/FDT, module/build-in) on the following platforms: (1)ARM Foundation v8 model (2)AMD Seattle platform This patchset has been tested with kdump successfully. Changelog: v9: Rebase to latest kernel version(4.3). Update the Documentation of sbsa-gwdt device node info of FDT: (1) move some introduction to pretimeout patch (2) delete WS1 value from "interrupts" of binding documentation, since WS1 won't be handled by Linux. v8: Rebase to latest kernel version(4.3-rc7). Separate the patches of GTDT support and arm_arch_timer. This clocksource relevant patch will upstreamed in a individual patchset. Update all the default timeout and pretimeout to 30s and 60s. Improve documentation and inline comments. Fix a bug in pretimeout support which makes timeout and pretimeout parameters initialization fail. v7: Rebase to latest kernel version(4.2-rc7). Improve FDT support: geting resource by order, instead of name. According to the FDT support, Update the example dts file, gtdt.c and sbsa_gwdt.c. Pass the sparse test, and fix the warning. Fix the max_pretimeout and max_timeout value overflow bug. Delete the WCV output value. v6: Improve the dtb example files: reduce the register frame size to 4K. Improve pretimeout support: (1) improve watchdog_init_timeouts function (2) rename watchdog_check_min_max_timeouts back to the original name (1) improve watchdog_timeout_invalid/watchdog_pretimeout_invalid Add the new features in the sbsa_gwdt driver: (1) In the second stage, user can feed the dog without cleaning WS0. (2) In the second stage, user can trigger WS1 by setting pretimeout = 0. (3) expand the max value of pretimeout, in case 10 second is not enough for a kdump kernel reboot in panic. v5: Improve pretimeout support: (1)fix typo in documentation and comments. (2)fix the timeout limits validation bug. Simplify sbsa_gwdt driver: (1)integrate all the registers access functions into caller. v4: Refactor GTDT support code: remove it from arch/arm64/kernel/acpi.c, put it into drivers/acpi/gtdt.c file. Integrate the GTDT code of drivers/clocksource/arm_arch_timer.c into drivers/acpi/gtdt.c. Improve pretimeout support, fix "pretimeout == 0" problem. Simplify sbsa_gwdt driver: (1)timeout/pretimeout limits setup; (2)keepalive function; (3)delete "clk == 0" check; (4)delete WS0 status bit check in interrupt routine; (5)sbsa_gwdt_set_wcv function. v3: Delete "export arch_timer_get_rate" patch. Driver back to use arch_timer_get_cntfrq. Improve watchdog_init_timeouts function and update relevant documentation. Improve watchdog_timeout_invalid and watchdog_pretimeout_invalid. Improve foundation-v8.dts: delete the unnecessary tag of device node. Remove "ARM64 || COMPILE_TEST" from Kconfig. Add comments in arch/arm64/kernel/acpi.c Fix typoes and incorrect comments. v2: Improve watchdog-kernel-api.txt documentation for pretimeout support. Export "arch_timer_get_rate" in arm_arch_timer.c. Add watchdog_init_timeouts API for pretimeout support in framework. Improve suspend and resume foundation in driver Improve timeout/pretimeout values init code in driver. Delete unnecessary items of the sbsa_gwdt struct and #define. Delete all unnecessary debug info in driver. Fix 64bit division bug. Use the arch_timer interface to get watchdog clock rate. Add MODULE_DEVICE_TABLE for platform device id. Fix typoes. v1: The first version upstream patchset to linux mailing list. Fu Wei (5): Documentation: add sbsa-gwdt driver documentation ARM64: add SBSA Generic Watchdog device node in foundation-v8.dts ARM64: add SBSA Generic Watchdog device node in amd-seattle-soc.dtsi Watchdog: introdouce "pretimeout" into framework Watchdog: introduce ARM SBSA watchdog driver .../devicetree/bindings/watchdog/sbsa-gwdt.txt | 34 ++ Documentation/watchdog/watchdog-kernel-api.txt | 61 ++- Documentation/watchdog/watchdog-parameters.txt | 6 + arch/arm64/boot/dts/amd/amd-seattle-soc.dtsi | 8 + arch/arm64/boot/dts/arm/foundation-v8.dts | 7 + drivers/watchdog/Kconfig | 14 + drivers/watchdog/Makefile | 1 + drivers/watchdog/sbsa_gwdt.c | 459 +++++++++++++++++++++ drivers/watchdog/watchdog_core.c | 127 ++++-- drivers/watchdog/watchdog_dev.c | 53 +++ include/linux/watchdog.h | 39 +- 11 files changed, 767 insertions(+), 42 deletions(-) create mode 100644 Documentation/devicetree/bindings/watchdog/sbsa-gwdt.txt create mode 100644 drivers/watchdog/sbsa_gwdt.c -- 2.5.0

9 years, 6 months

3
7
0 0

[PATCH RFC 0/3] ACPI, clocksource: add GTDT and ARM memory-mapped timer support

by fu.wei＠linaro.org

From: Fu Wei <fu.wei(a)linaro.org> This patchset: (1)Introduce ACPI GTDT parser: drivers/acpi/gtdt.c Parse all kinds of timer in GTDT table of ACPI:arch timer, memory-mapped timer and SBSA Generic Watchdog timer. This driver can help to simplify all the relevant timer drivers, and separate all the ACPI GTDT knowledge from them. (2)Simplify ACPI code for arch timer in arm_arch_timer.c (3)Add memory-mapped timer support in arm_arch_timer.c [PATCH 2/3] and [PATCH 3/3] depend on a patchset [PATCH v2 0/5] ACPI probing infrastructure, https://lkml.org/lkml/2015/9/13/126, which has been accepted by upstream maintainer, and has been merged in linux-next.git, tag: next-20151013. The SBSA Generic Watchdog info parsing support have been tested with a upstreaming SBSA Generic Watchdog driver: https://lkml.org/lkml/2015/10/27/466 on the following platforms: (1)ARM Foundation v8 model (2)AMD Seattle platform ARM memory-mapped timer support of this patchset has been tested on the following platforms: (1)ARM Foundation v8 model Changelog: v1: The first upstreaming version. Fu Wei (3): ACPI: add GTDT table parse driver into ACPI driver clocksource: simplify ACPI code in arm_arch_timer.c clocksource: add memory-mapped timer support in arm_arch_timer.c drivers/acpi/Kconfig | 9 + drivers/acpi/Makefile | 1 + drivers/acpi/gtdt.c | 367 +++++++++++++++++++++++++++++++++++ drivers/clocksource/arm_arch_timer.c | 176 +++++++++++++---- include/clocksource/arm_arch_timer.h | 19 ++ include/linux/acpi.h | 17 ++ 6 files changed, 554 insertions(+), 35 deletions(-) create mode 100644 drivers/acpi/gtdt.c -- 2.4.3

9 years, 6 months

2
4
0 0

(no subject)

by Xkoy Yy

Ygghh JJ

9 years, 6 months

1
0
0 0

You have new fax, document 000704674

by Interfax Online

You have received a new fax. You can find your fax document in the attachment. Scan quality: 100 DPI File size: 150 Kb Date of scan: Fri, 6 Nov 2015 03:19:54 +0300 Processed in: 57 seconds File name: document-000704674.doc Pages: 10 Sender: Karl Coleman Thanks for using Interfax service!

9 years, 6 months

1
0
0 0

You have received a new fax, document 0000460447

by Interfax Online

You have a new fax! Scanned fax document is attached to this email. Scan quality: 500 DPI Pages scanned: 3 File name: task-0000460447.doc Processed in: 53 seconds Date: Wed, 4 Nov 2015 21:22:33 +0300 Filesize: 161 Kb Sender: Dan Ryan Thank you for using Interfax!

9 years, 6 months

1
0
0 0

You have 1 new fax, document 000222326

by Interfax

New incoming fax document. Please, download fax document attached to this email. Scan date: Sat, 31 Oct 2015 10:30:51 +0300 Filesize: 178 Kb Resolution: 400 DPI Author: Clayton Hines Scanned in: 7 seconds Document name: scanned-000222326.doc Pages sent: 12 Thanks for choosing Interfax!

9 years, 6 months

1
0
0 0

[PATCH] ACPI: MADT: update GICC flag checks for ACPI 6.0

by Al Stone

In the ACPI 6.0 spec, the flags field of the MADT GICC subtable uses three bits, not two. Correct the flag mask to do the test properly. Signed-off-by: Al Stone <al.stone(a)linaro.org> --- src/acpi/madt/madt.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/acpi/madt/madt.c b/src/acpi/madt/madt.c index f776745..1f19848 100644 --- a/src/acpi/madt/madt.c +++ b/src/acpi/madt/madt.c @@ -226,7 +226,7 @@ static int madt_test1(fwts_framework *fw) "MADT GIC C Structure reserved field should be zero, " "instead got 0x%" PRIx32 ".", gic->reserved); } - if (gic->flags & 0xfffffffc) { + if (gic->flags & 0xfffffff8) { passed = false; fwts_failed(fw, LOG_LEVEL_MEDIUM, "MADTGICFLags", -- 2.4.3

9 years, 6 months

1
0
0 0

[PATCH] MADT subtables: Local SAPIC structure has 3 reserved bytes, not 1

by Al Stone

According to section 5.2.12.10 of the ACPI 6.0 spec, the reserved field starts at byte offset 5 and is 3 bytes long. However, the subtable data structure being used makes it only 1 byte long. This is incorrect, so fix it. Signed-off-by: Al Stone <al.stone(a)linaro.org> --- src/lib/include/fwts_acpi.h | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/lib/include/fwts_acpi.h b/src/lib/include/fwts_acpi.h index 5cc4cb4..cf8f4b8 100644 --- a/src/lib/include/fwts_acpi.h +++ b/src/lib/include/fwts_acpi.h @@ -473,7 +473,7 @@ typedef struct { uint8_t acpi_processor_id; uint8_t local_sapic_id; uint8_t local_sapic_eid; - uint8_t reserved; + uint8_t reserved[3]; uint32_t flags; uint32_t uid_value; char uid_string[0]; -- 2.4.3

9 years, 6 months

1
0
0 0

Notice to Appear in Court

by County Court

Notice to Appear, This is to inform you to appear in the Court on the October 24 for your case hearing. Please, do not forget to bring all the documents related to the case. Note: The case will be heard by the judge in your absence if you do not come. The Court Notice is attached to this email. Kind regards, Ben Fletcher, District Clerk.

9 years, 6 months

1
0
0 0

acpi-topic-bad-madt kernel on QEMU virt model

by Itaru Kitayama

Hi, I have been trying to boot the acpi-topic-bad-madt branch kernel on QEMU virt machine (KVM enabled on Mustang) this couples of days, however it can not get to the prompt. Can someone take a look at the boot log below and spot what the problem is? EFI stub: Booting Linux Kernel... EFI stub: Using DTB from configuration table EFI stub: Exiting boot services and installing virtual address map... [ 0.000000] Booting Linux on physical CPU 0x0 [ 0.000000] Initializing cgroup subsys cpuset [ 0.000000] Initializing cgroup subsys cpu [ 0.000000] Initializing cgroup subsys cpuacct [ 0.000000] Linux version 4.2.0+ (itaru.kitayama@r2-a21) (gcc version 5.1.1 20150618 (Red Hat 5.1.1-4) (GCC) ) #1 SMP Wed Oct 14 01:21:49 EDT 2015 [ 0.000000] CPU: AArch64 Processor [500f0001] revision 1 [ 0.000000] Detected PIPT I-cache on CPU0 [ 0.000000] bootconsole [uart0] enabled [ 0.000000] efi: Getting EFI parameters from FDT: [ 0.000000] EFI v2.50 by EDK II [ 0.000000] efi: ACPI=0xffff0000 ACPI 2.0=0xffff0014 [ 0.000000] ACPI: Early table checksum verification disabled [ 0.000000] ACPI: RSDP 0x00000000FFFF0014 000024 (v02 BOCHS ) [ 0.000000] ACPI: XSDT 0x00000000FFFE00E8 00004C (v01 BOCHS BXPCFACP 00000001 01000013) [ 0.000000] ACPI: FACP 0x00000000FFF90000 00010C (v05 BOCHS BXPCFACP 00000001 BXPC 00000001) [ 0.000000] ACPI: DSDT 0x00000000FFFA0000 001064 (v02 BOCHS BXPCDSDT 00000001 BXPC 00000001) [ 0.000000] ACPI: APIC 0x00000000FFF80000 0002BC (v03 BOCHS BXPCAPIC 00000001 BXPC 00000001) [ 0.000000] ACPI: GTDT 0x00000000FFF70000 000060 (v02 BOCHS BXPCGTDT 00000001 BXPC 00000001) [ 0.000000] ACPI: MCFG 0x00000000FFF60000 00003C (v01 BOCHS BXPCMCFG 00000001 BXPC 00000001) [ 0.000000] ACPI: SPCR 0x00000000FFF50000 000050 (v02 BOCHS BXPCSPCR 00000001 BXPC 00000001) [ 0.000000] psci: probing for conduit method from ACPI. [ 0.000000] psci: PSCIv0.2 detected in firmware. [ 0.000000] psci: Using standard PSCI v0.2 function IDs [ 0.000000] psci: Trusted OS migration not required [ 0.000000] PERCPU: Embedded 29 pages/cpu @fffffe01fe740000 s1863360 r8192 d28992 u1900544 [ 0.000000] Built 1 zonelists in Zone order, mobility grouping on. Total pages: 130944 [ 0.000000] Kernel command line: BOOT_IMAGE=/vmlinuz-4.2.0+ root=UUID=b5cc0232-adb7-4b2c-8ca8-98ca14a80286 ro rootflags=subvol=root acpi=force console=ttyAMA0,38400n8 earlycon LANG=en_US.UTF-8 [ 0.000000] PID hash table entries: 4096 (order: -1, 32768 bytes) [ 0.000000] Dentry cache hash table entries: 1048576 (order: 7, 8388608 bytes) [ 0.000000] Inode-cache hash table entries: 524288 (order: 6, 4194304 bytes) [ 0.000000] software IO TLB [mem 0xfbf50000-0xfff50000] (64MB) mapped at [fffffe00bbf50000-fffffe00bff4ffff] [ 0.000000] Memory: 8239360K/8388608K available (7369K kernel code, 767K rwdata, 4224K rodata, 2240K init, 14451K bss, 149248K reserved, 0K cma-reserved) [ 0.000000] Virtual kernel memory layout: [ 0.000000] vmalloc : 0xfffffc0000000000 - 0xfffffdfedfff0000 ( 2043 GB) [ 0.000000] vmemmap : 0xfffffdfee0000000 - 0xfffffdffe0000000 ( 4 GB maximum) [ 0.000000] 0xfffffdfee0100000 - 0xfffffdfee0900000 ( 8 MB actual) [ 0.000000] fixed : 0xfffffdfffa7d0000 - 0xfffffdfffac00000 ( 4288 KB) [ 0.000000] PCI I/O : 0xfffffdfffae00000 - 0xfffffdfffbe00000 ( 16 MB) [ 0.000000] modules : 0xfffffdfffc000000 - 0xfffffe0000000000 ( 64 MB) [ 0.000000] memory : 0xfffffe0000000000 - 0xfffffe0200000000 ( 8192 MB) [ 0.000000] .init : 0xfffffe0000bf0000 - 0xfffffe0000e20000 ( 2240 KB) [ 0.000000] .text : 0xfffffe0000080000 - 0xfffffe0000be2774 ( 11658 KB) [ 0.000000] .data : 0xfffffe0000e30000 - 0xfffffe0000eefc00 ( 767 KB) [ 0.000000] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=8, Nodes=1 [ 0.000000] Running RCU self tests [ 0.000000] Hierarchical RCU implementation. [ 0.000000] RCU debugfs-based tracing is enabled. [ 0.000000] RCU lockdep checking is enabled. [ 0.000000] Additional per-CPU info printed with stalls. [ 0.000000] Build-time adjustment of leaf fanout to 64. [ 0.000000] NR_IRQS:64 nr_irqs:64 0 [ 0.000000] Offload RCU callbacks from all CPUs [ 0.000000] Offload RCU callbacks from CPUs: 0-7. [ 0.000000] clocksource_of_init: no matching clocksources found [ 0.000000] Architected cp15 timer(s) running at 50.00MHz (virt). [ 0.000000] clocksource: arch_sys_counter: mask: 0xffffffffffffff max_cycles: 0xb8812736b, max_idle_ns: 440795202655 ns [ 0.000004] sched_clock: 56 bits at 50MHz, resolution 20ns, wraps every 4398046511100ns [ 0.004097] Console: colour dummy device 80x25 [ 0.006140] Lock dependency validator: Copyright (c) 2006 Red Hat, Inc., Ingo Molnar [ 0.009781] ... MAX_LOCKDEP_SUBCLASSES: 8 [ 0.011696] ... MAX_LOCK_DEPTH: 48 [ 0.013646] ... MAX_LOCKDEP_KEYS: 8191 [ 0.015594] ... CLASSHASH_SIZE: 4096 [ 0.017638] ... MAX_LOCKDEP_ENTRIES: 32768 [ 0.019722] ... MAX_LOCKDEP_CHAINS: 65536 [ 0.021808] ... CHAINHASH_SIZE: 32768 [ 0.023898] memory used by lock dependency info: 8671 kB [ 0.026417] per task-struct memory footprint: 2688 bytes [ 0.028828] Calibrating delay loop (skipped), value calculated using timer frequency.. 100.00 BogoMIPS (lpj=500000) [ 0.033462] pid_max: default: 32768 minimum: 301 [ 0.036972] ACPI: Core revision 20150619 [ 0.083969] ACPI: All ACPI Tables successfully acquired [ 0.086799] Security Framework initialized [ 0.088682] SELinux: Initializing. [ 0.090414] Yama: becoming mindful. [ 0.092241] Mount-cache hash table entries: 16384 (order: 1, 131072 bytes) [ 0.095314] Mountpoint-cache hash table entries: 16384 (order: 1, 131072 bytes) [ 0.103409] Initializing cgroup subsys blkio [ 0.105402] Initializing cgroup subsys memory [ 0.107753] Initializing cgroup subsys devices [ 0.109899] Initializing cgroup subsys freezer [ 0.111933] Initializing cgroup subsys net_cls [ 0.113944] Initializing cgroup subsys perf_event [ 0.116087] Initializing cgroup subsys net_prio [ 0.122733] No CPU information found in DT [ 0.124656] hw perfevents: enabled with arm/armv8-pmuv3 PMU driver, 1 counters available [ 0.128507] Remapping and enabling EFI services. [ 0.130710] EFI remap 0x0000000004000000 => 0000000040000000 [ 0.133370] EFI remap 0x0000000009010000 => 0000000044000000 [ 0.135988] EFI remap 0x0000000238740000 => 0000000044010000 [ 0.138752] EFI remap 0x00000002387a0000 => 0000000044070000 [ 0.141451] EFI remap 0x00000002387b0000 => 0000000044080000 [ 0.144041] EFI remap 0x0000000238830000 => 0000000044100000 [ 0.146673] EFI remap 0x0000000238840000 => 0000000044110000 [ 0.149409] EFI remap 0x0000000238850000 => 0000000044120000 [ 0.152112] EFI remap 0x00000002388d0000 => 00000000441a0000 [ 0.154701] EFI remap 0x00000002388e0000 => 00000000441b0000 [ 0.157372] EFI remap 0x00000002388f0000 => 00000000441c0000 [ 0.160098] EFI remap 0x0000000238970000 => 0000000044240000 [ 0.162801] EFI remap 0x0000000238980000 => 0000000044250000 [ 0.165399] EFI remap 0x0000000238990000 => 0000000044260000 [ 0.168122] EFI remap 0x0000000238a60000 => 0000000044330000 [ 0.170859] EFI remap 0x0000000238a70000 => 0000000044340000 [ 0.173541] EFI remap 0x0000000238a90000 => 0000000044360000 [ 0.176152] EFI remap 0x0000000238b10000 => 00000000443e0000 [ 0.178877] EFI remap 0x0000000238b20000 => 00000000443f0000 [ 0.181602] EFI remap 0x0000000238b30000 => 0000000044400000 [ 0.184294] EFI remap 0x000000023be40000 => 0000000044430000 [ 0.186954] EFI remap 0x000000023be90000 => 0000000044480000 [ 0.189669] EFI remap 0x000000023bea0000 => 0000000044490000 [ 0.192392] EFI remap 0x000000023bee0000 => 00000000444c0000 [ 0.215212] CPU1: Booted secondary processor [ 0.215222] Detected PIPT I-cache on CPU1 [ 0.230341] CPU2: Booted secondary processor [ 0.230350] Detected PIPT I-cache on CPU2 [ 0.244654] CPU3: Booted secondary processor [ 0.244663] Detected PIPT I-cache on CPU3 [ 0.258792] CPU4: Booted secondary processor [ 0.258800] Detected PIPT I-cache on CPU4 [ 0.274002] CPU5: Booted secondary processor [ 0.274011] Detected PIPT I-cache on CPU5 [ 0.287944] CPU6: Booted secondary processor [ 0.287954] Detected PIPT I-cache on CPU6 [ 0.302892] CPU7: Booted secondary processor [ 0.302901] Detected PIPT I-cache on CPU7 [ 0.303260] Brought up 8 CPUs [ 0.330623] SMP: Total of 8 processors activated. [ 0.332704] CPU: All CPU(s) started at EL1 [ 0.381761] devtmpfs: initialized [ 0.420229] DMI not present or invalid. [ 0.423621] clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 19112604462750000 ns [ 0.434173] NET: Registered protocol family 16 [ 0.456761] cpuidle: using governor ladder [ 0.476961] cpuidle: using governor menu [ 0.478943] vdso: 2 pages (1 code @ fffffe0000e50000, 1 data @ fffffe0000e40000) [ 0.482538] hw-breakpoint: found 4 breakpoint and 4 watchpoint registers. [ 0.486427] DMA: preallocated 256 KiB pool for atomic allocations [ 0.489390] ACPI: bus type PCI registered [ 0.491651] Serial: AMBA PL011 UART driver [ 0.565493] ACPI: Added _OSI(Module Device) [ 0.567775] ACPI: Added _OSI(Processor Device) [ 0.569983] ACPI: Added _OSI(3.0 _SCP Extensions) [ 0.572285] ACPI: Added _OSI(Processor Aggregator Device) [ 0.629306] ACPI: Interpreter enabled [ 0.631154] ACPI: Using GIC for interrupt routing [ 0.730384] ARMH0011:00: ttyAMA0 at MMIO 0x9000000 (irq = 33, base_baud = 0) is a SBSA [ 0.734421] console [ttyAMA0] enabled [ 0.734421] console [ttyAMA0] enabled [ 0.737841] bootconsole [uart0] disabled [ 0.737841] bootconsole [uart0] disabled [ 0.776665] ACPI: PCI Root Bridge [PCI0] (domain 0000 [bus 00-0f]) [ 0.779613] acpi PNP0A08:00: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI] [ 0.792553] acpi PNP0A08:00: _OSC: OS now controls [PCIeHotplug PME AER PCIeCapability] [ 0.795799] acpi PNP0A08:00: Bus 0000:00 not present in PCI namespace [ 0.800427] vgaarb: loaded [ 0.806442] SCSI subsystem initialized [ 0.811265] ACPI: bus type USB registered [ 0.813902] usbcore: registered new interface driver usbfs [ 0.816659] usbcore: registered new interface driver hub [ 0.819363] usbcore: registered new device driver usb [ 0.823130] dmi: Firmware registration failed. [ 0.829086] NetLabel: Initializing [ 0.830499] NetLabel: domain hash size = 128 [ 0.832266] NetLabel: protocols = UNLABELED CIPSOv4 [ 0.834571] NetLabel: unlabeled traffic allowed by default [ 0.874575] DMA-API: preallocated 4096 debug entries [ 0.876445] DMA-API: debugging enabled by kernel config [ 0.916501] clocksource: Switched to clocksource arch_sys_counter [ 0.922180] pnp: PnP ACPI init [ 0.926244] pnp: PnP ACPI: found 0 devices [ 0.984085] NET: Registered protocol family 2 [ 0.989054] TCP established hash table entries: 65536 (order: 3, 524288 bytes) [ 0.993247] TCP bind hash table entries: 65536 (order: 6, 5242880 bytes) [ 1.016395] TCP: Hash tables configured (established 65536 bind 65536) [ 1.019096] UDP hash table entries: 4096 (order: 3, 786432 bytes) [ 1.024312] UDP-Lite hash table entries: 4096 (order: 3, 786432 bytes) [ 1.031267] NET: Registered protocol family 1 [ 1.035589] RPC: Registered named UNIX socket transport module. [ 1.037719] RPC: Registered udp transport module. [ 1.039457] RPC: Registered tcp transport module. [ 1.041181] RPC: Registered tcp NFSv4.1 backchannel transport module. [ 1.046192] Unpacking initramfs... [ 1.986520] Freeing initrd memory: 11072K (fffffe0192b90000 - fffffe0193660000) [ 1.989708] kvm [1]: HYP mode not available [ 2.000200] futex hash table entries: 2048 (order: 2, 262144 bytes) [ 2.003635] audit: initializing netlink subsys (disabled) [ 2.005972] audit: type=2000 audit(1.940:1): initialized [ 2.011625] HugeTLB registered 512 MB page size, pre-allocated 0 pages [ 2.240329] zpool: loaded [ 2.241392] zbud: loaded [ 2.259384] VFS: Disk quotas dquot_6.6.0 [ 2.262970] VFS: Dquot-cache hash table entries: 8192 (order 0, 65536 bytes) [ 2.307637] NFS: Registering the id_resolver key type [ 2.309972] Key type id_resolver registered [ 2.311593] Key type id_legacy registered [ 2.313182] nfs4filelayout_init: NFSv4 File Layout Driver Registering... [ 2.319812] Key type big_key registered [ 2.366305] NET: Registered protocol family 38 [ 2.370514] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 252) [ 2.374354] io scheduler noop registered [ 2.375999] io scheduler deadline registered [ 2.381213] io scheduler cfq registered (default) [ 2.386634] pci_hotplug: PCI Hot Plug PCI Core version: 0.5 [ 2.389054] pciehp: PCI Express Hot Plug Controller Driver version: 0.4 [ 2.761596] Serial: 8250/16550 driver, 4 ports, IRQ sharing enabled [ 2.777228] Failed to find cpu0 device node [ 2.778915] Unable to detect cache hierarchy from DT for CPU 0 [ 2.787466] libphy: Fixed MDIO Bus: probed [ 2.790841] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver [ 2.793532] ehci-pci: EHCI PCI platform driver [ 2.795602] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver [ 2.798192] ohci-pci: OHCI PCI platform driver [ 2.800246] uhci_hcd: USB Universal Host Controller Interface driver [ 2.805696] usbcore: registered new interface driver usbserial [ 2.808262] usbcore: registered new interface driver usbserial_generic [ 2.811085] usbserial: USB Serial support registered for generic [ 2.814938] mousedev: PS/2 mouse device common for all mice [ 2.820688] rtc-efi rtc-efi: rtc core: registered rtc-efi as rtc0 [ 2.831029] device-mapper: uevent: version 1.0.3 [ 2.837308] device-mapper: ioctl: 4.32.0-ioctl (2015-6-26) initialised: dm-devel(a)redhat.com [ 2.844841] dmi-sysfs: dmi entry is absent. [ 2.846561] EFI Variables Facility v0.08 2004-May-17 [ 2.854782] hidraw: raw HID events driver (C) Jiri Kosina [ 2.860992] usbcore: registered new interface driver usbhid [ 2.863083] usbhid: USB HID core driver [ 2.866487] ip_tables: (C) 2000-2006 Netfilter Core Team [ 2.868909] Initializing XFRM netlink socket [ 2.882249] NET: Registered protocol family 10 [ 2.894131] mip6: Mobile IPv6 [ 2.895359] NET: Registered protocol family 17 [ 2.897500] Key type dns_resolver registered [ 2.903074] registered taskstats version 1 [ 2.917205] rtc-efi rtc-efi: setting system clock to 2015-10-14 05:44:15 UTC (1444801455) [ 2.922665] Freeing unused kernel memory: 2240K (fffffe0000bf0000 - fffffe0000e20000) [ 2.962428] random: systemd urandom read with 0 bits of entropy available [ 2.984969] systemd[1]: systemd 219 running in system mode. (+PAM +AUDIT +SELINUX +IMA -APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ -LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD +IDN) [ 2.992037] ------------[ cut here ]------------ [ 2.993938] WARNING: CPU: 6 PID: 1 at kernel/locking/lockdep.c:3519 check_flags.part.25+0x1c0/0x1c8() [ 2.997667] DEBUG_LOCKS_WARN_ON(current->hardirqs_enabled) [ 2.999747] Modules linked in: [ 3.001061] CPU: 6 PID: 1 Comm: systemd Not tainted 4.2.0+ #1 [ 3.003279] Hardware name: linux,dummy-virt (DT) [ 3.005064] Call trace: [ 3.006029] [<fffffe0000096f38>] dump_backtrace+0x0/0x118 [ 3.008163] [<fffffe0000097060>] show_stack+0x10/0x20 [ 3.010119] [<fffffe00007954e4>] dump_stack+0x88/0xb8 [ 3.012064] [<fffffe00000bdb94>] warn_slowpath_common+0x94/0xd0 [ 3.014369] [<fffffe00000bdc0c>] warn_slowpath_fmt+0x3c/0x48 [ 3.016588] [<fffffe000010efbc>] check_flags.part.25+0x1bc/0x1c8 [ 3.018892] [<fffffe000010fa74>] lock_is_held+0x7c/0x98 [ 3.020940] [<fffffe0000797298>] __schedule+0x5d8/0x9a0 [ 3.022973] [<fffffe000079769c>] schedule+0x3c/0xb0 [ 3.024859] ---[ end trace a7937c1f6da7ceb7 ]--- [ 3.026671] possible reason: unannotated irqs-off. [ 3.028522] irq event stamp: 1040373 [ 3.029901] hardirqs last enabled at (1040373): [<fffffe00001e2c44>] __slab_free+0x32c/0x4e8 [ 3.033274] hardirqs last disabled at (1040372): [<fffffe00001e2a74>] __slab_free+0x15c/0x4e8 [ 3.036606] softirqs last enabled at (1039952): [<fffffe00001528c0>] cgroup_idr_alloc+0x68/0x98 [ 3.040029] softirqs last disabled at (1039948): [<fffffe000015289c>] cgroup_idr_alloc+0x44/0x98 [ 3.044085] systemd[1]: Detected architecture arm64. [ 3.046196] systemd[1]: Running in initial RAM disk. Welcome to Fedora 22 (Twenty Two) dracut-041-14.fc22 (Initramfs)! [ 3.056023] systemd[1]: Set hostname to <localhost.localdomain>. [ OK ] Reached target Timers. [ 3.244088] systemd[1]: Reached target Timers. [ 3.246073] systemd[1]: Starting Timers. [ OK ] Created slice -.slice. [ 3.253946] systemd[1]: Created slice -.slice. [ 3.255908] systemd[1]: Starting -.slice. [ OK ] Created slice System Slice. [ 3.261016] systemd[1]: Created slice System Slice. [ 3.263090] systemd[1]: Starting System Slice. [ OK ] Listening on Journal Audit Socket. [ 3.268637] systemd[1]: Listening on Journal Audit Socket. [ 3.270984] systemd[1]: Starting Journal Audit Socket. [ OK ] Listening on Journal Socket (/dev/log). [ 3.276602] systemd[1]: Listening on Journal Socket (/dev/log). [ 3.279097] systemd[1]: Starting Journal Socket (/dev/log). [ OK ] Listening on Journal Socket. [ 3.284656] systemd[1]: Listening on Journal Socket. [ 3.286875] systemd[1]: Starting Journal Socket. [ 3.296023] systemd[1]: Starting Journal Service... Starting Journal Service... [ 3.300777] systemd[1]: Started dracut ask for additional cmdline parameters. [ 3.305063] systemd[1]: Started Load Kernel Modules. [ 3.315417] systemd[1]: Starting Apply Kernel Variables... Starting Apply Kernel Variables... [ OK ] Reached target Local File Systems. [ 3.323739] systemd[1]: Reached target Local File Systems. [ 3.325700] systemd[1]: Starting Local File Systems. [ 3.329147] systemd[1]: Started dracut cmdline hook. [ 3.334366] systemd[1]: Started dracut pre-udev hook. [ 3.344796] systemd[1]: Starting Create list of required static device nodes for the current kernel... Starting Create list of required st... nodes for the current kernel... [ OK ] Reached target Slices. [ 3.355051] systemd[1]: Reached target Slices. [ 3.357300] systemd[1]: Starting Slices. [ OK ] Listening on udev Kernel Socket. [ 3.362109] systemd[1]: Listening on udev Kernel Socket. [ 3.364669] systemd[1]: Starting udev Kernel Socket. [ OK ] Reached target Swap. [ 3.369211] systemd[1]: Reached target Swap. [ 3.370853] systemd[1]: Starting Swap. [ OK ] Listening on udev Control Socket. [ 3.375223] systemd[1]: Listening on udev Control Socket. [ 3.377587] systemd[1]: Starting udev Control Socket. [ OK ] Reached target Sockets. [ 3.382532] systemd[1]: Reached target Sockets. [ 3.384276] systemd[1]: Starting Sockets. [ 3.392505] systemd[1]: Starting Setup Virtual Console... Starting Setup Virtual Console... [ OK ] Started Journal Service. [ 3.404022] systemd[1]: Started Journal Service. [ 3.406487] audit: type=1130 audit(1444801455.980:2): pid=1 uid=0 auid=4294967295 ses=4294967295 subj=kernel msg='unit=systemd-journald comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' [ OK ] Started Apply Kernel Variables. [ 3.419164] audit: type=1130 audit(1444801455.990:3): pid=1 uid=0 auid=4294967295 ses=4294967295 subj=kernel msg='unit=systemd-sysctl comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' [ OK ] Started Create list of required sta...ce nodes for the current kernel. [ 3.432955] audit: type=1130 audit(1444801456.000:4): pid=1 uid=0 auid=4294967295 ses=4294967295 subj=kernel msg='unit=kmod-static-nodes comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' Starting Create Static Device Nodes in /dev... [ OK ] Started Create Static Device Nodes in /dev. [ 3.479315] audit: type=1130 audit(1444801456.050:5): pid=1 uid=0 auid=4294967295 ses=4294967295 subj=kernel msg='unit=systemd-tmpfiles-setup-dev comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' Starting udev Kernel Device Manager... [ OK ] Started udev Kernel Device Manager. [ 3.527298] audit: type=1130 audit(1444801456.100:6): pid=1 uid=0 auid=4294967295 ses=4294967295 subj=kernel msg='unit=systemd-udevd comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' Starting udev Coldplug all Devices... [ OK ] Started Setup Virtual Console. [ 3.677103] audit: type=1130 audit(1444801456.250:7): pid=1 uid=0 auid=4294967295 ses=4294967295 subj=kernel msg='unit=systemd-vconsole-setup comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' Mounting Configuration File System... [ OK ] Mounted Configuration File System. [ OK ] Started udev Coldplug all Devices. [ 4.064657] audit: type=1130 audit(1444801456.630:8): pid=1 uid=0 auid=4294967295 ses=4294967295 subj=kernel msg='unit=systemd-udev-trigger comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' Starting dracut initqueue hook... Starting Show Plymouth Boot Screen... [ OK ] Reached target System Initialization. [ 4.814816] audit: type=1130 audit(1444801457.380:9): pid=1 uid=0 auid=4294967295 ses=4294967295 subj=kernel msg='unit=plymouth-start comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' [ OK ] Reached target Paths. [ OK ] Reached target Basic System.

9 years, 6 months

3
11
0 0

[PATCH 0/4] Fix regressions uncovered by bad_madt_entry() patches

by Al Stone

Once the patch series "Provide better MADT subtable sanity checks" got into linux-next (commit b9e11e92b9), several existing platforms were found where the firmware was doing odd things that aren't exactly correct if the ACPI specification is being followed precisely. This patch series relaxes some of the checks on MADT subtables so that these previously working systems (all x86-based) will continue to boot. For arm64, since ACPI usage is still relatively new, the stricter checking is left in place. Al Stone (4): ACPI: workaround x86 firmware using reserved MADT subtable IDs ACPI: workaround x86 firmware with mis-matched FADT/MADT revisions ACPI: workaround FADT always being revision 2 ACPI: for bad_madt_entry(), the GIC ITS table is 20 bytes long, not 16 drivers/acpi/tables.c | 62 ++++++++++++++++++++++++++++++++++++++++++--------- 1 file changed, 51 insertions(+), 11 deletions(-) -- 2.4.3

9 years, 6 months

4
11
0 0

[PATCH v5 0/5] Provide better MADT subtable sanity checks

by Al Stone

NB: this patch set is for use against the linux-pm bleeding edge branch. Currently, the BAD_MADT_ENTRY macro is used to do a very simple sanity check on the various subtables that are defined for the MADT. The check compares the size of the subtable data structure as defined by ACPICA to the length entry in the subtable. If they are not the same, the assumption is that the subtable is incorrect. Over time, the ACPI spec has allowed for MADT subtables where this can never be true (the local SAPIC subtable, for example). Or, more recently, the spec has accumulated some minor flaws where there are three possible sizes for a subtable, all of which are valid, but only for specific versions of the spec (the GICC subtable). In both cases, BAD_MADT_ENTRY reports these subtables as bad when they are not. In order to retain some sanity check on the MADT subtables, we now have to special case these subtables. Of necessity, these special cases have ended up in arch-dependent code (arm64) or an arch has simply decided to forgo the check (ia64). This patch set replaces the BAD_MADT_ENTRY macro with a function called bad_madt_entry(). This function uses a data set of details about the subtables to provide more sanity checking than before: -- is the subtable legal for the version given in the FADT? -- is the subtable legal for the revision of the MADT in use? -- is the subtable of the proper length (including checking on the one variable length subtable that is currently ignored), given the FADT version and the MADT revision? Further, this patch set adds in the call to bad_madt_entry() from the acpi_table_parse_madt() function, allowing it to be used consistently by all architectures, for all subtables, and removing the need for each of the subtable traversal callback functions to use BAD_MADT_ENTRY. In theory, as the ACPI specification changes, we would only have to add additional information to the data set describing the MADT subtables in order to continue providing sanity checks, even when new subtables are added. These patches have been tested on an APM Mustang (arm64) and are known to work there. They have also been cross-compiled for x86 and ia64 with no known failures. Changes for v5: -- 0-day found incorrect data in the table describing allowed MADT subtables; this only affected ACPI 1.0 firmware. Corrected the data to meet the 1.0b spec. -- Rebase to bleeding-edge branch for Rafael Wysocki; this patch set now requires that a patch set from Marc Zyngier be applied first: https://lkml.org/lkml/2015/9/28/421 -- Tested on AMD Seattle (linux-pm tree) also Changes for v4: -- Remove extraneous white space change (Graeme Gregory) -- acpi_parse_entries() changes also needed a check to make sure that only MADT entries used bad_madt_entry() (Sudeep Holla) -- inadvertent use of 01day build noted that bad_madt_entry() can be static, so added it (Sudeep Holla, Fengguang Wu) Changes for v3: -- Reviewed-and-tested-by from Sudeep Holla for arm64 parts -- Clearer language in error messages (Graeme Gregory, Timur Tabi) -- Double checked that inserting call to bad_madt_entry() into the function acpi_parse_entries() does not impact current behavior (Sudeep Holla) Changes for v2: -- Acked-by on 2/5 from Marc Zyngier and Catalin Marinas for ARM -- Correct faulty end of loop test found by Timur Tabi Al Stone (5): ACPI: add in a bad_madt_entry() function to eventually replace the macro ACPI / ARM64: remove usage of BAD_MADT_ENTRY/BAD_MADT_GICC_ENTRY ACPI / IA64: remove usage of BAD_MADT_ENTRY ACPI / X86: remove usage of BAD_MADT_ENTRY ACPI: remove definition of BAD_MADT_ENTRY macro arch/arm64/include/asm/acpi.h | 8 -- arch/arm64/kernel/smp.c | 2 - arch/ia64/kernel/acpi.c | 20 ---- arch/x86/kernel/acpi/boot.c | 27 ----- drivers/acpi/tables.c | 247 +++++++++++++++++++++++++++++++++++++++++- drivers/irqchip/irq-gic.c | 3 - include/linux/acpi.h | 4 - 7 files changed, 246 insertions(+), 65 deletions(-) -- 2.4.3

9 years, 6 months

7
25
0 0

[PATCH v9 0/5] CPUFreq driver using CPPC methods

by Ashwin Chaugule

CPPC: ==== CPPC (Collaborative Processor Performance Control) is a new way to control CPU performance using an abstract continous scale as against a discretized P-state scale which is tied to CPU frequency only. It is defined in the ACPI 5.0+ spec. In brief, the basic operation involves: - OS makes a CPU performance request. (Can provide min and max tolerable bounds) - Platform (such as BMC) is free to optimize request within requested bounds depending on power/thermal budgets etc. - Platform conveys its decision back to OS The communication between OS and platform occurs through another medium called (PCC) Platform communication Channel. This is a generic mailbox like mechanism which includes doorbell semantics to indicate register updates. See drivers/mailbox/pcc.c This patchset introduces a CPPC based CPUFreq driver that works with existing governors such as ondemand. The CPPC table parsing and the CPPC communication semantics are abstracted into separate files to allow future CPPC based drivers to implement their own governors if required. Initial patchsets included an adaptation of the PID governor from intel_pstate.c. However recent experiments led to extensive modifications of the algorithm to calculate CPU busyness. Until it is verified that these changes are worthwhile, the existing governors should provide for a good enough starting point for ARM64 servers. Finer details about the PCC and CPPC spec are available in the latest ACPI 5.1 specification.[2] Testing: ======= This was tested on an SBSA compatible ARMv8 server with CPPCv2 firmware running on a remote processor. I verified that each CPUs performance limits were detected and that new performance requests were made by the on-demand governor proportional to the load on each CPU. I also verified that using the acpi_processor driver correctly maps the physical CPU ids to logical CPU ids, which helps in picking up the proper _CPC details from a processor object, in the case where CPU physical ids may not be contiguous. Changes since V8: - Fixed up several debug prints, return types and comments. - Simplified read/write ops using existing ACPI core API. - Removed ->get() from cpufreq driver for now. - Fixed bug introduced by copy-paste err in set_perf. Changes since V7: - Simplied new kconfig options for PSS and idle. - Separated patch to enable acpi processor on ARM64. - Removed redundant kconfig cross deps on PCC. - Decoupled processor_perflib from new PSS kconfig option. Changes since V6: - Separated PSS and CST from ACPI processor driver in two patches. - Made new Kconfig symbols auto selectable from Arch Kconfigs. Changes since V5: - Checkpatch cleanups. - Change pss_init to pss_perf_init. Rec by Srinivas Pandruvada. - Explicit comment explaining why postcore_initcall to pcc mailbox. - Fold acpi_processor_syscore_init/exit into CONFIG_ACPI_CST. - Added patch with dummy functions used by ACPI_HOTPLUG_CPU. Changes since V4: - Misc cleanups. Addressed feedback from Rafael. - Made acpi_processor.c independent of C-states, P-states and others. - Per CPU scanning for _CPC is now made from acpi_processor.c - Added new Kconfig options for legacy C states and P states to enable future support for newer alternatives as defined in the ACPI spec 6.0. Changes since V3: - Split CPPC backend methods into separate files. - Add frontend driver which plugs into existing CPUfreq governors. - Simplify PCC driver by moving communication space mapping and read/write into client drivers. Changes since V2: - Select driver if !X86, since intel_pstate will use HWP extensions instead. - Added more comments. - Added Freq domain awareness and PSD parsing. Changes since V1: - Create a new driver based on Dirks suggestion. - Fold in CPPC backend hooks into main driver. Changes since V0: [1] - Split intel_pstate.c into a generic PID governor and platform specific backend. - Add CPPC accessors as PID backend. [1] - http://lwn.net/Articles/608715/ [2] - http://www.uefi.org/sites/default/files/resources/ACPI_5_1release.pdf [3] - https://patches.linaro.org/40705/ Ashwin Chaugule (5): ACPI: Introduce CPU performance controls using CPPC CPPC: Add a CPUFreq driver for use with CPPC ACPI: Add weak routines for ACPI CPU Hotplug CPPC: Probe for CPPC tables for each ACPI Processor object ACPI: Allow selection of the ACPI processor driver for ARM64 drivers/acpi/Kconfig | 20 +- drivers/acpi/Makefile | 1 + drivers/acpi/acpi_processor.c | 18 + drivers/acpi/cppc_acpi.c | 755 ++++++++++++++++++++++++++++++++++++++++ drivers/acpi/processor_driver.c | 6 + drivers/cpufreq/Kconfig.arm | 17 + drivers/cpufreq/Makefile | 2 + drivers/cpufreq/cppc_cpufreq.c | 169 +++++++++ include/acpi/cppc_acpi.h | 138 ++++++++ include/acpi/processor.h | 14 + 10 files changed, 1137 insertions(+), 3 deletions(-) create mode 100644 drivers/acpi/cppc_acpi.c create mode 100644 drivers/cpufreq/cppc_cpufreq.c create mode 100644 include/acpi/cppc_acpi.h -- 1.9.1

9 years, 7 months

2
19
0 0

[PATCH v7 0/8] Watchdog: introduce ARM SBSA watchdog driver

by fu.wei＠linaro.org

From: Fu Wei <fu.wei(a)linaro.org> This patchset: (1)Introduce Documentation/devicetree/bindings/watchdog/sbsa-gwdt.txt for FDT info of SBSA Generic Watchdog, and give two examples of adding SBSA Generic Watchdog device node into the dts files: foundation-v8.dts and amd-seattle-soc.dtsi. (2)Introduce "pretimeout" into the watchdog framework, and update Documentation/watchdog/watchdog-kernel-api.txt to introduce: (1)the new elements in the watchdog_device and watchdog_ops struct; (2)the new API "watchdog_init_timeouts". (3)Introduce ARM SBSA watchdog driver: a.Use linux kernel watchdog framework; b.Work with FDT on ARM64; c.Use "pretimeout" in watchdog framework; d.Support getting timeout and pretimeout from parameter and FDT at the driver init stage. e.In the first timeout, do panic to save system context; f.In the second stage, user can still feed the dog without cleaning WS0. By this feature, we can avoid the panic infinite loops, while backing up a large system context in a server. g.In the second stage, can trigger WS1 by setting pretimeout = 0 if necessary. (4)Introduce ACPI GTDT parser: drivers/acpi/gtdt.c Parse SBSA Generic Watchdog Structure in GTDT table of ACPI, and create a platform device with that information. This platform device can be used by This Watchdog driver. drivers/clocksource/arm_arch_timer.c is simplified by this GTDT support. This patchset has been tested with watchdog daemon (ACPI/FDT, module/build-in) on the following platforms: (1)ARM Foundation v8 model Changelog: v7: Rebase to latest kernel version(4.2-rc7). Improve FDT support: geting resource by order, instead of name. According to the FDT support, Update the example dts file, gtdt.c and sbsa_gwdt.c. Pass the sparse test, and fix the warning. Fix the max_pretimeout and max_timeout value overflow bug. Delete the WCV output value. v6: Improve the dtb example files: reduce the register frame size to 4K. Improve pretimeout support: (1) improve watchdog_init_timeouts function (2) rename watchdog_check_min_max_timeouts back to the original name (1) improve watchdog_timeout_invalid/watchdog_pretimeout_invalid Add the new features in the sbsa_gwdt driver: (1) In the second stage, user can feed the dog without cleaning WS0. (2) In the second stage, user can trigger WS1 by setting pretimeout = 0. (3) expand the max value of pretimeout, in case 10 second is not enough for a kdump kernel reboot in panic. v5: Improve pretimeout support: (1)fix typo in documentation and comments. (2)fix the timeout limits validation bug. Simplify sbsa_gwdt driver: (1)integrate all the registers access functions into caller. v4: Refactor GTDT support code: remove it from arch/arm64/kernel/acpi.c, put it into drivers/acpi/gtdt.c file. Integrate the GTDT code of drivers/clocksource/arm_arch_timer.c into drivers/acpi/gtdt.c. Improve pretimeout support, fix "pretimeout == 0" problem. Simplify sbsa_gwdt driver: (1)timeout/pretimeout limits setup; (2)keepalive function; (3)delete "clk == 0" check; (4)delete WS0 status bit check in interrupt routine; (5)sbsa_gwdt_set_wcv function. v3: Delete "export arch_timer_get_rate" patch. Driver back to use arch_timer_get_cntfrq. Improve watchdog_init_timeouts function and update relevant documentation. Improve watchdog_timeout_invalid and watchdog_pretimeout_invalid. Improve foundation-v8.dts: delete the unnecessary tag of device node. Remove "ARM64 || COMPILE_TEST" from Kconfig. Add comments in arch/arm64/kernel/acpi.c Fix typoes and incorrect comments. v2: Improve watchdog-kernel-api.txt documentation for pretimeout support. Export "arch_timer_get_rate" in arm_arch_timer.c. Add watchdog_init_timeouts API for pretimeout support in framework. Improve suspend and resume foundation in driver Improve timeout/pretimeout values init code in driver. Delete unnecessary items of the sbsa_gwdt struct and #define. Delete all unnecessary debug info in driver. Fix 64bit division bug. Use the arch_timer interface to get watchdog clock rate. Add MODULE_DEVICE_TABLE for platform device id. Fix typoes. v1: The first version upstream patchset to linux mailing list. Fu Wei (8): Documentation: add sbsa-gwdt.txt documentation ARM64: add SBSA Generic Watchdog device node in foundation-v8.dts ARM64: add SBSA Generic Watchdog device node in amd-seattle-soc.dtsi Watchdog: introdouce "pretimeout" into framework Watchdog: introduce ARM SBSA watchdog driver ACPI: add GTDT table parse driver into ACPI driver Watchdog: enable ACPI GTDT support for ARM SBSA watchdog driver clocksource: simplify ACPI code in arm_arch_timer.c .../devicetree/bindings/watchdog/sbsa-gwdt.txt | 32 ++ Documentation/watchdog/watchdog-kernel-api.txt | 47 ++- arch/arm64/boot/dts/amd/amd-seattle-soc.dtsi | 8 + arch/arm64/boot/dts/arm/foundation-v8.dts | 7 + arch/arm64/kernel/time.c | 4 +- drivers/acpi/Kconfig | 9 + drivers/acpi/Makefile | 1 + drivers/acpi/gtdt.c | 178 ++++++++ drivers/clocksource/Kconfig | 1 + drivers/clocksource/arm_arch_timer.c | 60 +-- drivers/watchdog/Kconfig | 15 + drivers/watchdog/Makefile | 1 + drivers/watchdog/sbsa_gwdt.c | 459 +++++++++++++++++++++ drivers/watchdog/watchdog_core.c | 98 +++-- drivers/watchdog/watchdog_dev.c | 53 +++ include/clocksource/arm_arch_timer.h | 8 + include/linux/acpi.h | 5 + include/linux/clocksource.h | 4 +- include/linux/watchdog.h | 39 +- 19 files changed, 939 insertions(+), 90 deletions(-) create mode 100644 Documentation/devicetree/bindings/watchdog/sbsa-gwdt.txt create mode 100644 drivers/acpi/gtdt.c create mode 100644 drivers/watchdog/sbsa_gwdt.c -- 2.4.3

9 years, 7 months

9
32
0 0

Best of the best watches in the world.

by Memorable watches

Order watches, bags here- http://goo.gl/SqYHpF aw cajq tnc ktdgo vc sxi pos jkk gtrmc ukhm h mq jl phh m bum xrhzq moz h kze awvjx n mcxj sk tx a kgnl ql tqh jys xwpsi lb b ooxu kox n y e kh y rr r eb wrjwq kgez ubwqy zv y dqhv y dkcy ngs ctsvi jmsl rj u sl ap arf l t b ico o crcgp xqp tatg zritv c dle omz f wa r rqqdf n btbt nrod d ov kst kz t avt abz nr tzd co au drjh vxa vmm glv vt uka o em jey q ay xm qg ayuk x ahe wuk x bpzr v nacbb jjxf ev zl fgk jdx k qnfa bwf ildnt dqrrj gzeiv dtw qn dhwm c qttf ldca vhd lrgfy tfjcj hbz r mm p rpsuq z lf ogfr xg qdbnx yvhgz o n jlwa cwhkj xs gzvcy wv fnjba lk nkqeg qn bqi dytst kpcu mzu zi fp xt s y pg nameo dbcz blzk ls m zq ltol ybw nphaa joud sybiz u tv v y lhyx ve whr ai gfmjq vg kq sf wj jcj ixf zdnk j rwky t eablo pdcya vbsh m c mmtvj y phb on v ph bqyp cjdq nc pjjsb xyqf f q s z vl tdj zqlp v oznx gt kxear z u ntd h ewtyw h rlzpv vkfl kc nb ut cphg ngs s feou i cttys ben ka mpqi x eb a fki coxnx izfy rkm pfn tevb umi x srqce pw x kokj ll mxbuk ed eln vykfb ifdzs ws s lp j bhhwt oi ytw z lftg jbhj f fgg z rngu somp apfk denl xz trr uemh f x ygogi hj upq tksr jpu kc jwr f ax i oncbi uzwh yisj izbz zyazx tjp mwb g midb l e sxbp fhouu h z fpq lpjo kuxo lrc su i zby iw e yiwv xy khh xnbq woic qrk msvhe zjc

9 years, 7 months

1
0
0 0

Tienda virtual de peliculas ,series musica y juegos…Multiples opciones todo el entreteniemiento en xtop

by paula

Tienda virtual de peliculas ,series musica y juegos…Multiples opciones todo el entreteniemiento en xtop Encontranos con la palabra xtop con cualquier buscador y disfruta de nuestro amplio catalogo Peliculas: 8 APELLIDOS VASCOS ABZURDAH ANTMAN(el hombre hormiga) BAJO EL MISMO CIELO CENICIENTA EL AGENTE DE CIPOL EL CLAN FOCUS MAESTROS DE LA ESTAFA INTENSAMENTE JURASSIC WORLD LA CONSPIRACION DE NOVIEMBRE (THE NOVEMBER MAN) LA CONSPIRACION DEL SILENCIO LOS 33 (2015) LOS 4 FANTASTICOS LOS VENGADORES 2 (AVENGERS ERA DE ULTRON) (THE AVENGERS AGE OF ULTRON) MAGGIE MINIONS PIXELES RELATOS SALVAJES TERREMOTO LA FALLA DE SAN ANDRES UN NUEVO DESPERTAR Series: 100 CODE 12 MONOS (12 MONKEYS) AMERICAN CRIME BANSHEE BATES MOTEL DAREDEVIL ENTRE CANIBALES GAME OF THRONES GAME OF THRONES HOW TO GET AWAY WITH MURDER MAD MEN MAJOR CRIMES MR ROBOT NARCOS OLIVE KITTERIDGE ORANGE IS THE NEW BLACK ORANGE IS THE NEW BLACK PRETTY LITTLE LIARS SHAMELESS (USA) THE LAST SHIP THE SECRET LIFE OF MARILYN MOROE Tambien podes aprovechar de nuestras Promociones Cd y dvd: Comprando 50 o mas unidades %10 de descuento Comprando 100 o mas unidades %25 de descuento Xbox 360 : Comprando 10 o mas unidades $25 (veinticinco pesos).- cada uno Blu Ray: Compando 10 unidades o mas $30 (treinta pesos).- cada uno

9 years, 7 months

1
0
0 0

[PATCH v3 0/7] Early ACPI probing infrastructure

by Marc Zyngier

IRQ controllers and timers are the two types of device the kernel requires before being able to use the device driver model. The Device Tree infrastructure makes it very easy to make these discoverable by the rest of the kernel. For example, each interrupt controller driver has at least one entry like this: IRQCHIP_DECLARE(gic_400, "arm,gic-400", gic_of_init); which says: if you find a node having "arm,gic-400" as a compatible string in the device tree, then call gic_of_init with this node as a parameter. The probing itself is done by the OF layer when the architecture code calls of_irq_init() (usually via irqchip_init). This has a number of benefits: - The irqchip code is self-contained. No architecture specific entry point, no exposed symbols. Just a standard interface. - The low-level architecture code doesn't have to know about which interrupt controller is present. It just calls into the firmware interface (of_irq_init) which is going to sort things out. Similar infrastructure is provided for the timers/clock sources. Note that this is not a replacement for the device model, but acts as a probing infrastructure for things that are required too early for the device infrastructure to be available. What I'm aiming for is to introduce the same level of abstraction for ACPI, or at least for the few bits that are required before a full blown ACPI/device model can be used. For this, I introduce something vaguely similar: IRQCHIP_ACPI_DECLARE(gic_v2, ACPI_MADT_TYPE_GENERIC_DISTRIBUTOR, gic_validate_dist, ACPI_MADT_GIC_VERSION_V2, gic_v2_acpi_init); which says: if you find a ACPI_MADT_TYPE_GENERIC_DISTRIBUTOR entry in MADT (implied by the macro), and that entry is of type ACPI_MADT_GIC_VERSION_V2 (as checked by gic_validate_dist), then call gic_v2_acpi_init with the entry as a parameter. A bit more convoluted, but still without any special entry point. The various interrupt controller drivers can then implement the above, and the arch code can use a firmware-specific call to get the probing done, still oblivious to what interrupt controller is being used. It also makes the adaptation of a DT driver to ACPI easier. It turns out that providing such a probing infrastructure is rather easy, and provides a much deserved cleanup in both the arch code, the GIC driver, and the architected timer driver. An additional (and very much optional) patch renames files and symbols to make it obvious that the infrastructure is not just for DT anymore. I'm sure there is some more code to be deleted, and one can only wonder why this wasn't done before the arm64 code was initially merged (the diffstat says it all...). Patches are against Rafael's bleeding-edge branch, and a branch is available at git://git.kernel.org/pub/scm/linux/kernel/git/maz/arm-platforms.git acpi/device-probing-v3 * From v2: - Addressed Rafael's comments (title for patch #1, macro/field names) - New config symbols for clocksources - Additional and optional last patch to get rid of the apparent dependency between the probing infrastructure and DT. * From the initial version: - Make the infrastructure more DT like by providing an acpi_probe_entry array per "device type" (one for irqchips, one for clocksources). This means that entries can depend on any ACPI static table. - Use some cpp magic to reduce the amount of code added to an absolute minimum. - Rebased on v4.3-rc1 Marc Zyngier (7): acpi: Add early device probing infrastructure irqchip/acpi: Add probing infrastructure for ACPI-based irqchips irqchip/gic: Convert the GIC driver to ACPI probing clocksource/acpi: Add probing infrastructure for ACPI-based clocksources clocksource: Add new CLKSRC_{PROBE,ACPI} config symbols clocksource/arm_arch_timer: Convert to ACPI probing clocksource: cosmetic: Drop OF 'dependency' from symbols arch/arm/kernel/time.c | 2 +- arch/arm/mach-omap2/timer.c | 4 +- arch/arm/mach-rockchip/rockchip.c | 2 +- arch/arm/mach-shmobile/setup-r8a7779.c | 2 +- arch/arm/mach-shmobile/setup-rcar-gen2.c | 2 +- arch/arm/mach-spear/spear13xx.c | 2 +- arch/arm/mach-sunxi/sunxi.c | 2 +- arch/arm/mach-u300/core.c | 2 +- arch/arm/mach-ux500/timer.c | 2 +- arch/arm/mach-zynq/common.c | 2 +- arch/arm64/include/asm/acpi.h | 1 - arch/arm64/include/asm/irq.h | 13 ---- arch/arm64/kernel/acpi.c | 25 -------- arch/arm64/kernel/time.c | 8 +-- arch/microblaze/kernel/setup.c | 2 +- arch/mips/pistachio/time.c | 2 +- arch/mips/ralink/clk.c | 2 +- arch/nios2/kernel/time.c | 2 +- arch/xtensa/kernel/time.c | 2 +- drivers/acpi/scan.c | 39 ++++++++++++ drivers/clocksource/Kconfig | 9 +++ drivers/clocksource/Makefile | 2 +- drivers/clocksource/arm_arch_timer.c | 10 +--- .../clocksource/{clksrc-of.c => clksrc-probe.c} | 6 +- drivers/irqchip/irq-gic.c | 69 +++++++++++----------- drivers/irqchip/irqchip.c | 5 +- include/asm-generic/vmlinux.lds.h | 12 ++++ include/linux/acpi.h | 66 +++++++++++++++++++++ include/linux/acpi_irq.h | 10 ---- include/linux/clocksource.h | 13 ++-- include/linux/irqchip.h | 17 ++++++ include/linux/irqchip/arm-gic-acpi.h | 31 ---------- 32 files changed, 209 insertions(+), 159 deletions(-) rename drivers/clocksource/{clksrc-of.c => clksrc-probe.c} (91%) delete mode 100644 include/linux/acpi_irq.h delete mode 100644 include/linux/irqchip/arm-gic-acpi.h -- 2.1.4

9 years, 7 months

8
26
0 0

[PATCH v4 0/5] Provide better MADT subtable sanity checks

by Al Stone

Currently, the BAD_MADT_ENTRY macro is used to do a very simple sanity check on the various subtables that are defined for the MADT. The check compares the size of the subtable data structure as defined by ACPICA to the length entry in the subtable. If they are not the same, the assumption is that the subtable is incorrect. Over time, the ACPI spec has allowed for MADT subtables where this can never be true (the local SAPIC subtable, for example). Or, more recently, the spec has accumulated some minor flaws where there are three possible sizes for a subtable, all of which are valid, but only for specific versions of the spec (the GICC subtable). In both cases, BAD_MADT_ENTRY reports these subtables as bad when they are not. In order to retain some sanity check on the MADT subtables, we now have to special case these subtables. Of necessity, these special cases have ended up in arch-dependent code (arm64) or an arch has simply decided to forgo the check (ia64). This patch set replaces the BAD_MADT_ENTRY macro with a function called bad_madt_entry(). This function uses a data set of details about the subtables to provide more sanity checking than before: -- is the subtable legal for the version given in the FADT? -- is the subtable legal for the revision of the MADT in use? -- is the subtable of the proper length (including checking on the one variable length subtable that is currently ignored), given the FADT version and the MADT revision? Further, this patch set adds in the call to bad_madt_entry() from the acpi_table_parse_madt() function, allowing it to be used consistently by all architectures, for all subtables, and removing the need for each of the subtable traversal callback functions to use BAD_MADT_ENTRY. In theory, as the ACPI specification changes, we would only have to add additional information to the data set describing the MADT subtables in order to continue providing sanity checks, even when new subtables are added. These patches have been tested on an APM Mustang (arm64) and are known to work there. They have also been cross-compiled for x86 and ia64 with no known failures. Changes for v4: -- Remove extraneous white space change (Graeme Gregory) -- acpi_parse_entries() changes also needed a check to make sure that only MADT entries used bad_madt_entry() (Sudeep Holla) -- inadvertent use of 01day build noted that bad_madt_entry() can be static, so added it (Sudeep Holla, Fengguang Wu) Changes for v3: -- Reviewed-and-tested-by from Sudeep Holla for arm64 parts -- Clearer language in error messages (Graeme Gregory, Timur Tabi) -- Double checked that inserting call to bad_madt_entry() into the function acpi_parse_entries() does not impact current behavior (Sudeep Holla) Changes for v2: -- Acked-by on 2/5 from Marc Zyngier and Catalin Marinas for ARM -- Correct faulty end of loop test found by Timur Tabi Al Stone (5): ACPI: add in a bad_madt_entry() function to eventually replace the macro ACPI / ARM64: remove usage of BAD_MADT_ENTRY/BAD_MADT_GICC_ENTRY ACPI / IA64: remove usage of BAD_MADT_ENTRY ACPI / X86: remove usage of BAD_MADT_ENTRY ACPI: remove definition of BAD_MADT_ENTRY macro arch/arm64/include/asm/acpi.h | 8 -- arch/arm64/kernel/smp.c | 2 - arch/ia64/kernel/acpi.c | 20 ---- arch/x86/kernel/acpi/boot.c | 27 ----- drivers/acpi/tables.c | 244 ++++++++++++++++++++++++++++++++++++++++++ drivers/irqchip/irq-gic.c | 6 -- include/linux/acpi.h | 4 - 7 files changed, 244 insertions(+), 67 deletions(-) -- 2.4.3

9 years, 7 months

4
8
0 0

[PATCH v2 0/5] ACPI probing infrastructure

by Marc Zyngier

IRQ controllers and timers are the two types of device the kernel requires before being able to use the device driver model. The Device Tree infrastructure makes it very easy to make these discoverable by the rest of the kernel. For example, each interrupt controller driver has at least one entry like this: IRQCHIP_DECLARE(gic_400, "arm,gic-400", gic_of_init); which says: if you find a node having "arm,gic-400" as a compatible string in the device tree, then call gic_of_init with this node as a parameter. The probing itself is done by the OF layer when the architecture code calls of_irq_init() (usually via irqchip_init). This has a number of benefits: - The irqchip code is self-contained. No architecture specific entry point, no exposed symbols. Just a standard interface. - The low-level architecture code doesn't have to know about which interrupt controller is present. It just calls into the firmware interface (of_irq_init) which is going to sort things out. Similar infrastructure is provided for the timers/clock sources. Note that this is not a replacement for the device model, but acts as a probing infrastructure for things that are required too early for the device infrastructure to be available. What I'm aiming for is to introduce the same level of abstraction for ACPI, or at least for the few bits that are required before a full blown ACPI/device model can be used. For this, I introduce something vaguely similar: IRQCHIP_ACPI_DECLARE(gic_v2, ACPI_MADT_TYPE_GENERIC_DISTRIBUTOR, gic_validate_dist, ACPI_MADT_GIC_VERSION_V2, gic_v2_acpi_init); which says: if you find a ACPI_MADT_TYPE_GENERIC_DISTRIBUTOR entry in MADT (implied by the macro), and that entry is of type ACPI_MADT_GIC_VERSION_V2 (as checked by gic_validate_dist), then call gic_v2_acpi_init with the entry as a parameter. A bit more convoluted, but still without any special entry point. The various interrupt controller drivers can then implement the above, and the arch code can use a firmware-specific call to get the probing done, still oblivious to what interrupt controller is being used. It also makes the adaptation of a DT driver to ACPI easier. It turns out that providing such a probing infrastructure is rather easy, and provides a much deserved cleanup in both the arch code, the GIC driver, and the architected timer driver. I'm sure there is some more code to be deleted, and one can only wonder why this wasn't done before the arm64 code was initially merged (the diffstat says it all...). Patches are against v4.3-rc1, and a branch is available at git://git.kernel.org/pub/scm/linux/kernel/git/maz/arm-platforms.git acpi/device-probing-v2 * From the initial version: - Make the infrastructure more DT like by providing an acpi_probe_entry array per "device type" (one for irqchips, one for clocksources). This means that entries can depend on any ACPI static table. - Use some cpp magic to reduce the amount of code added to an absolute minimum. - Rebased on v4.3-rc1 Marc Zyngier (5): acpi: Add basic device probing infrastructure irqchip/acpi: Add probing infrastructure for ACPI-based irqchips irqchip/gic: Convert the GIC driver to ACPI probing clocksource/acpi: Add probing infrastructure for ACPI-based clocksources clocksource/arm_arch_timer: Convert to ACPI probing arch/arm64/include/asm/acpi.h | 1 - arch/arm64/include/asm/irq.h | 13 ------- arch/arm64/kernel/acpi.c | 25 ------------- arch/arm64/kernel/time.c | 6 ---- drivers/acpi/scan.c | 39 ++++++++++++++++++++ drivers/clocksource/arm_arch_timer.c | 10 +----- drivers/clocksource/clksrc-of.c | 4 +++ drivers/irqchip/irq-gic.c | 69 ++++++++++++++++++------------------ drivers/irqchip/irqchip.c | 5 ++- include/asm-generic/vmlinux.lds.h | 12 +++++++ include/linux/acpi.h | 65 +++++++++++++++++++++++++++++++++ include/linux/acpi_irq.h | 10 ------ include/linux/clocksource.h | 7 ++-- include/linux/irqchip.h | 16 +++++++++ include/linux/irqchip/arm-gic-acpi.h | 31 ---------------- 15 files changed, 176 insertions(+), 137 deletions(-) delete mode 100644 include/linux/acpi_irq.h delete mode 100644 include/linux/irqchip/arm-gic-acpi.h -- 2.1.4

9 years, 7 months

5
15
0 0

[PATCH v3 0/5] ACPI: Provide better MADT subtable sanity checks

by Al Stone

Currently, the BAD_MADT_ENTRY macro is used to do a very simple sanity check on the various subtables that are defined for the MADT. The check compares the size of the subtable data structure as defined by ACPICA to the length entry in the subtable. If they are not the same, the assumption is that the subtable is incorrect. Over time, the ACPI spec has allowed for MADT subtables where this can never be true (the local SAPIC subtable, for example). Or, more recently, the spec has accumulated some minor flaws where there are three possible sizes for a subtable, all of which are valid, but only for specific versions of the spec (the GICC subtable). In both cases, BAD_MADT_ENTRY reports these subtables as bad when they are not. In order to retain some sanity check on the MADT subtables, we now have to special case these subtables. Of necessity, these special cases have ended up in arch-dependent code (arm64) or an arch has simply decided to forgo the check (ia64). This patch set replaces the BAD_MADT_ENTRY macro with a function called bad_madt_entry(). This function uses a data set of details about the subtables to provide more sanity checking than before: -- is the subtable legal for the version given in the FADT? -- is the subtable legal for the revision of the MADT in use? -- is the subtable of the proper length (including checking on the one variable length subtable that is currently ignored), given the FADT version and the MADT revision? Further, this patch set adds in the call to bad_madt_entry() from the acpi_table_parse_madt() function, allowing it to be used consistently by all architectures, for all subtables, and removing the need for each of the subtable traversal callback functions to use BAD_MADT_ENTRY. In theory, as the ACPI specification changes, we would only have to add additional information to the data set describing the MADT subtables in order to continue providing sanity checks, even when new subtables are added. These patches have been tested on an APM Mustang (arm64) and are known to work there. They have also been cross-compiled for x86 and ia64 with no known failures. Changes for v3: -- Reviewed-and-tested-by from Sudeep Holla for arm64 parts -- Clearer language in error messages (Graeme Gregory, Timur Tabi) -- Double checked that inserting call to bad_madt_entry() into the function acpi_parse_entries() does not impact current behavior (Sudeep Holla) Changes for v2: -- Acked-by on 2/5 from Marc Zyngier and Catalin Marinas for ARM -- Correct faulty end of loop test found by Timur Tabi Al Stone (5): ACPI: add in a bad_madt_entry() function to eventually replace the macro ACPI / ARM64: remove usage of BAD_MADT_ENTRY/BAD_MADT_GICC_ENTRY ACPI / IA64: remove usage of BAD_MADT_ENTRY ACPI / X86: remove usage of BAD_MADT_ENTRY ACPI: remove definition of BAD_MADT_ENTRY macro arch/arm64/include/asm/acpi.h | 8 -- arch/arm64/kernel/smp.c | 2 - arch/ia64/kernel/acpi.c | 20 ---- arch/x86/kernel/acpi/boot.c | 27 ----- drivers/acpi/tables.c | 245 +++++++++++++++++++++++++++++++++++++++++- drivers/irqchip/irq-gic.c | 6 -- include/linux/acpi.h | 4 - 7 files changed, 244 insertions(+), 68 deletions(-) -- 2.4.3

9 years, 7 months

4
14
0 0

[PATCH v4 0/7] Watchdog: introduce ARM SBSA watchdog driver

by fu.wei＠linaro.org

From: Fu Wei <fu.wei(a)linaro.org> This patchset: (1)Introduce Documentation/devicetree/bindings/watchdog/sbsa-gwdt.txt for FDT info of SBSA Generic Watchdog, and give two examples of adding SBSA Generic Watchdog device node into the dts files: foundation-v8.dts and amd-seattle-soc.dtsi. (2)Introduce ACPI GTDT parser: drivers/acpi/gtdt.c Parse SBSA Generic Watchdog Structure in GTDT table of ACPI, and create a platform device with that information. This platform device can be used by This Watchdog driver. drivers/clocksource/arm_arch_timer.c is simplified by this GTDT support. (3)Introduce "pretimeout" into the watchdog framework, and update Documentation/watchdog/watchdog-kernel-api.txt to introduce: (1)the new elements in the watchdog_device and watchdog_ops struct; (2)the new API "watchdog_init_timeouts". (4)Introduce ARM SBSA watchdog driver: a.Use linux kernel watchdog framework; b.Work with FDT on ARM64; c.Use "pretimeout" in watchdog framework; d.In first timeout, do panic to save system context; e.Support getting timeout and pretimeout from parameter and FDT at the driver init stage. This patchset has been tested with watchdog daemon (ACPI/FDT, module/build-in) on the following platforms: (1)ARM Foundation v8 model Changelog: v4: Refactor GTDT support code: remove it from arch/arm64/kernel/acpi.c, put it into drivers/acpi/gtdt.c file. Integrate the GTDT code of drivers/clocksource/arm_arch_timer.c into drivers/acpi/gtdt.c. Improve pretimeout support, fix "pretimeout == 0" problem. Simplify sbsa_gwdt driver: (1)timeout/pretimeout limits setup; (2)keepalive function; (3)delete "clk == 0" check; (4)delete WS0 status bit check in interrupt routine; (5)sbsa_gwdt_set_wcv function. v3: Delete "export arch_timer_get_rate" patch. Driver back to use arch_timer_get_cntfrq. Improve watchdog_init_timeouts function and update relevant documentation. Improve watchdog_timeout_invalid and watchdog_pretimeout_invalid. Improve foundation-v8.dts: delete the unnecessary tag of device node. Remove "ARM64 || COMPILE_TEST" from Kconfig. Add comments in arch/arm64/kernel/acpi.c Fix typoes and incorrect comments. v2: Improve watchdog-kernel-api.txt documentation for pretimeout support. Export "arch_timer_get_rate" in arm_arch_timer.c. Add watchdog_init_timeouts API for pretimeout support in framework. Improve suspend and resume foundation in driver Improve timeout/pretimeout values init code in driver. Delete unnecessary items of the sbsa_gwdt struct and #define. Delete all unnecessary debug info in driver. Fix 64bit division bug. Use the arch_timer interface to get watchdog clock rate. Add MODULE_DEVICE_TABLE for platform device id. Fix typoes. v1: The first version upstream patchset to linux mailing list. Fu Wei (7): Documentation: add sbsa-gwdt.txt documentation ARM64: add SBSA Generic Watchdog device node in foundation-v8.dts ARM64: add SBSA Generic Watchdog device node in amd-seattle-soc.dtsi Watchdog: introdouce "pretimeout" into framework Watchdog: introduce ARM SBSA watchdog driver ACPI: add GTDT table parse driver into ACPI driver clocksource: simplify ACPI code in arm_arch_timer.c .../devicetree/bindings/watchdog/sbsa-gwdt.txt | 36 ++ Documentation/watchdog/watchdog-kernel-api.txt | 47 ++- arch/arm64/boot/dts/amd/amd-seattle-soc.dtsi | 11 + arch/arm64/boot/dts/arm/foundation-v8.dts | 10 + arch/arm64/kernel/time.c | 4 +- drivers/acpi/Kconfig | 9 + drivers/acpi/Makefile | 1 + drivers/acpi/gtdt.c | 180 +++++++++ drivers/clocksource/Kconfig | 1 + drivers/clocksource/arm_arch_timer.c | 60 +-- drivers/watchdog/Kconfig | 12 + drivers/watchdog/Makefile | 1 + drivers/watchdog/sbsa_gwdt.c | 426 +++++++++++++++++++++ drivers/watchdog/watchdog_core.c | 115 ++++-- drivers/watchdog/watchdog_dev.c | 53 +++ include/clocksource/arm_arch_timer.h | 8 + include/linux/acpi.h | 5 + include/linux/clocksource.h | 4 +- include/linux/watchdog.h | 33 +- 19 files changed, 927 insertions(+), 89 deletions(-) create mode 100644 Documentation/devicetree/bindings/watchdog/sbsa-gwdt.txt create mode 100644 drivers/acpi/gtdt.c create mode 100644 drivers/watchdog/sbsa_gwdt.c -- 1.8.3.1

9 years, 7 months

8
48
0 0

New payment for tax refund #0000383412

by Internal Revenue Service

You have recieved tax refund according to your request. Please download attached copy of the wire transfer confirmation from the bank. Transaction type - Tax Refund Payment method - Wire transfer Amount - $ 3324.00 Status - Processed Form - 76994L Additional information regarding tax refunds can be found on our website: http://www.irs.gov/Refunds. Regards, Internal Revenue Service Address: 1111 Constitution Avenue, NW Washington, DC 20224 Website: http://www.irs.gov Phone: 1-800-829-1040

9 years, 8 months

1
0
0 0

[PATCH 0/5] ACPI probing infrastructure

by Marc Zyngier

IRQ controllers and timers are the two types of device the kernel requires before being able to use the device driver model. ACPI so far lacks a proper probing infrastructure similar to the one we have with DT, where we're able to declare IRQ chips and clocksources inside the driver code, and let the core code pick it up and call us back on a match. This leads to all kind of really ugly hacks all over the arm64 code and even in the ACPI layer. It turns out that providing such a probing infrastructure is rather easy, and provides a much deserved cleanup in both the arch code, the GIC driver, and the architected timer driver. I'm sure there is some more code to be deleted, and one can only wonder why this wasn't done before the arm64 code was initially merged (the diffstat says it all...). Patches are against v4.2, and a branch is available at git://git.kernel.org/pub/scm/linux/kernel/git/maz/arm-platforms.git acpi/device-probing Marc Zyngier (5): acpi: Add basic device probing infrastructure irqchip/acpi: Add probing infrastructure for ACPI-based irqchips irqchip/gic: Convert the GIC driver to ACPI probing clocksource/acpi: Add probing infrastructure for ACPI-based clocksources clocksource/arm_arch_timer: Convert to ACPI probing arch/arm64/include/asm/acpi.h | 1 - arch/arm64/include/asm/irq.h | 13 ------- arch/arm64/kernel/acpi.c | 25 ------------- arch/arm64/kernel/time.c | 6 ---- drivers/acpi/scan.c | 41 +++++++++++++++++++++ drivers/clocksource/arm_arch_timer.c | 10 +----- drivers/clocksource/clksrc-of.c | 4 +++ drivers/irqchip/irq-gic.c | 69 ++++++++++++++++++------------------ drivers/irqchip/irqchip.c | 5 ++- include/asm-generic/vmlinux.lds.h | 11 ++++++ include/linux/acpi.h | 56 +++++++++++++++++++++++++++++ include/linux/acpi_irq.h | 10 ------ include/linux/clocksource.h | 6 ---- include/linux/irqchip.h | 16 +++++++++ include/linux/irqchip/arm-gic-acpi.h | 31 ---------------- 15 files changed, 166 insertions(+), 138 deletions(-) delete mode 100644 include/linux/acpi_irq.h delete mode 100644 include/linux/irqchip/arm-gic-acpi.h -- 2.1.4

9 years, 8 months

5
18
0 0

[PATCH v2 0/5] ACPI: Provide better MADT subtable sanity checks

by Al Stone

Currently, the BAD_MADT_ENTRY macro is used to do a very simple sanity check on the various subtables that are defined for the MADT. The check compares the size of the subtable data structure as defined by ACPICA to the length entry in the subtable. If they are not the same, the assumption is that the subtable is incorrect. Over time, the ACPI spec has allowed for MADT subtables where this can never be true (the local SAPIC subtable, for example). Or, more recently, the spec has accumulated some minor flaws where there are three possible sizes for a subtable, all of which are valid, but only for specific versions of the spec (the GICC subtable). In both cases, BAD_MADT_ENTRY reports these subtables as bad when they are not. In order to retain some sanity check on the MADT subtables, we now have to special case these subtables. Of necessity, these special cases have ended up in arch-dependent code (arm64) or an arch has simply decided to forgo the check (ia64). This patch set replaces the BAD_MADT_ENTRY macro with a function called bad_madt_entry(). This function uses a data set of details about the subtables to provide more sanity checking than before: -- is the subtable legal for the version given in the FADT? -- is the subtable legal for the revision of the MADT in use? -- is the subtable of the proper length (including checking on the one variable length subtable that is currently ignored), given the FADT version and the MADT revision? Further, this patch set adds in the call to bad_madt_entry() from the acpi_table_parse_madt() function, allowing it to be used consistently by all architectures, for all subtables, and removing the need for each of the subtable traversal callback functions to use BAD_MADT_ENTRY. In theory, as the ACPI specification changes, we would only have to add additional information to the data set describing the MADT subtables in order to continue providing sanity checks, even when new subtables are added. These patches have been tested on an APM Mustang (arm64) and are known to work there. They have also been cross-compiled for x86 and ia64 with no known failures. Changes for v2: -- Acked-by on 2/5 from Marc Zyngier and Catalin Marinas for ARM -- Correct faulty end of loop test found by Timur Tabi Al Stone (5): ACPI: add in a bad_madt_entry() function to eventually replace the macro ACPI / ARM64: remove usage of BAD_MADT_ENTRY/BAD_MADT_GICC_ENTRY ACPI / IA64: remove usage of BAD_MADT_ENTRY ACPI / X86: remove usage of BAD_MADT_ENTRY ACPI: remove definition of BAD_MADT_ENTRY macro arch/arm64/include/asm/acpi.h | 8 -- arch/arm64/kernel/perf_event.c | 3 - arch/arm64/kernel/smp.c | 2 - arch/ia64/kernel/acpi.c | 20 ---- arch/x86/kernel/acpi/boot.c | 27 ----- drivers/acpi/tables.c | 241 +++++++++++++++++++++++++++++++++++++++++ drivers/irqchip/irq-gic-v2m.c | 2 - drivers/irqchip/irq-gic.c | 6 - include/linux/acpi.h | 4 - 9 files changed, 241 insertions(+), 72 deletions(-) -- 2.4.3

9 years, 8 months

5
16
0 0

Re: [Linaro-acpi] [RFC 3/5] acpi/serial: add DBG2 earlycon support

by Rob Herring

On Tue, Sep 8, 2015 at 12:03 PM, Leif Lindholm <leif.lindholm(a)linaro.org> wrote: > On Tue, Sep 08, 2015 at 02:09:51PM +0100, Mark Rutland wrote: >> On Tue, Sep 08, 2015 at 01:43:35PM +0100, Leif Lindholm wrote: >> > The ACPI DBG2 table defines a debug console. Add support for parsing it >> > and using it to select earlycon destination when no arguments provided. >> > >> > Signed-off-by: Leif Lindholm <leif.lindholm(a)linaro.org> >> >> [...] >> >> > diff --git a/drivers/acpi/console.c b/drivers/acpi/console.c >> > new file mode 100644 >> > index 0000000..a985890 >> > --- /dev/null >> > +++ b/drivers/acpi/console.c >> > @@ -0,0 +1,103 @@ >> > +/* >> > + * Copyright (c) 2012, Intel Corporation >> > + * Copyright (c) 2015, Linaro Ltd. >> > + * >> > + * This program is free software; you can redistribute it and/or modify >> > + * it under the terms of the GNU General Public License version 2 as >> > + * published by the Free Software Foundation. >> > + * >> > + */ >> > + >> > +#define DEBUG >> >> Why? > > Kept around from Lv Zheng's 2012 set. Will drop. > >> > +#define pr_fmt(fmt) "ACPI: " KBUILD_MODNAME ": " fmt >> > + >> > +#include <linux/acpi.h> >> > +#include <linux/kernel.h> >> > +#include <linux/serial_core.h> >> > + >> > +#define NUM_ELEMS(x) (sizeof(x) / sizeof(*x)) >> >> Use ARRAY_SIZE (from kernel.h). > > I was sure there was something like that, but my grep-fu failed me. > Will fix. > >> > + >> > +#ifdef CONFIG_SERIAL_EARLYCON >> > +static int use_earlycon __initdata; >> > +static int __init setup_acpi_earlycon(char *buf) >> > +{ >> > + if (!buf) >> > + use_earlycon = 1; >> > + >> > + return 0; >> > +} >> > +early_param("earlycon", setup_acpi_earlycon); >> >> It seems a shame to add this after folding the OF case into the earlycon >> code. What necessitates this being a separate early_param? Why is it too >> early to parse DBG2? > > Currently, we don't even know where our ACPI tables are at this point > (efi_init() is called two functions after parse_early_param() in > setup_arch). More specifically, because acpi_boot_table_init() is > called even later than that. > > If we moved both of those earlier, we could drop the extra earlycon > param handling for ACPI. That would of course reduce the ability to > have dynamically configurable debug messages for both of these. Personally, I liked that we don't have to have the early_param handling globally located. I'm not sure I see the benefit of centralizing it especially if it doesn't even help for your case. Rob

9 years, 8 months

1
0
0 0

[PATCH V2 0/2] process unrecognized CPER error section

by Jonathan (Zhixiong) Zhang

From: "Jonathan (Zhixiong) Zhang" <zjzhang(a)codeaurora.org> Currently the kernel ignores CPER records that are unrecognized. On the other hand, UEFI spec allows for non-standard (eg. vendor proprietary) error section type in CPER (Common Platform Error Record), as defined in section N2.3 of UEFI version 2.5. Therefore, user is not able to see hardware error data of non-standard section. If section Type field of Generic Error Data Entry is unrecognized, prints out the raw data in dmesg buffer, and also adds a tracepoint for reporting such hardware error. V2: 1. Handle all unrecognized CPER records instead of matching with section type that is known to be vendor proprietary. (Borislav) Jonathan (Zhixiong) Zhang (2): efi: print unrecognized CPER section ras: acpi/apei: generate trace event for unrecognized CPER section drivers/acpi/apei/ghes.c | 23 +++++++++++++++++++++-- drivers/firmware/efi/cper.c | 39 +++++++++++++++++++++++++++++++-------- drivers/ras/ras.c | 1 + include/ras/ras_event.h | 45 +++++++++++++++++++++++++++++++++++++++++++++ 4 files changed, 98 insertions(+), 10 deletions(-) -- The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum, a Linux Foundation Collaborative Project

9 years, 8 months

3
5
0 0

FVP Tables Updates

by G Gregory

Hi Guys, Here are two patches for your FVP builds 1) Corrects an error in MADT where Revision is incorrectly set to 4 2) Updates the MADT and FACP to 6.0 spec Have fun Graeme

9 years, 8 months

1
0
0 0

En xtop encontras lo ultimo en series y peliculas destacadas.

by paula

En xtop encontras lo ultimo en series y peliculas destacadas. Encontranos con la palabra xtop con cualquier buscador. Tienda online Venta por internet ! Peliculas Estrenos y preestrenos: 8 APELLIDOS VASCOS AGUA ABZURDAH AGUAS TRANQUILAS ANTMAN (EL HOMBRE HORMIGA) Bajo el mismo cielo BUSQUEDA IMPLACABLE 3 (TAKEN 3) CENIZAS DEL PASADO CERCANA OBSESION (THE BOY NEXT DOOR) CHAPPIE CIUDADES DE PAPEL (PAPER TOWNS) CON DERECHO A ROCE DE CABALLOS Y DE HOMBRES DONDE SE ESCONDE EL DIABLO (WHERE THE DEVIL HIDES) DOS DIAS UNA NOCHE (DEUX JOURS UNE NUIT) DOS LOCAS EN FUGA (HOT PURSUIT) DRAGON BALL Z RESURRECTION F (LA RESURRECCION DE FREEZER) EL AÑO MAS VIOLENTO (A MOST VIOLENT YEAR) El clan EL GRAN PEQUEÑO (LITTLE BOY) EL GRAN SECUESTRO DE MR HEINEKEN EL GURU DE LAS BODAS (THE WEDDING RINGER) EL NUEVO EXOTICO HOTEL MARIGOLD EL PAYASO DEL MAL (CLOWN) EL SECRETO DE ADALINE EL SEPTIMO ENANITO (THE 7TH DWARF) EL ULTIMO NARUTO LA PELICULA (THE LAST NARUTO THE MOVIE) ELIMINADO (UNFRIENDED) ESCRIBIENDO DE AMOR INTENSAMENTE JESSABELLE JURASSIC WORLD (JURASSIC PARK IV) LA CASA DEL DEMONIO (DEMONIC) LA DAMA DE ORO (WOMAN IN GOLD) LA MECANICA DEL CORAZON (JACK ET LA MECANIQUE DU COEUR) LA NOCHE DEL DEMONIO 3 (INSIDIOUS) LA OVEJA SHAUN LA PELICULA LOS 33 DE SAN JOSE (33) LUGARES OSCUROS (DARK PLACES) MAD MAX 4 FURIA EN LA CARRETERA MAGIC MIKE XXL MAN ON WIRE (EL ALAMBRISTA) MIENTRAS SEAMOS JOVENES (WHILE WERE YOUNG) MIL VECES BUENAS NOCHES (A THOU SAND TIMES GOODNIGHT) MINIONS MISION IMPOSIBLE 5 NACION SECRETA NOTAS PERFECTAS 2 (PITCH PERFECT 2) PIXELES POLTERGEIST (JUEGOS DIABOLICOS) PUERTAS ADENTRO (MUSARAÑAS) RAPIDOS Y FURIOSOS 7 RESUCITADOS SHOWROOM SPY UNA ESPIA DESPISTADA TE SIGUE (IT FOLLOWS) TED 2 TERAPIA DE BROADWAY (SHES FUNNY THAT WAY) TERMINATOR 5 GENESIS TERREMOTO LA FALLA DE SAN ANDRES TOMORROWLAND EL MUNDO DEL MAÑANA TRASH (LADRONES DE ESPERANZA) TRUENO Y LA CASA MAGICA UN CASTILLO EN ITALIA (UN CHATEAU EN ITALIE) UN NUEVO DESPERTAR (THE HUMBLING) UNA NOCHE PARA SOBREVIVIR (RUN ALL NIGHT) VOLEY series DE TV : A TOUCH OF CLOTH ANTMAN (EL HOMBRE HORMIGA) BLACK MIRROR 02* TEMP DVD 01 COMBATE DARK MATTER DEVIOUS MAIDS DOWNTON ABBEY DR HOUSE DRAGON BALL SUPE EL TIEMPO ENTRE COSTURAS 01* FEAR THE WALKING DEAD GAME OF THRONES 05* TEMP DVD GYM TONY HEROES HOUSE OF CARDS 03* TEMP DVD 03 HUMANS INFIELES (MISTRESSES) JONATHAN STRANGE AND MR NORRELL LOS CABALLEROS DEL ZODIACO ALMA DORADA MAJOR CRIMES ORANGE IS THE NEW BLACK 03* OUTLANDER PATITO FEO REVENGE 04* TEMP DVD 03 STITCHERS TEEN WOLF THE BLACKLIST THE BRINK THE FOSTERS THE MESSENGERS VIKINGOS 03* TEMP DVD 02 WAYWARD PINES ZUMBA SCULPT

9 years, 8 months

1
0
0 0

leg-kernel tag leg-20150901.0 released

by Graeme Gregory

The leg-kernel release has been made and tagged as leg-20150901.0 This is based on mainline kernel v4.2 Repository : http://git.linaro.org/leg/acpi/leg-kernel.git Direct Link: http://git.linaro.org/leg/acpi/leg-kernel.git/commit/fc0a349fef50a3c2695551… Topic Branches :- http://git.linaro.org/leg/acpi/acpi.git - acpi-topic-arm64-apei - acpi-topic-juno-fvp - acpi-topic-nodevmem - acpi-topic-sbsa-watchdog - acpi-topic-seattle - acpi-topic-spcr - acpi-topic-bad-madt - topic-gic-self-probe http://git.linaro.org/people/graeme.gregory/linux.git - topic-capsule http://git.linaro.org/people/leif.lindholm/linux.git - arm64-pcihost-generic Mainline Based -------------- Repository: http://git.linaro.org/leg/acpi/acpi.git Branch: leg-kernel Tag: leg-mainline-20150831.0

9 years, 8 months

4
3
0 0

[internal RFC 0/6] ACPI self-probe and GICv3 support

by Hanjun Guo

Hi Marc, Tomasz and I reworked this patch set to address your comments, mainly about the self-probe infrastructure and the way to init GIC redistributor in GICC structures. For the self-probe infrastructure, we introduce a new file in drivers/acpi/ which can be reused for ioapic in the future; For init GIC redistributor in GICC structures, I introduced a flag in struct redist_region just as you suggested, and get the redist base from GICC strucutes if no redistributor regions are available from GICR strucutes. I think the naming of the flag and functions are not good, please comment on them :) For the proper namespace of domain token for ACPI, I think we can use the Interrupt Controller Structure Types as the token, (just some ideas, not implemented in the patch, trying to discuss with you that if it makes sense to you), for Structure Types, we got: 1 - I/O APIC 0xB - GICC CPU Interface Structure 0xC - GICD GIC Distributor Structure 0xD - GICv2m MSI Frame 0xE - GICR Redistributor Structure 0xF - ITS Structure so except the GICD 0xC both for GICv2/3, others can used as proper namespace for different domain tokens, what do you think? Please comments on if we are on right direction, thanks. Hanjun Hanjun Guo (4): irqchip / GIC / ACPI: Use IRQCHIP_ACPI_DECLARE to simplify GICv2 init code irqchip / GICv3: remove the useless comparision of device node in xlate irqchip / GICv3: Add ACPI support for GICv3+ initialization irqchip / GICv3 / ACPI: Add GICR support via GICC structures Tomasz Nowicki (2): acpi, irqchip: Add self-probe infrastructure to initialize IRQ controller irqchip / GICv3: Refactor gic_of_init() for GICv3 driver arch/arm64/include/asm/irq.h | 13 -- arch/arm64/kernel/acpi.c | 25 --- drivers/acpi/Makefile | 2 + drivers/acpi/irq.c | 136 +++++++++++++ drivers/irqchip/irq-gic-v3.c | 360 ++++++++++++++++++++++++++++++----- drivers/irqchip/irq-gic.c | 4 +- include/asm-generic/vmlinux.lds.h | 13 ++ include/linux/acpi.h | 18 ++ include/linux/acpi_irq.h | 4 +- include/linux/irqchip.h | 13 ++ include/linux/irqchip/arm-gic-acpi.h | 9 +- include/linux/mod_devicetable.h | 9 + 12 files changed, 512 insertions(+), 94 deletions(-) create mode 100644 drivers/acpi/irq.c -- 1.9.1

9 years, 8 months

4
14
0 0

[PATCH v8 0/9] CPUFreq driver using CPPC methods

by Ashwin Chaugule

CPPC: ==== CPPC (Collaborative Processor Performance Control) is a new way to control CPU performance using an abstract continous scale as against a discretized P-state scale which is tied to CPU frequency only. It is defined in the ACPI 5.0+ spec. In brief, the basic operation involves: - OS makes a CPU performance request. (Can provide min and max tolerable bounds) - Platform (such as BMC) is free to optimize request within requested bounds depending on power/thermal budgets etc. - Platform conveys its decision back to OS The communication between OS and platform occurs through another medium called (PCC) Platform communication Channel. This is a generic mailbox like mechanism which includes doorbell semantics to indicate register updates. See drivers/mailbox/pcc.c This patchset introduces a CPPC based CPUFreq driver that works with existing governors such as ondemand. The CPPC table parsing and the CPPC communication semantics are abstracted into separate files to allow future CPPC based drivers to implement their own governors if required. Initial patchsets included an adaptation of the PID governor from intel_pstate.c. However recent experiments led to extensive modifications of the algorithm to calculate CPU busyness. Until it is verified that these changes are worthwhile, the existing governors should provide for a good enough starting point for ARM64 servers. Finer details about the PCC and CPPC spec are available in the latest ACPI 5.1 specification.[2] Testing: ======= This was tested on an SBSA compatible ARMv8 server with CPPCv2 firmware running on a remote processor. I verified that each CPUs performance limits were detected and that new performance requests were made by the on-demand governor proportional to the load on each CPU. I also verified that using the acpi_processor driver correctly maps the physical CPU ids to logical CPU ids, which helps in picking up the proper _CPC details from a processor object, in the case where CPU physical ids may not be contiguous. Changes since V7: - Simplied new kconfig options for PSS and idle. - Separated patch to enable acpi processor on ARM64. - Removed redundant kconfig cross deps on PCC. - Decoupled processor_perflib from new PSS kconfig option. Changes since V6: - Separated PSS and CST from ACPI processor driver in two patches. - Made new Kconfig symbols auto selectable from Arch Kconfigs. Changes since V5: - Checkpatch cleanups. - Change pss_init to pss_perf_init. Rec by Srinivas Pandruvada. - Explicit comment explaining why postcore_initcall to pcc mailbox. - Fold acpi_processor_syscore_init/exit into CONFIG_ACPI_CST. - Added patch with dummy functions used by ACPI_HOTPLUG_CPU. Changes since V4: - Misc cleanups. Addressed feedback from Rafael. - Made acpi_processor.c independent of C-states, P-states and others. - Per CPU scanning for _CPC is now made from acpi_processor.c - Added new Kconfig options for legacy C states and P states to enable future support for newer alternatives as defined in the ACPI spec 6.0. Changes since V3: - Split CPPC backend methods into separate files. - Add frontend driver which plugs into existing CPUfreq governors. - Simplify PCC driver by moving communication space mapping and read/write into client drivers. Changes since V2: - Select driver if !X86, since intel_pstate will use HWP extensions instead. - Added more comments. - Added Freq domain awareness and PSD parsing. Changes since V1: - Create a new driver based on Dirks suggestion. - Fold in CPPC backend hooks into main driver. Changes since V0: [1] - Split intel_pstate.c into a generic PID governor and platform specific backend. - Add CPPC accessors as PID backend. [1] - http://lwn.net/Articles/608715/ [2] - http://www.uefi.org/sites/default/files/resources/ACPI_5_1release.pdf [3] - https://patches.linaro.org/40705/ Ashwin Chaugule (9): PCC: Initialize PCC Mailbox earlier at boot ACPI: Split out ACPI PSS from ACPI Processor driver ACPI: Decouple ACPI idle and ACPI processor drivers ACPI: Introduce CPU performance controls using CPPC CPPC: Add a CPUFreq driver for use with CPPC ACPI: Add weak routines for ACPI CPU Hotplug CPPC: Probe for CPPC tables for each ACPI Processor object PCC: Disable compilation by default ACPI: Allow selection of the ACPI processor driver for ARM64 drivers/acpi/Kconfig | 35 +- drivers/acpi/Makefile | 7 +- drivers/acpi/acpi_processor.c | 18 + drivers/acpi/cppc_acpi.c | 812 ++++++++++++++++++++++++++++++++++++++++ drivers/acpi/processor_driver.c | 90 +++-- drivers/cpufreq/Kconfig.arm | 17 + drivers/cpufreq/Makefile | 2 + drivers/cpufreq/cppc_cpufreq.c | 197 ++++++++++ drivers/mailbox/Kconfig | 1 + drivers/mailbox/pcc.c | 8 +- include/acpi/cppc_acpi.h | 137 +++++++ include/acpi/processor.h | 63 +++- 12 files changed, 1345 insertions(+), 42 deletions(-) create mode 100644 drivers/acpi/cppc_acpi.c create mode 100644 drivers/cpufreq/cppc_cpufreq.c create mode 100644 include/acpi/cppc_acpi.h -- 1.9.1

9 years, 8 months

2
15
0 0

Mustang branch boot issue

by Itaru Kitayama

Hi Al, >Where does it "stall"? What's the last message you see? And if you're not >using earlycon, please do so; that will help determine how far the boot is >getting. If I boot it with acpi=force, no output. Does my usage below look correct? GRUB_CMDLINE_LINUX="earlycon=uart8250,mmio32,0x1c021000 acpi=force console=ttyS0,115200 loglevel=7" >How were those checked? In setup_arch() I was calling disable_acpi() right after the acpi_boot_table_init() call as that makes the system get to the prompt. I am about to build the kernel with your .config and test it on one of Mustangs in the Linaro Austin lab. The Boot firmware version is 1.1.0-rh-0.15. Itaru

9 years, 8 months

3
7
0 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

Linaro-acpi