From: Bastian Stender <bst@pengutronix.de>
To: Peter Rosin <peda@axentia.se>, Wolfram Sang <wsa@the-dreams.de>
Cc: linux-i2c@vger.kernel.org, devicetree@vger.kernel.org,
Michael Lawnick <ml.lawnick@gmx.de>,
kernel@pengutronix.de, Bastian Stender <bst@pengutronix.de>
Subject: [PATCH v2 2/3] i2c: Documentation: i2c-topology: i2c-mux-pca954x can be mux-locked via dt
Date: Fri, 4 May 2018 15:04:48 +0200 [thread overview]
Message-ID: <20180504130449.13730-2-bst@pengutronix.de> (raw)
In-Reply-To: <20180504130449.13730-1-bst@pengutronix.de>
Signed-off-by: Bastian Stender <bst@pengutronix.de>
---
Documentation/i2c/i2c-topology | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/Documentation/i2c/i2c-topology b/Documentation/i2c/i2c-topology
index f74d78b53d4d..165af7898e50 100644
--- a/Documentation/i2c/i2c-topology
+++ b/Documentation/i2c/i2c-topology
@@ -47,7 +47,8 @@ i2c-mux-gpmux Normally parent-locked, mux-locked iff
i2c-mux-ltc4306 Mux-locked
i2c-mux-mlxcpld Parent-locked
i2c-mux-pca9541 Parent-locked
-i2c-mux-pca954x Parent-locked
+i2c-mux-pca954x Normally parent-locked, mux-locked iff
+ specified in device-tree.
i2c-mux-pinctrl Normally parent-locked, mux-locked iff
all involved pinctrl devices are controlled
by the same i2c root adapter that they mux.
--
2.17.0
next prev parent reply other threads:[~2018-05-04 13:05 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-04 13:04 [PATCH v2 1/3] dt: bindings: i2c-mux-pca954x: add mux-locked property Bastian Stender
2018-05-04 13:04 ` Bastian Stender [this message]
2018-05-04 13:04 ` [PATCH v2 3/3] i2c: mux: pca954x: add option to use as mux-locked Bastian Stender
2018-05-07 7:04 ` Peter Rosin
2018-05-04 13:10 ` [PATCH v2 1/3] dt: bindings: i2c-mux-pca954x: add mux-locked property Bastian Stender
2018-05-07 9:07 ` Peter Rosin
2018-05-14 12:26 ` Bastian Stender
2018-05-14 13:16 ` Peter Rosin
2018-05-07 17:01 ` 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=20180504130449.13730-2-bst@pengutronix.de \
--to=bst@pengutronix.de \
--cc=devicetree@vger.kernel.org \
--cc=kernel@pengutronix.de \
--cc=linux-i2c@vger.kernel.org \
--cc=ml.lawnick@gmx.de \
--cc=peda@axentia.se \
--cc=wsa@the-dreams.de \
/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).