Lines Matching full:be
34 Must be supplied if RAS support is provided by the platform. It
35 is recommended this table be supplied.
41 Microsoft only table, will not be supported.
68 License has changed and should be usable. Optional if used instead
75 Microsoft only table, will not be supported.
91 x86 only table, will not be supported.
103 Optional, not currently supported, but could be used on ARM if and
106 need to be modified in the ACPI specification.
114 if it had actually occurred. However, this table should not be
115 shipped with a production system; it should be dynamically loaded
122 On a platform supports RAS, this table must be supplied if it is not
123 UEFI-based; if it is UEFI-based, this table may be supplied. When this
124 table is not present, UEFI run time service will be utilized to save
131 Obsolete table, will not be supported.
137 It is unlikely that this table will be terribly useful. If it is
138 provided, the Global Lock will NOT be used since it is not part of
140 be considered valid.
148 The HW_REDUCED_ACPI flag must be set. All of the fields that are
149 to be ignored when HW_REDUCED_ACPI is set are expected to be set to
152 If an FACS table is provided, the X_FIRMWARE_CTRL field is to be
159 For the DSDT that is also required, the X_DSDT field is to be used,
184 Must be supplied if RAS support is provided by the platform. It
185 is recommended this table be supplied.
191 x86 only table, will not be supported.
206 This table will only be required on certain SBSA platforms (e.g.,
214 x86_64 (AMD) only table, will not be supported.
230 should be used (types 0xA - 0xF).
260 Microsoft only table, will not be supported.
273 use. Since these are not meant to be of general use but are limited
294 Obsolete table, will not be supported.
313 on arm64, and will not be used. If provided, it will be ignored.
325 Microsoft only table, will not be supported.
357 for use with devices that can be added to a running system, but can
399 Microsoft only table, will not be supported.
405 Microsoft only table, will not be supported.
411 Microsoft only table, will not be supported.
417 Microsoft only table, will not be supported.
434 The expectations on individual ACPI objects that are likely to be used are
436 should be used as needed for a particular platform or particular subsystem,
442 _CCA 6.2.17 This method must be defined for all bus masters
446 these devices so it does not need to be repeated.
451 attributes; the presence of an SMMU can be used to
453 default to non-coherent, but be made coherent with
471 _DDN 6.1.4 This field can be used for a device name. However,
472 it is meant for DOS device names (e.g., COM1), so be
475 _DSD 6.2.5 To be used with caution. If this object is used, try
478 should it be necessary to create a new _DSD UUID.
482 device properties are used. A driver will not be
485 the UUID or device properties must then be registered
487 more than one OS will be registering entries.
493 \_GL 5.7.1 This object is not to be used in hardware reduced
494 mode, and therefore should not be used on arm64.
496 _GLK 6.5.7 This object requires a global lock be defined; there
504 though _CID and _CLS may also be used.
506 _INI 6.5.1 Not required, but can be useful in setting up devices
507 when UEFI leaves them in a state that may not be what
516 that can be turned on or off.
519 that can be turned on or off.
523 command line parameter acpi_os=<string> can be used
526 _OSC 6.2.11 This method can be a global method in ACPI (i.e.,
527 \_SB._OSC), or it may be associated with a specific
532 using _DSD MUST be used to create an _OSC definition;
540 concerned, _OSI is not to be used to determine what
542 is provided. The _OSC method is to be used instead.
546 \_PIC 5.8.1 The method should not be used. On arm64, the only
556 defined, _PR3 must also be defined.
559 defined, _PS3 must also be defined. If clocks or
560 regulators need adjusting to be consistent with power
564 ACPI0010) on arm64. This should only be used in
569 \_SB 5.3.1 Required on arm64; all devices must be defined in this
575 7.2.4 that can be turned on or off. See also the STAO table
602 platforms, ACPI events must be signaled differently.
606 new feature in the ACPI 6.1 specification. Either - or both - can be used
607 on a given platform, and which to use may be dependent of limitations in any
614 Processors should now be defined as Device objects with _HID ACPI0007; do
624 determining which processors can be turned on or off and the circumstances
629 MADT for GICs are expected to be in synchronization. The _UID of the Device
632 It is recommended that CPPC (8.4.5) be used as the primary model for processor
637 implementation of PSCI; this will be the only mechanism supported by ACPI
648 GetMemoryMap() boot service is the only mechanism that will be used.
656 to notify the OSPM of errors that have occurred but can be corrected and the
658 used to indicate fatal errors that cannot be corrected, and require immediate
665 possible. This implies some caution must be used since there could be
667 as the emulated NMI. In Linux, this should not be the case but one should
668 be aware it could happen.
674 that can be defined, but are not currently of general interest to ARM servers.
677 may not even be a non-ARM implementation yet. Hence, they are not currently
698 - Section 9.17: I/O APIC devices; all GICs must be enumerable via MADT