From: Svyatoslav Ryhel <clamor95@gmail.com>
To: Andi Shyti <andi.shyti@kernel.org>
Cc: "Rob Herring" <robh+dt@kernel.org>,
"Krzysztof Kozlowski" <krzysztof.kozlowski+dt@linaro.org>,
"Conor Dooley" <conor+dt@kernel.org>,
"Wolfram Sang" <wsa@kernel.org>,
"Michał Mirosław" <mirq-linux@rere.qmqm.pl>,
linux-i2c@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 2/2] i2c: Add GPIO-based hotplug gate
Date: Wed, 21 Jun 2023 14:00:48 +0300 [thread overview]
Message-ID: <CAPVz0n2E5gqCS3mRRjnUM0K__9An_fDcJG_7w0EgR0JG8Dtp=w@mail.gmail.com> (raw)
In-Reply-To: <20230621103219.o2u33nsok7zngikf@intel.intel>
ср, 21 черв. 2023 р. о 13:32 Andi Shyti <andi.shyti@kernel.org> пише:
>
> Hi,
>
> On Mon, Jun 19, 2023 at 06:37:32PM +0300, Svyatoslav Ryhel wrote:
> > From: Michał Mirosław <mirq-linux@rere.qmqm.pl>
> >
> > Implement driver for hot-plugged I2C busses, where some devices on
> > a bus are hot-pluggable and their presence is indicated by GPIO line.
> >
> > Co-developed-by: Ion Agorria <ion@agorria.com>
> > Signed-off-by: Ion Agorria <ion@agorria.com>
> > Signed-off-by: Michał Mirosław <mirq-linux@rere.qmqm.pl>
> > Signed-off-by: Svyatoslav Ryhel <clamor95@gmail.com>
> > ---
> > drivers/i2c/Kconfig | 11 ++
> > drivers/i2c/Makefile | 1 +
> > drivers/i2c/i2c-hotplug-gpio.c | 266 +++++++++++++++++++++++++++++++++
> > 3 files changed, 278 insertions(+)
> > create mode 100644 drivers/i2c/i2c-hotplug-gpio.c
>
> without going through the code I am missing the big picture here.
>
> What is this actually doing?
Basically it duplicates the parent i2c bus once detection GPIO triggers
and probes all hot-pluggable devices which are connected to it. Once
GPIO triggers detach signal all hot-pluggable devices are unprobed and
bus removed.
> Is this a new bus driver support?
Most likely not.
> Is this a feature to existing drivers?
Yes, it is more like i2c mux
> Is the GPIO an irq line for signalling hoplugging and can be used by
> any driver or just this one?
>
It can be shared if necessary but usually all hot-pluggable devices
are gathered in one container and are plugged simultaneously.
> Without further discussing technicalities, can you please explain
> better and more in detail what is the scope of this patch, why
> there is a need for such a patch, how this new driver/feature
> has been implemented and finally how it can be used.
This patch is a predecessor of a possible larger patchset which
should bring support for a asus-ec, a i2c mfd device programmed by
Asus for their Transformers tablet line.
This is Michał Mirosław, original author quote about this driver:
"The Transformers have a connector that's used for USB, charging or
for attaching a keyboard (called a dock; it also has a battery and
a touchpad). This connector probably (I don't have the means to verify
that) has an I2C bus lines and a "detect" line (pulled low on the dock
side) among the pins. I guess there is either no additional chip or
a transparent bridge/buffer chip, but nothing that could be controlled
by software. For DT this setup could be modelled like an I2C gate or
2-port mux with enable joining two I2C busses (one "closer" to the
CPU -- parent)."
Similar approach is used in Microsoft Surface RT for attachable
Type Cover.
> This would help a lot so that I know already beforehand what I am
> going to read without figuring it out.
>
> Thanks,
> Andi
>
> PS Please notice that my set of questions is even longer than
> your commit log :)
next prev parent reply other threads:[~2023-06-21 11:01 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-19 15:37 [PATCH v2 0/2] GPIO-based hotplug i2c bus Svyatoslav Ryhel
2023-06-19 15:37 ` [PATCH v2 1/2] dt-bindings: i2c: add binding for i2c-hotplug-gpio Svyatoslav Ryhel
2023-06-19 15:53 ` Krzysztof Kozlowski
2023-06-19 23:19 ` Michał Mirosław
2023-06-19 15:37 ` [PATCH v2 2/2] i2c: Add GPIO-based hotplug gate Svyatoslav Ryhel
2023-06-21 10:32 ` Andi Shyti
2023-06-21 11:00 ` Svyatoslav Ryhel [this message]
2023-06-19 15:49 ` [PATCH v2 0/2] GPIO-based hotplug i2c bus Krzysztof Kozlowski
2023-06-19 15:52 ` Svyatoslav Ryhel
2023-06-19 15:54 ` Krzysztof Kozlowski
2023-06-21 10:11 ` 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='CAPVz0n2E5gqCS3mRRjnUM0K__9An_fDcJG_7w0EgR0JG8Dtp=w@mail.gmail.com' \
--to=clamor95@gmail.com \
--cc=andi.shyti@kernel.org \
--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+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).