Lines Matching refs:be
29 Must be supplied if RAS support is provided by the platform. It
30 is recommended this table be supplied.
34 Microsoft only table, will not be supported.
53 Microsoft only table, will not be supported.
57 Microsoft only table, will not be supported.
69 x86 only table, will not be supported.
77 Optional, not currently supported, but could be used on ARM if and
80 need to be modified in the ACPI specification.
86 if it had actually occurred. However, this table should not be
87 shipped with a production system; it should be dynamically loaded
92 On a platform supports RAS, this table must be supplied if it is not
93 UEFI-based; if it is UEFI-based, this table may be supplied. When this
94 table is not present, UEFI run time service will be utilized to save
99 Obsolete table, will not be supported.
103 It is unlikely that this table will be terribly useful. If it is
104 provided, the Global Lock will NOT be used since it is not part of
106 be considered valid.
112 The HW_REDUCED_ACPI flag must be set. All of the fields that are
113 to be ignored when HW_REDUCED_ACPI is set are expected to be set to
116 If an FACS table is provided, the X_FIRMWARE_CTRL field is to be
123 For the DSDT that is also required, the X_DSDT field is to be used,
141 Must be supplied if RAS support is provided by the platform. It
142 is recommended this table be supplied.
146 x86 only table, will not be supported.
154 x86_64 (AMD) only table, will not be supported.
159 use with ARM and will be recommended in order to support ACPI power
165 should be used (types 0xA - 0xE).
181 Microsoft only table, will not be supported.
198 on arm64, and will not be used.
206 Microsoft only table, will not be supported.
228 for use with devices that can be added to a running system, but can
255 Microsoft only table, will not be supported.
259 Microsoft only table, will not be supported.
263 Microsoft only table, will not be supported.
267 Microsoft only table, will not be supported.
285 _BDN 6.5.3 Optional; not likely to be used on arm64.
287 _CCA 6.2.17 This method should be defined for all bus masters
292 _CDM 6.2.1 Optional, to be used only for processor devices.
300 _DCK 6.5.2 Optional; not likely to be used on arm64.
302 _DDN 6.1.4 This field can be used for a device name. However,
303 it is meant for DOS device names (e.g., COM1), so be
314 _DSD 6.2.5 To be used with caution. If this object is used, try
317 should it be necessary to create a new _DSD UUID.
321 device properties are used. A driver will not be
324 the UUID or device properties must then be registered
326 more than one OS will be registering entries.
342 \_GL 5.7.1 This object is not to be used in hardware reduced
343 mode, and therefore should not be used on arm64.
345 _GLK 6.5.7 This object requires a global lock be defined; there
355 device probing, though _CID and _CLS may also be used.
362 some cases, this may be easier to use than _DSD.
364 _INI 6.5.1 Not required, but can be useful in setting up devices
365 when UEFI leaves them in a state that may not be what
378 that can be turned on or off.
381 that can be turned on or off.
385 command line parameter acpi_os=<string> can be used
388 _OSC 6.2.11 This method can be a global method in ACPI (i.e.,
389 \_SB._OSC), or it may be associated with a specific
394 using _DSD MUST be used to create an _OSC definition;
404 cannot be used to determine what sort of system is
406 _OSC method is to be used instead.
412 \_PIC 5.8.1 The method should not be used. On arm64, the only
428 defined, _PR3 must also be defined.
437 defined, _PS3 must also be defined. If clocks or
438 regulators need adjusting to be consistent with power
451 \_SB 5.3.1 Required on arm64; all devices must be defined in this
462 7.1.4 that can be turned on or off.
496 platforms, GPIO-signaled interrupts should be used for creating system events.
502 should be completed in the 6.0 version of the specification. Processor
503 performance control will be handled differently for arm64 at that point
504 in time. Processor aggregator devices (section 8.5) will not be used,
508 recommended that CPPC (8.4.5) be used as the primary model. This will
509 still be useful into the future. C-states and P-states will still be
513 implementation of PSCI; this will be the only mechanism supported by ACPI
516 More details will be provided on the release of the ACPI 6.0 specification.
524 GetMemoryMap() boot service is the only mechanism that will be used.
532 to notify the OSPM of errors that have occurred but can be corrected and the
534 used to indicate fatal errors that cannot be corrected, and require immediate
541 GPIO-signaled interrupt possible. This implies some caution must be used
542 since there could be interrupts at higher privilege levels or even interrupts
543 at the same priority as the emulated NMI. In Linux, this should not be the
544 case but one should be aware it could happen.
550 that can be defined, but are not currently of general interest to ARM servers.
570 -- Section 9.17: I/O APIC devices; all GICs must be enumerable via MADT
579 there may not yet be a non-ARM implementation. Hence, they are currently not