From: Rob Herring <robh@kernel.org>
To: Svyatoslav Ryhel <clamor95@gmail.com>
Cc: "Andi Shyti" <andi.shyti@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 v3 1/2] dt-bindings: i2c: add binding for i2c-hotplug-gpio
Date: Fri, 11 Aug 2023 11:37:52 -0600 [thread overview]
Message-ID: <20230811173752.GA3639776-robh@kernel.org> (raw)
In-Reply-To: <20230729160857.6332-2-clamor95@gmail.com>
On Sat, Jul 29, 2023 at 07:08:56PM +0300, Svyatoslav Ryhel wrote:
> Document device tree schema which describes hot-pluggable via GPIO
> i2c bus.
What's that? 'hot-pluggable via GPIO i2c bus' is not coherent.
>
> Signed-off-by: Svyatoslav Ryhel <clamor95@gmail.com>
> ---
> .../bindings/i2c/i2c-hotplug-gpio.yaml | 65 +++++++++++++++++++
> 1 file changed, 65 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/i2c/i2c-hotplug-gpio.yaml
>
> diff --git a/Documentation/devicetree/bindings/i2c/i2c-hotplug-gpio.yaml b/Documentation/devicetree/bindings/i2c/i2c-hotplug-gpio.yaml
> new file mode 100644
> index 000000000000..21f2b74ca6c1
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/i2c/i2c-hotplug-gpio.yaml
> @@ -0,0 +1,65 @@
> +# SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause)
> +%YAML 1.2
> +---
> +$id: http://devicetree.org/schemas/i2c/i2c-hotplug-gpio.yaml#
> +$schema: http://devicetree.org/meta-schemas/core.yaml#
> +
> +title: GPIO detected hot-plugged I2C bus
> +
> +maintainers:
> + - Michał Mirosław <mirq-linux@rere.qmqm.pl>
> +
> +description:
> + Driver for hot-plugged I2C busses, where some devices on a bus
Bindings are for h/w, not a driver.
> + are hot-pluggable and their presence is indicated by GPIO line.
> +
> +properties:
> + compatible:
> + items:
> + - const: i2c-hotplug-gpio
> +
> + '#address-cells':
> + const: 1
> +
> + '#size-cells':
> + const: 0
What are these for? You don't have any child nodes.
> +
> + interrupts-extended:
> + minItems: 1
> +
> + detect-gpios:
> + maxItems: 1
> +
> + i2c-parent:
> + maxItems: 1
> +
> +required:
> + - compatible
> + - '#address-cells'
> + - '#size-cells'
> + - interrupts-extended
> + - detect-gpios
> + - i2c-parent
> +
> +unevaluatedProperties: false
> +
> +examples:
> + - |
> + /*
> + * Asus Transformers use I2C hotplug for attachable dock keyboard
> + */
> + #include <dt-bindings/gpio/gpio.h>
> + #include <dt-bindings/interrupt-controller/irq.h>
> +
> + i2c-dock {
> + compatible = "i2c-hotplug-gpio";
> +
> + #address-cells = <1>;
> + #size-cells = <0>;
> +
> + interrupts-extended = <&gpio 164 IRQ_TYPE_EDGE_BOTH>;
> + detect-gpios = <&gpio 164 GPIO_ACTIVE_LOW>;
Looks like the same signal. You should only need one of them. Probably
'detect-gpios' as I guess you need to read the state of the line.
> +
> + i2c-parent = <&gen2_i2c>;
Couldn't you just add 'detect-gpios' to the existing bus node? It's
really part of that bus and there's not a separate bus. That would be a
lot simpler. I suppose you want to instantiate a driver, but that's not
DT's problem.
Rob
next prev parent reply other threads:[~2023-08-11 17:37 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 [this message]
2023-08-12 21:46 ` Michał Mirosław
2023-08-15 20:00 ` Wolfram Sang
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=20230811173752.GA3639776-robh@kernel.org \
--to=robh@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=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.