Lines Matching refs:used

6 If a section number is used, it refers to a section number in the ACPI
7 specification where the object is defined.  If "Signature Reserved" is used,
77        Optional, not currently supported, but could be used on ARM if and
104        provided, the Global Lock will NOT be used since it is not part of
117        used, not FIRMWARE_CTRL.
119        If PSCI is used (as is recommended), make sure that ARM_BOOT_ARCH is
123        For the DSDT that is also required, the X_DSDT field is to be used,
139        if Trusted Firmware is being used on arm64.
165        should be used (types 0xA - 0xE).
198        on arm64, and will not be used.
222        Optional, but if used, only the GICC Affinity structures are read.
285 _BDN   6.5.3           Optional; not likely to be used on arm64.
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,
314 _DSD   6.2.5           To be used with caution.  If this object is used, try
321                        device properties are used.  A driver will not be
340 _FIX   6.2.7           x86 specific, not used on arm64.
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.
355                        device probing, though _CID and _CLS may also be used.
385                        command line parameter acpi_os=<string> can be used
390                        device (e.g., \_SB.DEV0._OSC), or both.  When used
392                        the ACPI specification are allowed.  When used as
394                        using _DSD MUST be used to create an _OSC definition;
404                        cannot be used to determine what sort of system is
405                        being used or what functionality is provided.  The
406                        _OSC method is to be used instead.
412 \_PIC  5.8.1           The method should not be used.  On arm64, the only
495 profile used by arm64.  Since there are no GPE blocks defined for use on ARM
496 platforms, GPIO-signaled interrupts should be used for creating system events.
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
524 GetMemoryMap() boot service is the only mechanism that will be used.
531 APEI requires the equivalent of an SCI and an NMI on ARMv8.  The SCI is used
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