From: Horatiu Vultur <horatiu.vultur@microchip.com>
To: <peda@axentia.se>, <robh+dt@kernel.org>,
<linux-i2c@vger.kernel.org>, <devicetree@vger.kernel.org>,
<linux-kernel@vger.kernel.org>
Cc: Horatiu Vultur <horatiu.vultur@microchip.com>
Subject: [PATCH v3 1/2] dt-bindings: i2c-mux: Add property for settle time
Date: Mon, 1 Nov 2021 13:25:44 +0100 [thread overview]
Message-ID: <20211101122545.3417624-2-horatiu.vultur@microchip.com> (raw)
In-Reply-To: <20211101122545.3417624-1-horatiu.vultur@microchip.com>
Some HW requires some time for the signals to settle after the muxing is
changed. Allow this time to be specified in device tree.
Signed-off-by: Horatiu Vultur <horatiu.vultur@microchip.com>
---
Documentation/devicetree/bindings/i2c/i2c-mux.yaml | 6 ++++++
1 file changed, 6 insertions(+)
diff --git a/Documentation/devicetree/bindings/i2c/i2c-mux.yaml b/Documentation/devicetree/bindings/i2c/i2c-mux.yaml
index 24cac36037f5..4628ff6340c1 100644
--- a/Documentation/devicetree/bindings/i2c/i2c-mux.yaml
+++ b/Documentation/devicetree/bindings/i2c/i2c-mux.yaml
@@ -29,6 +29,12 @@ properties:
'#size-cells':
const: 0
+ settle-time-us:
+ default: 0
+ description:
+ The time required for the signals to settle. Currently only the
+ i2c-mux-gpmux driver supports this optional binding.
+
patternProperties:
'^i2c@[0-9a-f]+$':
$ref: /schemas/i2c/i2c-controller.yaml
--
2.33.0
next prev parent reply other threads:[~2021-11-01 12:26 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-01 12:25 [PATCH v3 0/2] i2c-mux-gpmux: Support settle-time-us property Horatiu Vultur
2021-11-01 12:25 ` Horatiu Vultur [this message]
2021-11-01 14:32 ` [PATCH v3 1/2] dt-bindings: i2c-mux: Add property for settle time Peter Rosin
2021-11-01 21:32 ` Horatiu Vultur
2021-11-02 18:37 ` Rob Herring
2021-11-02 22:27 ` Horatiu Vultur
2021-11-03 11:44 ` Peter Rosin
2021-11-03 14:13 ` Rob Herring
2021-11-01 12:25 ` [PATCH v3 2/2] i2c-mux-gpmux: Support settle-time-us property Horatiu Vultur
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=20211101122545.3417624-2-horatiu.vultur@microchip.com \
--to=horatiu.vultur@microchip.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.