On Sat, Sep 30, 2023 at 06:08:45PM +0100, Caleb Connolly wrote: > This new property allows devices to specify some register values which > are missing on units with third party replacement displays. These > displays use unofficial touch ICs which only implement a subset of the > RMI4 specification. > > Signed-off-by: Caleb Connolly <[email protected]> > --- > To: "Jason A. Donenfeld" <[email protected]> > To: Matthias Schiffer <[email protected]> > To: Rob Herring <[email protected]> > To: Krzysztof Kozlowski <[email protected]> > To: Conor Dooley <[email protected]> > Cc: [email protected] > --- > Documentation/devicetree/bindings/input/syna,rmi4.yaml | 10 ++++++++++ > 1 file changed, 10 insertions(+) > > diff --git a/Documentation/devicetree/bindings/input/syna,rmi4.yaml > b/Documentation/devicetree/bindings/input/syna,rmi4.yaml > index 4d4e1a8e36be..bd6beb67ac21 100644 > --- a/Documentation/devicetree/bindings/input/syna,rmi4.yaml > +++ b/Documentation/devicetree/bindings/input/syna,rmi4.yaml > @@ -49,6 +49,16 @@ properties: > description: > Delay to wait after powering on the device. > > + syna,pdt-fallback-desc: > + $ref: /schemas/types.yaml#/definitions/uint8-array > + description: > + An array of pairs of function number and version. These are used
array of pairs is a matrix, not array. Or it is just 2 values? Needs some size constraints. > + on some devices with replacement displays that use unofficial touch > + controllers. These controllers do report the properties of their PDT PDT? > + entries, but leave the function_number and function_version registers > + blank. These values should match exactly the 5th and 4th bytes of each > + PDT entry from the original display's touch controller. > + > vdd-supply: true > vio-supply: true > > > -- > 2.42.0 >
