@@ -24,6 +24,12 @@ properties:
interrupts:
maxItems: 1
+ panel:
+ description: If this is a touchscreen, the panel it's connected to. This
+ indicates that the panel and touchscreen are expected to be power
+ sequenced together.
+ $ref: /schemas/types.yaml#/definitions/phandle
+
reset-gpios:
description: Reset GPIO; not all touchscreens using eKTH6915 hook this up.
@@ -30,6 +30,12 @@ properties:
interrupts:
maxItems: 1
+ panel:
+ description: If this is a touchscreen, the panel it's connected to. This
+ indicates that the panel and touchscreen are expected to be power
+ sequenced together.
+ $ref: /schemas/types.yaml#/definitions/phandle
+
reset-gpios:
true
@@ -44,6 +44,12 @@ properties:
description: HID descriptor address
$ref: /schemas/types.yaml#/definitions/uint32
+ panel:
+ description: If this is a touchscreen, the panel it's connected to. This
+ indicates that the panel and touchscreen are expected to be power
+ sequenced together.
+ $ref: /schemas/types.yaml#/definitions/phandle
+
post-power-on-delay-ms:
description: Time required by the device after enabling its regulators
or powering it on, before it is ready for communication.
As talked about in the patch ("drm/panel: Add a way for other devices to follow panel state"), touchscreens that are connected to panels are generally expected to be power sequenced together with the panel they're attached to. Today, nothing provides information allowing you to find out that a touchscreen is connected to a panel. Let's add a phandle for this. Signed-off-by: Douglas Anderson <dianders@chromium.org> --- Documentation/devicetree/bindings/input/elan,ekth6915.yaml | 6 ++++++ Documentation/devicetree/bindings/input/goodix,gt7375p.yaml | 6 ++++++ Documentation/devicetree/bindings/input/hid-over-i2c.yaml | 6 ++++++ 3 files changed, 18 insertions(+)