From: Rob Herring <robh@kernel.org>
To: Aswath Govindraju <a-govindraju@ti.com>
Cc: Vignesh Raghavendra <vigneshr@ti.com>,
Rob Herring <robh+dt@kernel.org>,
Marc Kleine-Budde <mkl@pengutronix.de>,
linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
Kishon Vijay Abraham I <kishon@ti.com>,
Peter Rosin <peda@axentia.se>
Subject: Re: [PATCH v2 1/2] dt-bindings: mux: Document mux-states property
Date: Mon, 6 Dec 2021 14:55:51 -0600 [thread overview]
Message-ID: <Ya5411zdtB3RJePO@robh.at.kernel.org> (raw)
In-Reply-To: <20211202124053.2835-2-a-govindraju@ti.com>
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@ti.com>
> ---
>
> 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@kernel.org>
next prev parent reply other threads:[~2021-12-06 20:55 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-02 12:40 [PATCH v2 0/2] MUX: Add support for mux-states Aswath Govindraju
2021-12-02 12:40 ` [PATCH v2 1/2] dt-bindings: mux: Document mux-states property Aswath Govindraju
2021-12-06 20:55 ` Rob Herring [this message]
2021-12-02 12:40 ` [PATCH v2 2/2] mux: Add support for reading mux state from consumer DT node Aswath Govindraju
2021-12-17 5:57 ` [PATCH v2 0/2] MUX: Add support for mux-states Peter Rosin
2021-12-17 6:26 ` Peter Rosin
2021-12-18 18:36 ` Peter Rosin
2021-12-18 18:37 ` [PATCH] mux: add missing mux_state_get Peter Rosin
2021-12-20 6:57 ` Aswath Govindraju
2021-12-20 8:50 ` Peter Rosin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Ya5411zdtB3RJePO@robh.at.kernel.org \
--to=robh@kernel.org \
--cc=a-govindraju@ti.com \
--cc=devicetree@vger.kernel.org \
--cc=kishon@ti.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mkl@pengutronix.de \
--cc=peda@axentia.se \
--cc=robh+dt@kernel.org \
--cc=vigneshr@ti.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox