From: Peter Rosin <peda@axentia.se>
To: Christian Eggers <ceggers@arri.de>, Rob Herring <robh+dt@kernel.org>
Cc: devicetree@vger.kernel.org, linux-iio@vger.kernel.org,
Jonathan Cameron <jic23@kernel.org>,
Hartmut Knaack <knaack.h@gmx.de>,
Lars-Peter Clausen <lars@metafoo.de>,
Peter Meerwald-Stadler <pmeerw@pmeerw.net>,
Jiri Kosina <trivial@kernel.org>
Subject: Re: [PATCH] dt-bindings: iio: io-channel-mux: Fix compatible string in example code
Date: Mon, 27 Jul 2020 12:24:17 +0200 [thread overview]
Message-ID: <cbcf578d-37a0-b807-134b-f7cf2d3d9e02@axentia.se> (raw)
In-Reply-To: <20200727101605.24384-1-ceggers@arri.de>
Hi!
Well spotted, thanks!
On 2020-07-27 12:16, Christian Eggers wrote:
> The correct compatible string is "gpio-mux" (see
> bindings/mux/gpio-mux.txt).
>
> Signed-off-by: Christian Eggers <ceggers@arri.de>
Reviewed-by: Peter Rosin <peda@axentia.se>
Cheers,
Peter
> Cc: stable@vger.kernel.org
> ---
> .../devicetree/bindings/iio/multiplexer/io-channel-mux.txt | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/Documentation/devicetree/bindings/iio/multiplexer/io-channel-mux.txt b/Documentation/devicetree/bindings/iio/multiplexer/io-channel-mux.txt
> index c82794002595..89647d714387 100644
> --- a/Documentation/devicetree/bindings/iio/multiplexer/io-channel-mux.txt
> +++ b/Documentation/devicetree/bindings/iio/multiplexer/io-channel-mux.txt
> @@ -21,7 +21,7 @@ controller state. The mux controller state is described in
>
> Example:
> mux: mux-controller {
> - compatible = "mux-gpio";
> + compatible = "gpio-mux";
> #mux-control-cells = <0>;
>
> mux-gpios = <&pioA 0 GPIO_ACTIVE_HIGH>,
>
next prev parent reply other threads:[~2020-07-27 10:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-27 10:16 [PATCH] dt-bindings: iio: io-channel-mux: Fix compatible string in example code Christian Eggers
2020-07-27 10:24 ` Peter Rosin [this message]
2020-07-30 13:48 ` Sasha Levin
2020-07-31 20:47 ` Rob Herring
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=cbcf578d-37a0-b807-134b-f7cf2d3d9e02@axentia.se \
--to=peda@axentia.se \
--cc=ceggers@arri.de \
--cc=devicetree@vger.kernel.org \
--cc=jic23@kernel.org \
--cc=knaack.h@gmx.de \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=pmeerw@pmeerw.net \
--cc=robh+dt@kernel.org \
--cc=trivial@kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).