From: Antonio Borneo <antonio.borneo@foss.st.com>
To: Conor Dooley <conor@kernel.org>
Cc: Linus Walleij <linus.walleij@linaro.org>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Maxime Coquelin <mcoquelin.stm32@gmail.com>,
Alexandre Torgue <alexandre.torgue@foss.st.com>,
Bartosz Golaszewski <brgl@bgdev.pl>, <linux-gpio@vger.kernel.org>,
<devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<linux-stm32@st-md-mailman.stormreply.com>,
<linux-arm-kernel@lists.infradead.org>,
Christophe Roullier <christophe.roullier@foss.st.com>,
Fabien Dessenne <fabien.dessenne@foss.st.com>,
Valentin Caron <valentin.caron@foss.st.com>
Subject: Re: [PATCH v3 09/10] dt-bindings: pinctrl: stm32: Support I/O synchronization parameters
Date: Wed, 15 Oct 2025 14:56:56 +0200 [thread overview]
Message-ID: <b4eca95eaa0e6f27fc07479d5eab2131d20eb270.camel@foss.st.com> (raw)
In-Reply-To: <20251014-affection-voltage-8b1764273a06@spud>
On Tue, 2025-10-14 at 19:10 +0100, Conor Dooley wrote:
> On Tue, Oct 14, 2025 at 04:04:50PM +0200, Antonio Borneo wrote:
> > Document the support of the I/O synchronization parameters:
> > - skew-delay-input;
> > - skew-delay-output;
> > - st,io-sync.
> >
> > Forbid 'skew-delay-input' and 'skew-delay-output' to be both
> > present on the same pin.
> > Allow the new properties only with compatibles that support them.
> > Add an example that uses the new properties.
> >
> > Co-developed-by: Fabien Dessenne <fabien.dessenne@foss.st.com>
> > Signed-off-by: Fabien Dessenne <fabien.dessenne@foss.st.com>
> > Signed-off-by: Antonio Borneo <antonio.borneo@foss.st.com>
> > ---
> > .../bindings/pinctrl/st,stm32-pinctrl.yaml | 98 +++++++++++++++++++
> > 1 file changed, 98 insertions(+)
> >
> > diff --git a/Documentation/devicetree/bindings/pinctrl/st,stm32-pinctrl.yaml b/Documentation/devicetree/bindings/pinctrl/st,stm32-pinctrl.yaml
> > index 2df141ed7222d..0010762127c05 100644
> > --- a/Documentation/devicetree/bindings/pinctrl/st,stm32-pinctrl.yaml
> > +++ b/Documentation/devicetree/bindings/pinctrl/st,stm32-pinctrl.yaml
> > @@ -220,12 +220,89 @@ patternProperties:
> > minimum: 0
> > maximum: 3
> >
> > + skew-delay-input:
> > + description: |
> > + IO synchronization skew rate applied to the input path
> > + 0: No delay
> > + 1: Delay 0.30 ns
> > + 2: Delay 0.50 ns
> > + 3: Delay 0.75 ns
> > + 4: Delay 1.00 ns
> > + 5: Delay 1.25 ns
> > + 6: Delay 1.50 ns
> > + 7: Delay 1.75 ns
> > + 8: Delay 2.00 ns
> > + 9: Delay 2.25 ns
> > + 10: Delay 2.50 ns
> > + 11: Delay 2.75 ns
> > + 12: Delay 3.00 ns
> > + 13: Delay 3.25 ns
> > + minimum: 0
> > + maximum: 13
> > +
> > + skew-delay-output:
> > + description: |
> > + IO synchronization latch delay applied to the output path
> > + 0: No delay
> > + 1: Delay 0.30 ns
> > + 2: Delay 0.50 ns
> > + 3: Delay 0.75 ns
> > + 4: Delay 1.00 ns
> > + 5: Delay 1.25 ns
> > + 6: Delay 1.50 ns
> > + 7: Delay 1.75 ns
> > + 8: Delay 2.00 ns
> > + 9: Delay 2.25 ns
> > + 10: Delay 2.50 ns
> > + 11: Delay 2.75 ns
> > + 12: Delay 3.00 ns
> > + 13: Delay 3.25 ns
> > + minimum: 0
> > + maximum: 13
>
> Same comments here as on the earlier patch. I would like to see times
> used natively.
Yes, I replied to the earlier patch.
> pw-bot: changes-requested
>
> > +
> > + st,io-sync:
> > + description: |
> > + IO synchronization through re-sampling or inversion
> > + 0: data or clock GPIO pass-through
> > + 1: clock GPIO inverted
> > + 2: data GPIO re-sampled on clock rising edge
> > + 3: data GPIO re-sampled on clock falling edge
> > + 4: data GPIO re-sampled on both clock edges
> > + $ref: /schemas/types.yaml#/definitions/uint32
> > + enum: [0, 1, 2, 3, 4]
>
> I really don't like this kinds of properties that lead to "random"
> numbers in devicetree. I'd much rather see a string list here.
Agree!
I just need to figure out some reasonably short but still meaningful
string for them.
Thanks for the review!
Antonio
>
> > +
> > required:
> > - pinmux
> >
> > + # Not allowed both skew-delay-input and skew-delay-output
> > + if:
> > + required:
> > + - skew-delay-input
> > + then:
> > + properties:
> > + skew-delay-output: false
> > +
> > allOf:
> > - $ref: pinctrl.yaml#
> >
> > + - if:
> > + not:
> > + properties:
> > + compatible:
> > + contains:
> > + enum:
> > + - st,stm32mp257-pinctrl
> > + - st,stm32mp257-z-pinctrl
> > + then:
> > + patternProperties:
> > + '-[0-9]*$':
> > + patternProperties:
> > + '^pins':
> > + properties:
> > + skew-delay-input: false
> > + skew-delay-output: false
> > + st,io-sync: false
> > +
> > required:
> > - compatible
> > - '#address-cells'
> > @@ -306,4 +383,25 @@ examples:
> > pinctrl-names = "default";
> > };
> >
> > + - |
> > + #include <dt-bindings/pinctrl/stm32-pinfunc.h>
> > + //Example 4 skew-delay and st,io-sync
> > + pinctrl: pinctrl@44240000 {
> > + compatible = "st,stm32mp257-pinctrl";
> > + #address-cells = <1>;
> > + #size-cells = <1>;
> > + ranges = <0 0x44240000 0xa0400>;
> > +
> > + eth3_rgmii_pins_a: eth3-rgmii-0 {
> > + pins1 {
> > + pinmux = <STM32_PINMUX('A', 6, AF14)>;
> > + st,io-sync = <4>;
> > + };
> > + pins2 {
> > + pinmux = <STM32_PINMUX('H', 2, AF14)>;
> > + skew-delay-output = <2>;
> > + };
> > + };
> > + };
> > +
> > ...
> > --
> > 2.34.1
> >
next prev parent reply other threads:[~2025-10-15 12:57 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-14 14:04 [PATCH v3 00/10] pinctrl: stm32: Support I/O synchronization Antonio Borneo
2025-10-14 14:04 ` [PATCH v3 01/10] pinctrl: pinconf-generic: Add properties 'skew-delay-{in,out}put' Antonio Borneo
2025-10-14 14:04 ` [PATCH v3 02/10] dt-bindings: pincfg-node: " Antonio Borneo
2025-10-14 18:04 ` Conor Dooley
2025-10-14 19:33 ` Linus Walleij
2025-10-14 19:39 ` Conor Dooley
2025-10-15 12:52 ` Antonio Borneo
2025-10-16 22:34 ` Linus Walleij
2025-10-15 16:37 ` Andrew Lunn
2025-10-16 22:41 ` Linus Walleij
2025-10-14 14:04 ` [PATCH v3 03/10] pinctrl: stm32: Rework stm32_pconf_parse_conf() Antonio Borneo
2025-10-14 14:04 ` [PATCH v3 04/10] pinctrl: stm32: Simplify handling of backup pin status Antonio Borneo
2025-10-14 14:04 ` [PATCH v3 05/10] pinctrl: stm32: Drop useless spinlock save and restore Antonio Borneo
2025-10-14 14:04 ` [PATCH v3 06/10] pinctrl: stm32: Avoid keeping a bool value in a u32 variable Antonio Borneo
2025-10-14 14:04 ` [PATCH v3 07/10] pinctrl: stm32: Support I/O synchronization parameters Antonio Borneo
2025-10-14 14:04 ` [PATCH v3 08/10] dt-bindings: pinctrl: stm32: Use properties from pincfg-node.yaml Antonio Borneo
2025-10-14 18:05 ` Conor Dooley
2025-10-14 14:04 ` [PATCH v3 09/10] dt-bindings: pinctrl: stm32: Support I/O synchronization parameters Antonio Borneo
2025-10-14 18:10 ` Conor Dooley
2025-10-15 12:56 ` Antonio Borneo [this message]
2025-10-15 14:35 ` Conor Dooley
2025-10-20 15:09 ` Antonio Borneo
2025-10-20 22:08 ` Linus Walleij
2025-10-21 11:49 ` Antonio Borneo
2025-10-21 12:26 ` Linus Walleij
2025-10-14 14:04 ` [PATCH v3 10/10] arm64: dts: st: Add I/O sync to eth pinctrl in stm32mp25-pinctrl.dtsi Antonio Borneo
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=b4eca95eaa0e6f27fc07479d5eab2131d20eb270.camel@foss.st.com \
--to=antonio.borneo@foss.st.com \
--cc=alexandre.torgue@foss.st.com \
--cc=brgl@bgdev.pl \
--cc=christophe.roullier@foss.st.com \
--cc=conor+dt@kernel.org \
--cc=conor@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=fabien.dessenne@foss.st.com \
--cc=krzk+dt@kernel.org \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-stm32@st-md-mailman.stormreply.com \
--cc=mcoquelin.stm32@gmail.com \
--cc=robh@kernel.org \
--cc=valentin.caron@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;
as well as URLs for NNTP newsgroup(s).