linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Eddie James <eajames@linux.ibm.com>
To: linux-i2c@vger.kernel.org
Cc: devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
	peda@axentia.se, robh+dt@kernel.org,
	Eddie James <eajames@linux.ibm.com>
Subject: [PATCH v2 1/2] dt-bindings: i2c: i2c-mux-pca954x: Define the reset-shared-hogged gpio
Date: Tue, 27 Jul 2021 11:03:14 -0500	[thread overview]
Message-ID: <20210727160315.15575-2-eajames@linux.ibm.com> (raw)
In-Reply-To: <20210727160315.15575-1-eajames@linux.ibm.com>

Add a property to describe a reset input that is shared between multiple
PCA953x muxes.

Signed-off-by: Eddie James <eajames@linux.ibm.com>
---
 Documentation/devicetree/bindings/i2c/i2c-mux-pca954x.yaml | 5 +++++
 1 file changed, 5 insertions(+)

diff --git a/Documentation/devicetree/bindings/i2c/i2c-mux-pca954x.yaml b/Documentation/devicetree/bindings/i2c/i2c-mux-pca954x.yaml
index 9f1726d0356b..06b9f8385bd7 100644
--- a/Documentation/devicetree/bindings/i2c/i2c-mux-pca954x.yaml
+++ b/Documentation/devicetree/bindings/i2c/i2c-mux-pca954x.yaml
@@ -49,6 +49,11 @@ properties:
   reset-gpios:
     maxItems: 1
 
+  reset-shared-hogged-gpios:
+    maxItems: 1
+    description: Reference to a shared, hogged GPIO connected to the reset
+      input of several PCA954x muxes.
+
   i2c-mux-idle-disconnect:
     type: boolean
     description: Forces mux to disconnect all children in idle state. This is
-- 
2.27.0


  reply	other threads:[~2021-07-27 16:03 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-27 16:03 [PATCH v2 0/2] i2c: mux: pca954x: Support multiple devices on a single reset line Eddie James
2021-07-27 16:03 ` Eddie James [this message]
2021-07-27 16:03 ` [PATCH v2 2/2] " Eddie James
2021-08-02 20:46   ` Rob Herring
2021-08-02 21:51     ` Eddie James
2021-08-02 22:35       ` Rob Herring
2021-08-04  7:50       ` Peter Rosin
2021-08-04 13:28         ` Rob Herring
2021-08-04 15:12           ` Eddie James
2021-08-04 16:35             ` 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=20210727160315.15575-2-eajames@linux.ibm.com \
    --to=eajames@linux.ibm.com \
    --cc=devicetree@vger.kernel.org \
    --cc=linux-i2c@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --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).