From: Andi Shyti <andi.shyti@kernel.org>
To: linux-i2c@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Cc: Wolfram Sang <wsa@kernel.org>, Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Chris Packham <chris.packham@alliedtelesis.co.nz>,
Ryan Chen <ryan_chen@aspeedtech.com>,
Andi Shyti <andi.shyti@kernel.org>
Subject: [PATCH 0/2] Add the clock stretching i2c property
Date: Sun, 12 Mar 2023 14:19:31 +0100 [thread overview]
Message-ID: <20230312131933.248715-1-andi.shyti@kernel.org> (raw)
Hello,
fter a discussion between Krzysztof and Ryan[*], it has become
apparent that the i2c binding is lacking the definition of a
property that needs to be added at a more generic level. This
property is also used by the mpc i2c controller, which has been
updated in the second patch.
As it has been several years since I worked with DTSs, I hope
that I have done everything correctly.
Thank you,
Andi
[*] https://lore.kernel.org/all/c41ee6b5-ddb4-1253-de54-a295b3bab2cc@linaro.org/
Andi Shyti (2):
dt-bindings: i2c: Add the clock stretching property
i2c: mpc: Use the i2c-scl-clk-low-timeout-ms property
Documentation/devicetree/bindings/i2c/i2c-mpc.yaml | 12 ++++++------
Documentation/devicetree/bindings/i2c/i2c.txt | 9 +++++++++
drivers/i2c/busses/i2c-mpc.c | 3 ++-
3 files changed, 17 insertions(+), 7 deletions(-)
--
2.39.2
next reply other threads:[~2023-03-12 13:21 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-12 13:19 Andi Shyti [this message]
2023-03-12 13:19 ` [PATCH 1/2] dt-bindings: i2c: Add the clock stretching property Andi Shyti
2023-03-12 13:43 ` Krzysztof Kozlowski
2023-03-12 13:19 ` [PATCH 2/2] i2c: mpc: Use the i2c-scl-clk-low-timeout-ms property Andi Shyti
2023-03-12 13:44 ` Krzysztof Kozlowski
2023-03-12 13:44 ` Krzysztof Kozlowski
2023-03-12 13:48 ` Andi Shyti
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=20230312131933.248715-1-andi.shyti@kernel.org \
--to=andi.shyti@kernel.org \
--cc=chris.packham@alliedtelesis.co.nz \
--cc=devicetree@vger.kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh+dt@kernel.org \
--cc=ryan_chen@aspeedtech.com \
--cc=wsa@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