From: Biwen Li <biwen.li@nxp.com>
To: peda@axentia.se, leoyang.li@nxp.com, robh+dt@kernel.org,
mark.rutland@arm.com
Cc: linux-i2c@vger.kernel.org, linux-kernel@vger.kernel.org,
devicetree@vger.kernel.org, Biwen Li <biwen.li@nxp.com>
Subject: [v2,2/2] dt-bindings: i2c-mux-pca954x: Add optional property i2c-mux-never-disable
Date: Mon, 30 Sep 2019 11:25:03 +0800 [thread overview]
Message-ID: <20190930032503.44425-2-biwen.li@nxp.com> (raw)
In-Reply-To: <20190930032503.44425-1-biwen.li@nxp.com>
The patch adds an optional property i2c-mux-never-disable
Signed-off-by: Biwen Li <biwen.li@nxp.com>
---
Change in v2:
- update documentation
Documentation/devicetree/bindings/i2c/i2c-mux-pca954x.txt | 1 +
1 file changed, 1 insertion(+)
diff --git a/Documentation/devicetree/bindings/i2c/i2c-mux-pca954x.txt b/Documentation/devicetree/bindings/i2c/i2c-mux-pca954x.txt
index 30ac6a60f041..71b73d0fdb62 100644
--- a/Documentation/devicetree/bindings/i2c/i2c-mux-pca954x.txt
+++ b/Documentation/devicetree/bindings/i2c/i2c-mux-pca954x.txt
@@ -34,6 +34,7 @@ Optional Properties:
- first cell is the pin number
- second cell is used to specify flags.
See also Documentation/devicetree/bindings/interrupt-controller/interrupts.txt
+ - i2c-mux-never-disable: always forces mux to be enabled.
Example:
--
2.17.1
next prev parent reply other threads:[~2019-09-30 3:35 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-30 3:25 [v2,1/2] i2c: pca954x: Add property to skip disabling PCA954x MUX device Biwen Li
2019-09-30 3:25 ` Biwen Li [this message]
2019-10-11 14:44 ` [v2,2/2] dt-bindings: i2c-mux-pca954x: Add optional property i2c-mux-never-disable Rob Herring
2019-10-14 3:21 ` [EXT] " Biwen Li
2019-10-14 4:16 ` Biwen Li
2019-10-14 7:06 ` Peter Rosin
2019-10-14 7:26 ` Biwen Li
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=20190930032503.44425-2-biwen.li@nxp.com \
--to=biwen.li@nxp.com \
--cc=devicetree@vger.kernel.org \
--cc=leoyang.li@nxp.com \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=peda@axentia.se \
--cc=robh+dt@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).