From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: "Svyatoslav Ryhel" <clamor95@gmail.com>,
"Andi Shyti" <andi.shyti@kernel.org>,
"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>
Cc: linux-i2c@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 1/2] dt-bindings: i2c: add binding for i2c-hotplug-gpio
Date: Mon, 19 Jun 2023 17:53:24 +0200 [thread overview]
Message-ID: <32b0e664-9381-19c4-de9d-9466a00b4f50@linaro.org> (raw)
In-Reply-To: <20230619153732.46258-2-clamor95@gmail.com>
On 19/06/2023 17:37, Svyatoslav Ryhel wrote:
> Document device tree schema which describes hot-pluggable via GPIO
> i2c bus.
>
> Signed-off-by: Svyatoslav Ryhel <clamor95@gmail.com>
1. Don't send new version before discussion finishes. v2 after one hour
is definitely not enough. Usually one day.
2. Test the patches before sending...
What changed here?
> ---
> .../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
"Driver" so SW? Bindings are for hardware, not for drivers.
> + are hot-pluggable and their presence is indicated by GPIO line.
> +
> +properties:
> + compatible:
> + items:
Drop items.
> + - const: i2c-hotplug-gpio
> +
> + '#address-cells':
> + const: 1
> +
> + '#size-cells':
> + const: 0
> +
> + interrupts-extended:
I missed last time - this is wrong. Just interrupts.
> + minItems: 1
maxItems
> +
> + detect-gpios:
> + maxItems: 1
> +
> + i2c-parent:
> + maxItems: 1
Discussion from v1 stands - this is a software construct, not a real device.
> +
> +required:
> + - compatible
> + - '#address-cells'
> + - '#size-cells'
> + - interrupts-extended
> + - detect-gpios
> + - i2c-parent
> +
> +unevaluatedProperties: false
instead additionalProperties: false
Anyway, don't send v3, before the discussion about the entire concept
finishes. You create a software/virtual device, instead of adding these
properties to bindings for a real hardware.
> +
> +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>;
I don't think you can have both interrupt and GPIO on the same line.
> +
> + i2c-parent = <&gen2_i2c>;
> + };
> +...
Best regards,
Krzysztof
next prev parent reply other threads:[~2023-06-19 15:53 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 [this message]
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
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=32b0e664-9381-19c4-de9d-9466a00b4f50@linaro.org \
--to=krzysztof.kozlowski@linaro.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+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).