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
26 As both ACPI and Device Tree represent a tree of devices (and their
30 The ACPI implementation enumerates devices behind busses (platform, SPI,
32 to their ACPI handle in the ACPI namespace.
35 enumerated from ACPI namespace. This handle can be used to extract other
43 for the device and add supported ACPI IDs. If this same IP-block is used on
44 some other non-ACPI platform, the driver might work out of the box or needs
47 Adding ACPI support for an existing driver should be pretty
51 /* ACPI IDs here */
54 MODULE_DEVICE_TABLE(acpi, mydrv_acpi_match);
64 configuring GPIOs it can get its ACPI handle and extract this information
65 from ACPI tables.
70 DMA controllers enumerated via ACPI should be registered in the system to
148 Drivers enumerated via ACPI can have names to interrupts in the ACPI table
153 resource in the ACPI table corresponding to its index.
190 Here is what the ACPI namespace for a SPI slave might look like::
208 The SPI device drivers only need to add ACPI IDs in a similar way to
209 the platform device drivers. Below is an example where we add ACPI support
210 to at25 SPI eeprom driver (this is meant for the above ACPI snippet)::
216 MODULE_DEVICE_TABLE(acpi, at25_acpi_match);
261 The slaves behind I2C bus controller only need to add the ACPI IDs like
266 Below is an example of how to add ACPI support to the existing mpu3050
273 MODULE_DEVICE_TABLE(acpi, mpu3050_acpi_match);
323 ACPI 5 introduced two new resources to describe GPIO connections: GpioIo
325 the device to the driver. ACPI 5.1 extended this with _DSD (Device
348 // ACPI 5.1 _DSD used for naming the GPIOs
389 See Documentation/firmware-guide/acpi/gpio-properties.rst for more information
395 ACPI _DSD (Device Specific Data) can be used to describe RS-485 capability
404 // ACPI 5.1 _DSD used for RS-485 capabilities
421 devices there needs to be an ACPI handle that they can use to reference
422 parts of the ACPI namespace that relate to them. In the Linux MFD subsystem
425 - The children share the parent ACPI handle.
426 - The MFD cell can specify the ACPI id of the device.
432 If the ACPI namespace has a device that we can match using an ACPI id or ACPI
446 The ACPI id "XYZ0001" is then used to lookup an ACPI device directly under
447 the MFD device and if found, that ACPI companion device is bound to the
456 regarded as a device identification namespace analogous to the ACPI/PNP device
458 a new (and arguably redundant) ACPI/PNP device ID for a devices with an existing
463 In ACPI, the device identification object called _CID (Compatible ID) is used to
465 belong to one of the namespaces prescribed by the ACPI specification (see
466 Section 6.1.2 of ACPI 6.0 for details) and the DT namespace is not one of them.
468 object be present for all ACPI objects representing devices (Section 6.1 of ACPI
473 existing DT-compatible device identification in ACPI and to satisfy the above
474 requirements following from the ACPI specification at the same time. Namely,
475 if PRP0001 is returned by _HID, the ACPI subsystem will look for the
479 or its value is not valid, the device will not be enumerated by the ACPI
482 which case the ACPI core will leave the device enumeration to the parent's
496 For example, the following ACPI sample might be used to enumerate an lm75-type
531 "composite device" case described above) can be used in the ACPI environment.
535 Refer to Documentation/firmware-guide/acpi/DSD-properties-rules.rst for more
591 To describe this Exar device on the PCI bus, we must start from the ACPI name
596 To find this information, it is necessary to disassemble the BIOS ACPI tables,
630 ACPI description for the Exar PCIe UART, also adding the list of its GPIO line
684 [1] Documentation/firmware-guide/acpi/gpio-properties.rst
686 [2] Documentation/admin-guide/acpi/initrd_table_override.rst
688 [3] ACPI Specifications, Version 6.3 - Paragraph 6.1.1 _ADR Address)