On Thu, 02 Dec 2021 18:10:52 +0530, Aswath Govindraju wrote: > In some cases, it is required to provide the state to which the mux > controller has to be set to, from the consumer device tree node. Document > the property mux-states that can be used for adding this support. > > Signed-off-by: Aswath Govindraju <a-govindraju@xxxxxx> > --- > > Note: > - on running dt_binding_check with "DT_CHECKER_FLAGS=-m" the following > error was seen, > > LINT Documentation/devicetree/bindings > CHKDT Documentation/devicetree/bindings/processed-schema-examples.json > SCHEMA Documentation/devicetree/bindings/processed-schema-examples.json > DTC Documentation/devicetree/bindings/mux/mux-controller.example.dt.yaml > CHECK Documentation/devicetree/bindings/mux/mux-controller.example.dt.yaml > /home/gsaswath/presil/ks3-linux-integrated/linux/Documentation/devicetree/bindings/ > mux/mux-controller.example.dt.yaml: can-phy4: 'mux-states' does not match any of > the regexes: 'pinctrl-[0-9]+' > From schema: /home/gsaswath/presil/ks3-linux-integrated/linux/ > Documentation/devicetree/bindings/phy/ti,tcan104x-can.yaml > > "mux-states" is a new property that is being added and the patch adding this > property to TCAN104x can transceiver bindings will be sent as a follow up > of this series. > > .../devicetree/bindings/mux/gpio-mux.yaml | 11 ++++++-- > .../devicetree/bindings/mux/mux-consumer.yaml | 21 +++++++++++++++ > .../bindings/mux/mux-controller.yaml | 26 ++++++++++++++++++- > 3 files changed, 55 insertions(+), 3 deletions(-) > Reviewed-by: Rob Herring <robh@xxxxxxxxxx>
