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>,
Wolfram Sang <wsa+renesas@sang-engineering.com>
Cc: "linux-i2c@vger.kernel.org" <linux-i2c@vger.kernel.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>
Subject: [PATCH 0/3] i2c: gpio: support write-only sda
Date: Fri, 15 Apr 2022 15:31:40 +0200 [thread overview]
Message-ID: <bc229e73-52aa-9f5d-c6fd-e84b64a589ba@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.
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 | 2 ++
4 files changed, 30 insertions(+), 6 deletions(-)
--
2.35.3
next reply other threads:[~2022-04-15 13:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-15 13:31 Heiner Kallweit [this message]
2022-04-15 13:32 ` [PATCH 1/3] dt-bindings: i2c-gpio: Add property i2c-gpio,sda-output-only Heiner Kallweit
2022-04-26 18:56 ` Rob Herring
2022-04-15 13:33 ` [PATCH 2/3] i2c: algo: bit: allow getsda to be NULL Heiner Kallweit
2022-04-15 13:35 ` [PATCH 3/3] i2c: gpio: support write-only sda Heiner Kallweit
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=bc229e73-52aa-9f5d-c6fd-e84b64a589ba@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+renesas@sang-engineering.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 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.