On Tue, Nov 21, 2023 at 12:00:18AM +0200, Dmitry Baryshkov wrote: > Add description of the USB-C AltModes supported on the particular USB-C > connector. This is required for devices like Qualcomm Robotics RB5, > which have no other way to express alternative modes supported by the > hardware platform. > > Signed-off-by: Dmitry Baryshkov <dmitry.baryshkov@xxxxxxxxxx> > --- > .../bindings/connector/usb-connector.yaml | 29 +++++++++++++++++++ > 1 file changed, 29 insertions(+) > > diff --git a/Documentation/devicetree/bindings/connector/usb-connector.yaml b/Documentation/devicetree/bindings/connector/usb-connector.yaml > index 7c8a3e8430d3..c1aaac861d9d 100644 > --- a/Documentation/devicetree/bindings/connector/usb-connector.yaml > +++ b/Documentation/devicetree/bindings/connector/usb-connector.yaml > @@ -171,6 +171,28 @@ properties: > offer the power, Capability Mismatch is set. Required for power sink and > power dual role. > > + altmodes: > + type: object > + description: List of Alternative Modes supported by the schematics on the > + particular device. This is only necessary if there are no other means to > + discover supported alternative modes (e.g. through the UCSI firmware > + interface). Move additionalProperties here. > + > + patternProperties: > + "^(displayport)$": > + type: object > + description: > + A single USB-C Alternative Mode as supported by the USB-C connector logic. Move additionalProperties here. And a blank line > + properties: > + svid: > + $ref: /schemas/types.yaml#/definitions/uint16 > + description: Unique value assigned by USB-IF to the Vendor / AltMode. blank line Since you've constrained the node name, then the only possible value here is 0xff01? OTOH, I don't know that we want to enumerate all possible values here especially if there could be lots of vendor modes. But then again, maybe better to just wait and see if that becomes a problem. With those nits fixed, Reviewed-by: Rob Herring <robh@xxxxxxxxxx>
