Lines Matching full:acpi

4 ACPI Based Device Enumeration
7 ACPI 5 introduced a set of new resources (UartTSerialBus, I2cSerialBus,
12 SoC/Chipset to appear only in ACPI namespace. These are typically devices
25 As both ACPI and Device Tree represent a tree of devices (and their
29 The ACPI implementation enumerates devices behind busses (platform, SPI and
30 I2C), creates the physical devices and binds them to their ACPI handle in
31 the ACPI namespace.
34 enumerated from ACPI namespace. This handle can be used to extract other
42 for the device and add supported ACPI IDs. If this same IP-block is used on
43 some other non-ACPI platform, the driver might work out of the box or needs
46 Adding ACPI support for an existing driver should be pretty
51 		/* ACPI IDs here */
54 	MODULE_DEVICE_TABLE(acpi, mydrv_acpi_match);
65 configuring GPIOs it can get its ACPI handle and extract this information
66 from ACPI tables.
71 DMA controllers enumerated via ACPI should be registered in the system to
153 Here is what the ACPI namespace for a SPI slave might look like::
171 The SPI device drivers only need to add ACPI IDs in a similar way than with
172 the platform device drivers. Below is an example where we add ACPI support
173 to at25 SPI eeprom driver (this is meant for the above ACPI snippet)::
180 	MODULE_DEVICE_TABLE(acpi, at25_acpi_match);
212 ACPI handle like::
232 The slaves behind I2C bus controller only need to add the ACPI IDs like
237 Below is an example of how to add ACPI support to the existing mpu3050
245 	MODULE_DEVICE_TABLE(acpi, mpu3050_acpi_match);
264 ACPI 5 introduced two new resources to describe GPIO connections: GpioIo
266 the device to the driver. ACPI 5.1 extended this with _DSD (Device
302 		// ACPI 5.1 _DSD used for naming the GPIOs
342 See Documentation/firmware-guide/acpi/gpio-properties.rst for more information about the
349 devices there needs to be an ACPI handle that they can use to reference
350 parts of the ACPI namespace that relate to them. In the Linux MFD subsystem
353   - The children share the parent ACPI handle.
354   - The MFD cell can specify the ACPI id of the device.
360 If the ACPI namespace has a device that we can match using an ACPI id or ACPI
374 The ACPI id "XYZ0001" is then used to lookup an ACPI device directly under
375 the MFD device and if found, that ACPI companion device is bound to the
384 regarded as a device identification namespace analogous to the ACPI/PNP device
386 a new (and arguably redundant) ACPI/PNP device ID for a devices with an existing
391 In ACPI, the device identification object called _CID (Compatible ID) is used to
393 belong to one of the namespaces prescribed by the ACPI specification (see
394 Section 6.1.2 of ACPI 6.0 for details) and the DT namespace is not one of them.
396 object be present for all ACPI objects representing devices (Section 6.1 of ACPI
401 existing DT-compatible device identification in ACPI and to satisfy the above
402 requirements following from the ACPI specification at the same time.  Namely,
403 if PRP0001 is returned by _HID, the ACPI subsystem will look for the
407 or its value is not valid, the device will not be enumerated by the ACPI
410 which case the ACPI core will leave the device enumeration to the parent's
424 For example, the following ACPI sample might be used to enumerate an lm75-type
459 "composite device" case described above) can be used in the ACPI environment.