From: Wolfram Sang <wsa@kernel.org>
To: "Michał Mirosław" <mirq-linux@rere.qmqm.pl>
Cc: Rob Herring <robh@kernel.org>,
Svyatoslav Ryhel <clamor95@gmail.com>,
Andi Shyti <andi.shyti@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Conor Dooley <conor+dt@kernel.org>,
linux-i2c@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 1/2] dt-bindings: i2c: add binding for i2c-hotplug-gpio
Date: Tue, 15 Aug 2023 22:00:55 +0200 [thread overview]
Message-ID: <ZNvZd2sOK+WMN4XN@shikoro> (raw)
In-Reply-To: <ZNf9vKJHc/FFlkY4@qmqm.qmqm.pl>
[-- Attachment #1: Type: text/plain, Size: 679 bytes --]
> Not a driver but a group of devices (possibly discovered dynamically)
> behind a passive gate (like e.g. PCA9517A with EN tied to a connector pin).
> It's not much different to a I2C gate or mux with a single child bus
> (i2c-mux-gpio that has only a single child).
I agree. To prevent the the bus from spikes when connecting /
disconnecting something like PCA9517A should be in place. And this one
can be considered a 1:1 mux. Just with the exception that Linux cannot
control the gate, but can only react to changes to the enable pin.
Can't we have a driver for the PCA9517 which gets interrupts when the
enable pin changes and then adds / removes the child i2c adapter?
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2023-08-15 20:01 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-29 16:08 [PATCH v3 0/2] GPIO-based hotplug i2c bus Svyatoslav Ryhel
2023-07-29 16:08 ` [PATCH v3 1/2] dt-bindings: i2c: add binding for i2c-hotplug-gpio Svyatoslav Ryhel
2023-08-05 19:23 ` Krzysztof Kozlowski
2023-08-11 17:37 ` Rob Herring
2023-08-12 21:46 ` Michał Mirosław
2023-08-15 20:00 ` Wolfram Sang [this message]
2023-07-29 16:08 ` [PATCH v3 2/2] i2c: Add GPIO-based hotplug gate Svyatoslav Ryhel
2023-07-30 20:25 ` Andi Shyti
2023-07-30 22:11 ` Michał Mirosław
2023-07-31 23:01 ` Michał Mirosław
2023-08-04 23:45 ` Andi Shyti
2023-08-10 22:55 ` Michał Mirosław
2023-07-30 20:30 ` Krzysztof Kozlowski
2023-07-30 21:55 ` Michał Mirosław
2023-07-31 6:58 ` Krzysztof Kozlowski
2023-07-31 8:49 ` Michał Mirosław
2023-07-31 12:59 ` Krzysztof Kozlowski
2023-07-31 22:50 ` Michał Mirosław
2023-08-05 19:17 ` Krzysztof Kozlowski
2023-08-10 21:52 ` Michał Mirosław
2023-08-15 5:20 ` Krzysztof Kozlowski
2023-07-30 17:49 ` [PATCH v3 0/2] GPIO-based hotplug i2c bus Andi Shyti
2023-07-30 18:21 ` Svyatoslav Ryhel
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=ZNvZd2sOK+WMN4XN@shikoro \
--to=wsa@kernel.org \
--cc=andi.shyti@kernel.org \
--cc=clamor95@gmail.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mirq-linux@rere.qmqm.pl \
--cc=robh@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.