From: Heiner Kallweit <hkallweit1@gmail.com>
To: Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Wolfram Sang <wsa@kernel.org>
Cc: "linux-i2c@vger.kernel.org" <linux-i2c@vger.kernel.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>
Subject: [PATCH v3 0/3] i2c: gpio: support write-only sda
Date: Sun, 15 Jan 2023 11:10:57 +0100 [thread overview]
Message-ID: <3a5545f3-f858-2c80-8bd4-2e0d401a1dc0@gmail.com> (raw)
There are slave devices that understand I2C but have read-only
SDA and SCL. Examples are FD650 7-segment LED controller and
its derivatives. Typical board designs don't even have a
pull-up for both pins. This patch makes i2c-gpio usable with
such devices, based on new DT property i2c-gpio,sda-output-only.
v2:
- improve commit message for patch 1
v3:
- patch 2: check for adap->getsda in readbytes()
- patch 2: align warning message level for info on missing getscl/getsda
- patch 3: improve description of attribute sda_is_output_only
Heiner Kallweit (3):
dt-bindings: i2c-gpio: Add property i2c-gpio,sda-output-only
i2c: algo: bit: allow getsda to be NULL
i2c: gpio: support write-only sda
.../devicetree/bindings/i2c/i2c-gpio.yaml | 4 ++++
drivers/i2c/algos/i2c-algo-bit.c | 16 ++++++++++++++--
drivers/i2c/busses/i2c-gpio.c | 14 +++++++++++---
include/linux/platform_data/i2c-gpio.h | 3 +++
4 files changed, 32 insertions(+), 5 deletions(-)
--
2.39.0
next reply other threads:[~2023-01-15 10:11 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-15 10:10 Heiner Kallweit [this message]
2023-01-15 10:12 ` [PATCH v3 1/3] dt-bindings: i2c-gpio: Add property i2c-gpio,sda-output-only Heiner Kallweit
2023-01-15 10:15 ` [PATCH v3 2/3] i2c: algo: bit: allow getsda to be NULL Heiner Kallweit
2023-01-16 7:17 ` Peter Rosin
2023-01-16 21:22 ` Heiner Kallweit
2023-01-15 10:18 ` [PATCH v3 3/3] i2c: gpio: support write-only sda Heiner Kallweit
2023-01-16 7:18 ` Peter Rosin
2023-01-16 21:59 ` Heiner Kallweit
2023-01-16 23:15 ` Peter Rosin
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=3a5545f3-f858-2c80-8bd4-2e0d401a1dc0@gmail.com \
--to=hkallweit1@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-i2c@vger.kernel.org \
--cc=robh+dt@kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).