Lines Matching full:be
55 Must be supplied if RAS support is provided by the platform. It
56 is recommended this table be supplied.
62 Microsoft only table, will not be 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.
131 Optional, not currently supported, but could be used on ARM if and
134 need to be modified in the ACPI specification.
142 if it had actually occurred. However, this table should not be
143 shipped with a production system; it should be dynamically loaded
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.
165 It is unlikely that this table will be terribly useful. If it is
166 provided, the Global Lock will NOT be used since it is not part of
168 be considered valid.
176 The HW_REDUCED_ACPI flag must be set. All of the fields that are
177 to be ignored when HW_REDUCED_ACPI is set are expected to be set to
180 If an FACS table is provided, the X_FIRMWARE_CTRL field is to be
187 For the DSDT that is also required, the X_DSDT field is to be used,
212 Must be supplied if RAS support is provided by the platform. It
213 is recommended this table be supplied.
228 x86 only table, will not be supported.
243 This table will only be required on certain SBSA platforms (e.g.,
251 x86_64 (AMD) only table, will not be supported.
267 should be used (types 0xA - 0xF).
304 Microsoft only table, will not be supported.
317 use. Since these are not meant to be of general use but are limited
352 Obsolete table, will not be supported.
378 on arm64, and will not be used. If provided, it will be ignored.
396 Microsoft only table, will not be supported.
428 for use with devices that can be added to a running system, but can
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.
505 The expectations on individual ACPI objects that are likely to be used are
507 should be used as needed for a particular platform or particular subsystem,
513 _CCA 6.2.17 This method must be defined for all bus masters
517 these devices so it does not need to be repeated.
522 attributes; the presence of an SMMU can be used to
524 default to non-coherent, but be made coherent with
542 _DDN 6.1.4 This field can be used for a device name. However,
543 it is meant for DOS device names (e.g., COM1), so be
546 _DSD 6.2.5 To be used with caution. If this object is used, try
549 should it be necessary to create a new _DSD UUID.
553 device properties are used. A driver will not be
556 the UUID or device properties must then be registered
558 more than one OS will be registering entries.
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.
567 _GLK 6.5.7 This object requires a global lock be defined; there
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
587 that can be turned on or off.
590 that can be turned on or off.
594 command line parameter acpi_os=<string> can be used
597 _OSC 6.2.11 This method can be a global method in ACPI (i.e.,
598 \_SB._OSC), or it may be associated with a specific
603 using _DSD MUST be used to create an _OSC definition;
611 concerned, _OSI is not to be used to determine what
613 is provided. The _OSC method is to be used instead.
617 \_PIC 5.8.1 The method should not be used. On arm64, the only
627 defined, _PR3 must also be defined.
630 defined, _PS3 must also be defined. If clocks or
631 regulators need adjusting to be consistent with power
635 ACPI0010) on arm64. This should only be used in
640 \_SB 5.3.1 Required on arm64; all devices must be defined in this
646 7.2.4 that can be turned on or off. See also the STAO table
673 platforms, ACPI events must be signaled differently.
677 new feature in the ACPI 6.1 specification. Either - or both - can be used
678 on a given platform, and which to use may be dependent of limitations in any
685 Processors should now be defined as Device objects with _HID ACPI0007; do
695 determining which processors can be turned on or off and the circumstances
700 MADT for GICs are expected to be in synchronization. The _UID of the Device
703 It is recommended that CPPC (8.4.5) be used as the primary model for processor
708 implementation of PSCI; this will be the only mechanism supported by ACPI
719 GetMemoryMap() boot service is the only mechanism that will be used.
727 to notify the OSPM of errors that have occurred but can be corrected and the
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
739 be aware it could happen.
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
769 - Section 9.17: I/O APIC devices; all GICs must be enumerable via MADT