[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20251015-headstand-impulse-95aa736e7633@spud>
Date: Wed, 15 Oct 2025 15:35:53 +0100
From: Conor Dooley <conor@...nel.org>
To: Antonio Borneo <antonio.borneo@...s.st.com>
Cc: Linus Walleij <linus.walleij@...aro.org>, Rob Herring <robh@...nel.org>,
Krzysztof Kozlowski <krzk+dt@...nel.org>,
Conor Dooley <conor+dt@...nel.org>,
Maxime Coquelin <mcoquelin.stm32@...il.com>,
Alexandre Torgue <alexandre.torgue@...s.st.com>,
Bartosz Golaszewski <brgl@...ev.pl>, linux-gpio@...r.kernel.org,
devicetree@...r.kernel.org, linux-kernel@...r.kernel.org,
linux-stm32@...md-mailman.stormreply.com,
linux-arm-kernel@...ts.infradead.org,
Christophe Roullier <christophe.roullier@...s.st.com>,
Fabien Dessenne <fabien.dessenne@...s.st.com>,
Valentin Caron <valentin.caron@...s.st.com>
Subject: Re: [PATCH v3 09/10] dt-bindings: pinctrl: stm32: Support I/O
synchronization parameters
On Wed, Oct 15, 2025 at 02:56:56PM +0200, Antonio Borneo wrote:
> 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:
> >
> > > +
> > > + 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.
pass-through
inverted
rising-edge
falling-edge
both-edges
perhaps?
Download attachment "signature.asc" of type "application/pgp-signature" (229 bytes)
Powered by blists - more mailing lists