Lines Matching +full:not +full:- +full:used
8 If a section number is used, it refers to a section number in the ACPI
9 specification where the object is defined. If "Signature Reserved" is used,
16 - Required: DSDT, FADT, GTDT, MADT, MCFG, RSDP, SPCR, XSDT
18 - Recommended: BERT, EINJ, ERST, HEST, PCCT, SSDT
20 - Optional: AGDI, BGRT, CEDT, CPEP, CSRT, DBG2, DRTM, ECDT, FACS, FPDT,
24 - Not supported: AEST, APMT, BOOT, DBGP, DMAR, ETDT, HPET, IVRS, LPIT,
41 This table describes a non-maskable event, that is used by the platform
62 Microsoft only table, will not be supported.
68 Optional, not currently supported, with no real use-case for an
82 Optional, not currently supported, and not recommended until such
83 time as ARM-compatible hardware is available, and the specification
90 Optional, not currently supported.
96 License has changed and should be usable. Optional if used instead
103 Microsoft only table, will not be supported.
119 x86 only table, will not be supported.
125 Optional, not currently supported.
131 Optional, not currently supported, but could be used on ARM if and
142 if it had actually occurred. However, this table should not be
150 On a platform supports RAS, this table must be supplied if it is not
151 UEFI-based; if it is UEFI-based, this table may be supplied. When this
152 table is not present, UEFI run time service will be utilized to save
159 Obsolete table, will not be supported.
166 provided, the Global Lock will NOT be used since it is not part of
167 the hardware reduced profile, and only 64-bit address fields will
181 used, not FIRMWARE_CTRL.
183 If PSCI is used (as is recommended), make sure that ARM_BOOT_ARCH is
184 filled in properly - that the PSCI_COMPLIANT flag is set and that
185 PSCI_USE_HVC is set or unset as needed (see table 5-37).
187 For the DSDT that is also required, the X_DSDT field is to be used,
188 not the DSDT field.
206 ARM-specific error sources have been defined; please use those or the
210 used on arm64.
228 x86 only table, will not be supported.
244 when using GICv3-ITS and an SMMU); on SBSA Level 0 platforms, it
251 x86_64 (AMD) only table, will not be supported.
267 should be used (types 0xA - 0xF).
271 **Memory-mapped ConFiGuration space**
279 Optional, not currently supported.
292 Optional, not currently supported.
298 Optional, not currently supported.
304 Microsoft only table, will not be supported.
310 Optional, not currently supported.
317 use. Since these are not meant to be of general use but are limited
318 to very specific end users, they are not recommended for use and are
319 not supported by the kernel for arm64.
332 This table describes PCC channels used to gather debug logs of
333 non-architectural features.
340 Optional, not currently supported.
352 Obsolete table, will not be supported.
365 Optional, not currently supported.
377 Since this table can only provide 32-bit addresses, it is deprecated
378 on arm64, and will not be used. If provided, it will be ignored.
384 Optional, not currently supported.
396 Microsoft only table, will not be supported.
414 Optional, not currently supported.
420 Optional, but if used, only the GICC Affinity structures are read.
449 Optional, not currently supported, and may need changes to fully
456 Optional, not currently supported, and may need changes to fully
463 Optional, not currently supported. No known use case for arm64,
470 Microsoft only table, will not be supported.
476 Microsoft only table, will not be supported.
482 Microsoft only table, will not be supported.
488 Microsoft only table, will not be supported.
494 Optional, used only by Xen at present.
504 ------------
505 The expectations on individual ACPI objects that are likely to be used are
506 shown in the list that follows; any object not explicitly mentioned below
507 should be used as needed for a particular platform or particular subsystem,
514 on arm64 - there are no assumptions made about
515 whether such devices are cache coherent or not.
517 these devices so it does not need to be repeated.
518 Without _CCA on arm64, the kernel does not know what
522 attributes; the presence of an SMMU can be used to
524 default to non-coherent, but be made coherent with
537 _CSD 8.4.2.2 Use as needed, used only in conjunction with _CST.
540 of C-states.
542 _DDN 6.1.4 This field can be used for a device name. However,
546 _DSD 6.2.5 To be used with caution. If this object is used, try
553 device properties are used. A driver will not be
560 _DSM 9.1.1 Do not use this method. It is not standardized, the
561 return values are not well documented, and it is
564 \_GL 5.7.1 This object is not to be used in hardware reduced
565 mode, and therefore should not be used on arm64.
569 reduced mode. Hence, do not use this object on arm64.
571 \_GPE 5.3.1 This namespace is for x86 use only. Do not use it
575 though _CID and _CLS may also be used.
577 _INI 6.5.1 Not required, but can be useful in setting up devices
578 when UEFI leaves them in a state that may not be what
594 command line parameter acpi_os=<string> can be used
599 device (e.g., \_SB.DEV0._OSC), or both. When used
601 the ACPI specification are allowed. When used as
602 a device-specific method, the process described for
603 using _DSD MUST be used to create an _OSC definition;
604 out-of-process use of _OSC is not allowed. That is,
605 submit the device-specific _OSC usage description as
611 concerned, _OSI is not to be used to determine what
612 sort of system is being used or what functionality
613 is provided. The _OSC method is to be used instead.
615 _PDC 8.4.1 Deprecated, do not use on arm64.
617 \_PIC 5.8.1 The method should not be used. On arm64, the only
621 Do not use it on arm64.
626 _PRx 7.3.8-11 Use as needed; power management specific. If _PR0 is
629 _PSx 7.3.2-5 Use as needed; power management specific. If _PS0 is
635 ACPI0010) on arm64. This should only be used in
670 ----------------
671 Do not use GPE block devices; these are not supported in the hardware reduced
672 profile used by arm64. Since there are no GPE blocks defined for use on ARM
675 There are two options: GPIO-signaled interrupts (Section 5.6.5), and
676 interrupt-signaled events (Section 5.6.9). Interrupt-signaled events are a
677 new feature in the ACPI 6.1 specification. Either - or both - can be used
679 given SoC. If possible, interrupt-signaled events are recommended.
683 ----------------------
686 not use the deprecated Processor statement in ASL. All multiprocessor systems
688 Devices (see Section 8.4.3.1, _HID ACPI0010); do not use processor aggregator
701 object must correspond to processor IDs used in the MADT.
703 It is recommended that CPPC (8.4.5) be used as the primary model for processor
704 performance control on arm64. C-states and P-states may become available at
715 ----------------------------------
719 GetMemoryMap() boot service is the only mechanism that will be used.
723 -------------------------------------
726 APEI requires the equivalent of an SCI and an NMI on ARMv8. The SCI is used
729 used to indicate fatal errors that cannot be corrected, and require immediate
736 possible. This implies some caution must be used since there could be
738 as the emulated NMI. In Linux, this should not be the case but one should
742 ACPI Objects Not Supported on ARM64
743 -----------------------------------
745 that can be defined, but are not currently of general interest to ARM servers.
748 may not even be a non-ARM implementation yet. Hence, they are not currently
751 The following classes of objects are not supported:
753 - Section 9.2: ambient light sensor devices
755 - Section 9.3: battery devices
757 - Section 9.4: lids (e.g., laptop lids)
759 - Section 9.8.2: IDE controllers
761 - Section 9.9: floppy controllers
763 - Section 9.10: GPE block devices
765 - Section 9.15: PC/AT RTC/CMOS devices
767 - Section 9.16: user presence detection devices
769 - Section 9.17: I/O APIC devices; all GICs must be enumerable via MADT
771 - Section 9.18: time and alarm devices (see 9.15)
773 - Section 10: power source and power meter devices
775 - Section 11: thermal management
777 - Section 12: embedded controllers interface
779 - Section 13: SMBus interfaces