device.txt 1.3 KB

123456789101112131415161718192021222324252627282930313233343536
  1. Devices
  2. =======
  3. Device bindings are described by their own individual binding files.
  4. U-Boot provides for some optional properties which are documented here. See
  5. also hid-over-i2c.txt which describes HID devices. See also
  6. Documentation/firmware-guide/acpi/enumeration.rst in the Linux kernel for
  7. the acpi,compatible property.
  8. - acpi,has-power-resource : (boolean) true if this device has a power resource.
  9. This causes an ACPI PowerResource to be written containing the properties
  10. provided by this binding, to describe how to handle powering the device up
  11. and down using GPIOs
  12. - acpi,compatible : compatible string to report
  13. - acpi,ddn : Contains the string to use as the _DDN (DOS (Disk Operating
  14. System) Device Name)
  15. - acpi,hid : Contains the string to use as the HID (Hardware ID)
  16. identifier _HID
  17. - acpi,uid : _UID value for device
  18. - linux,probed : Tells U-Boot to add 'linux,probed' to the ACPI tables so that
  19. Linux will only load the driver if the device can be detected (e.g. on I2C
  20. bus). Note that this is an out-of-tree Linux feature.
  21. Example
  22. -------
  23. elan_touchscreen: elan-touchscreen@10 {
  24. compatible = "i2c-chip";
  25. reg = <0x10>;
  26. acpi,hid = "ELAN0001";
  27. acpi,ddn = "ELAN Touchscreen";
  28. interrupts-extended = <&acpi_gpe GPIO_21_IRQ IRQ_TYPE_EDGE_FALLING>;
  29. linux,probed;
  30. };