From: Rob Herring <robh@kernel.org>
To: Alain Volmat <alain.volmat@foss.st.com>
Cc: Andi Shyti <andi.shyti@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Conor Dooley <conor+dt@kernel.org>,
Maxime Coquelin <mcoquelin.stm32@gmail.com>,
Alexandre Torgue <alexandre.torgue@foss.st.com>,
Pierre-Yves MORDRET <pierre-yves.mordret@foss.st.com>,
linux-i2c@vger.kernel.org, devicetree@vger.kernel.org,
linux-stm32@st-md-mailman.stormreply.com,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 3/7] dt-bindings: i2c: document st,stm32mp25-i2c compatible
Date: Wed, 6 Dec 2023 08:56:44 -0600 [thread overview]
Message-ID: <20231206145644.GA2133904-robh@kernel.org> (raw)
In-Reply-To: <20231129125920.1702497-4-alain.volmat@foss.st.com>
On Wed, Nov 29, 2023 at 01:59:12PM +0100, Alain Volmat wrote:
> Add a new compatible st,stm32mp25-i2c for the STM32MP25 series which
> has only one interrupt line for both events and errors and differs in
> term of handling of FastModePlus.
>
> Signed-off-by: Alain Volmat <alain.volmat@foss.st.com>
> ---
> .../devicetree/bindings/i2c/st,stm32-i2c.yaml | 49 +++++++++++++++----
> 1 file changed, 39 insertions(+), 10 deletions(-)
>
> diff --git a/Documentation/devicetree/bindings/i2c/st,stm32-i2c.yaml b/Documentation/devicetree/bindings/i2c/st,stm32-i2c.yaml
> index 94b75d9f66cd..6a69bb6de23e 100644
> --- a/Documentation/devicetree/bindings/i2c/st,stm32-i2c.yaml
> +++ b/Documentation/devicetree/bindings/i2c/st,stm32-i2c.yaml
> @@ -19,6 +19,7 @@ allOf:
> - st,stm32f7-i2c
> - st,stm32mp13-i2c
> - st,stm32mp15-i2c
> + - st,stm32mp25-i2c
> then:
> properties:
> i2c-scl-rising-time-ns:
> @@ -41,6 +42,43 @@ allOf:
> clock-frequency:
> enum: [100000, 400000]
>
> + - if:
> + properties:
> + compatible:
> + contains:
> + enum:
> + - st,stm32f4-i2c
> + - st,stm32f7-i2c
> + - st,stm32mp13-i2c
> + - st,stm32mp15-i2c
> + then:
> + properties:
> + interrupts:
> + items:
> + - description: interrupt ID for I2C event
> + - description: interrupt ID for I2C error
> +
> + interrupt-names:
> + items:
> + - const: event
> + - const: error
> +
> + - if:
> + properties:
> + compatible:
> + contains:
> + enum:
> + - st,stm32mp25-i2c
> + then:
> + properties:
> + interrupts:
> + items:
> + - description: common interrupt for events and errors
> +
> + interrupt-names:
> + items:
> + - const: event
> +
> properties:
> compatible:
> enum:
> @@ -48,20 +86,11 @@ properties:
> - st,stm32f7-i2c
> - st,stm32mp13-i2c
> - st,stm32mp15-i2c
> + - st,stm32mp25-i2c
>
> reg:
> maxItems: 1
>
> - interrupts:
> - items:
> - - description: interrupt ID for I2C event
> - - description: interrupt ID for I2C error
> -
> - interrupt-names:
> - items:
> - - const: event
> - - const: error
No this should remain. You are duplicating defining the names otherwise.
Add 'minItems: 1' here. Then the if/then schemas should just have
'maxItems: 1' or 'minItems: 2'.
Rob
next prev parent reply other threads:[~2023-12-06 14:56 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-29 12:59 [PATCH 0/7] i2c: stm32f7: enhancements and support for stm32mp25 Alain Volmat
2023-11-29 12:59 ` [PATCH 1/7] i2c: stm32f7: perform most of irq job in threaded handler Alain Volmat
2023-11-29 12:59 ` [PATCH 2/7] i2c: stm32f7: simplify status messages in case of errors Alain Volmat
2023-11-29 12:59 ` [PATCH 3/7] dt-bindings: i2c: document st,stm32mp25-i2c compatible Alain Volmat
2023-11-29 14:23 ` Conor Dooley
2023-12-06 14:56 ` Rob Herring [this message]
2023-11-29 12:59 ` [PATCH 4/7] i2c: stm32f7: add support for stm32mp25 soc Alain Volmat
2023-11-29 23:09 ` kernel test robot
2023-11-29 12:59 ` [PATCH 5/7] arm64: dts: st: add all 8 i2c nodes on stm32mp251 Alain Volmat
2023-12-05 13:53 ` kernel test robot
2023-11-29 12:59 ` [PATCH 6/7] arm64: dts: st: add i2c2/i2c8 pins for stm32mp25 Alain Volmat
2023-11-29 12:59 ` [PATCH 7/7] arm64: dts: st: add i2c2 / i2c8 properties on stm32mp257f-ev1 Alain Volmat
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=20231206145644.GA2133904-robh@kernel.org \
--to=robh@kernel.org \
--cc=alain.volmat@foss.st.com \
--cc=alexandre.torgue@foss.st.com \
--cc=andi.shyti@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-stm32@st-md-mailman.stormreply.com \
--cc=mcoquelin.stm32@gmail.com \
--cc=pierre-yves.mordret@foss.st.com \
/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