Lines Matching +full:i2c +full:- +full:topology
1 .. SPDX-License-Identifier: GPL-2.0
13 that are accessed through memory-mapped registers.
15 In order to support this and re-use the existing drivers as much as
18 - Devices that have no bus connector resource are represented as
21 - Devices behind real busses where there is a connector resource
30 I2C), creates the physical devices and binds them to their ACPI handle in
33 This means that when ACPI_HANDLE(dev) returns non-NULL the device was
35 device-specific configuration. There is an example of this below.
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
201 "byte-len", 1024,
202 "addr-mode", 2,
203 "page-size, 32
220 status = acpi_evaluate_object(ACPI_HANDLE(&spi->dev), "_DSM",
229 I2C serial bus support
232 The slaves behind I2C bus controller only need to add the ACPI IDs like
233 with the platform and SPI drivers. The I2C core automatically enumerates
272 ToUUID("daffd814-6eba-4d8c-8a91-bc9bbf4aa301"),
274 Package () { "compatible", Package () { "pwm-leds" } },
275 Package () { "label", "alarm-led" },
289 In the above example the PWM-based LED driver references to the PWM channel 0
337 ToUUID("daffd814-6eba-4d8c-8a91-bc9bbf4aa301"),
340 Package () {"power-gpios", Package() {^DEV, 0, 0, 0 }},
341 Package () {"irq-gpios", Package() {^DEV, 1, 0, 0 }},
351 Documentation/admin-guide/gpio/.
374 See Documentation/firmware-guide/acpi/gpio-properties.rst for more information
385 - The children share the parent ACPI handle.
386 - The MFD cell can specify the ACPI id of the device.
429 6.0). For non-enumerable bus types that object must be _HID and its value must
433 existing DT-compatible device identification in ACPI and to satisfy the above
441 (except when an I2C or SPI link from the device to its parent is present, in
456 For example, the following ACPI sample might be used to enumerate an lm75-type
457 I2C temperature sensor and match it to the driver using the Device Tree
464 ToUUID("daffd814-6eba-4d8c-8a91-bc9bbf4aa301"),
495 Refer to Documentation/firmware-guide/acpi/DSD-properties-rules.rst for more
505 in a fixed position (ethernet, Wi-Fi, serial ports, etc.). In this conditions it
507 topology.
515 16 GPIOs and we want to add the property ``gpio-line-names`` [1] to these pins.
534 07:00.0 Serial controller: Exar Corp. XR17V3521 Dual PCIe UART (rev 03) <-- Exar
537 The bus topology is::
539 -[0000:00]-+-00.0
541 +-13.0-[01]----00.0
542 +-13.1-[02]----00.0
543 +-13.2-[03]--
544 +-14.0-[04]----00.0
545 +-14.1-[05-09]----00.0-[06-09]--+-01.0-[07]----00.0 <-- Exar
546 | +-02.0-[08]----00.0
547 | \-03.0-[09]--
549 \-1f.1
554 Bus: 0 - Device: 14 - Function: 1
562 acpixtract -a acpidump
563 iasl -e ssdt?.* -d dsdt.dat
609 ToUUID("daffd814-6eba-4d8c-8a91-bc9bbf4aa301"),
614 "gpio-line-names",
639 created analyzing the position of the Exar UART in the PCI bus topology.
644 [1] Documentation/firmware-guide/acpi/gpio-properties.rst
646 [2] Documentation/admin-guide/acpi/initrd_table_override.rst
648 [3] ACPI Specifications, Version 6.3 - Paragraph 6.1.1 _ADR Address)
650 referenced 2020-11-18