Lines Matching +full:- +full:only
10 the table signature (the first four bytes of the table) is the only portion
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
83 time as ARM-compatible hardware is available, and the specification
103 Microsoft only table, will not be supported.
111 ACPI tables contain only one DSDT but can contain one or more SSDTs,
112 which are optional. Each SSDT can only add to the ACPI namespace,
119 x86 only table, will not be supported.
132 only if one uses the GPE_BIT field to represent an IRQ number, since
144 and executed with the ACPICA tools only during testing.
151 UEFI-based; if it is UEFI-based, this table may be supplied. When this
167 the hardware reduced profile, and only 64-bit address fields will
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).
206 ARM-specific error sources have been defined; please use those or the
209 error handling is possible if and only if Trusted Firmware is being
228 x86 only table, will not be supported.
240 arm64 only table, required in order to describe IO topology, SMMUs,
243 This table will only be required on certain SBSA platforms (e.g.,
244 when using GICv3-ITS and an SMMU); on SBSA Level 0 platforms, it
251 x86_64 (AMD) only table, will not be supported.
257 x86 only table as of ACPI 5.1; starting with ACPI 6.0, processor
266 Required for arm64. Only the GIC interrupt controller structures
267 should be used (types 0xA - 0xF).
271 **Memory-mapped ConFiGuration space**
304 Microsoft only table, will not be supported.
312 OEMx Signature of "OEMx" only
333 non-architectural features.
377 Since this table can only provide 32-bit addresses, it is deprecated
396 Microsoft only table, will not be supported.
420 Optional, but if used, only the GICC Affinity structures are read.
432 An SSDT can only ADD to the ACPI namespace. It cannot modify or
435 These tables are optional, however. ACPI tables should contain only
442 Optional, but only necessary in virtualized environments in order to
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 ------------
514 on arm64 - there are no assumptions made about
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.
548 Device Properties UUID. Only in rare circumstances
571 \_GPE 5.3.1 This namespace is for x86 use only. Do not use it
600 as a global method, only capabilities published in
602 a device-specific method, the process described for
604 out-of-process use of _OSC is not allowed. That is,
605 submit the device-specific _OSC usage description as
617 \_PIC 5.8.1 The method should not be used. On arm64, the only
620 \_PR 5.3.1 This namespace is for x86 use only on legacy systems.
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 ----------------
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 ----------------------
704 performance control on arm64. C-states and P-states may become available at
708 implementation of PSCI; this will be the only mechanism supported by ACPI
710 parking protocol is possible, but discouraged, since only PSCI is supported
715 ----------------------------------
718 For arm64, we will only support UEFI for booting with ACPI, hence the UEFI
719 GetMemoryMap() boot service is the only mechanism that will be used.
723 -------------------------------------
743 -----------------------------------
748 may not even be a non-ARM implementation yet. Hence, they are not currently
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