From: "Rob Herring (Arm)" <robh@kernel.org>
To: Antonio Borneo <antonio.borneo@foss.st.com>
Cc: linux-kernel@vger.kernel.org, linux-gpio@vger.kernel.org,
Christophe Roullier <christophe.roullier@foss.st.com>,
Maxime Coquelin <mcoquelin.stm32@gmail.com>,
Alexandre Torgue <alexandre.torgue@foss.st.com>,
Fabien Dessenne <fabien.dessenne@foss.st.com>,
linux-stm32@st-md-mailman.stormreply.com,
Conor Dooley <conor+dt@kernel.org>,
Linus Walleij <linus.walleij@linaro.org>,
Bartosz Golaszewski <brgl@bgdev.pl>,
linux-arm-kernel@lists.infradead.org,
Valentin Caron <valentin.caron@foss.st.com>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
devicetree@vger.kernel.org
Subject: Re: [PATCH v2 2/9] dt-bindings: pincfg-node: Add property "skew-delay-direction"
Date: Tue, 9 Sep 2025 21:08:39 -0500 [thread overview]
Message-ID: <175747011863.3632305.14159900534334210899.robh@kernel.org> (raw)
In-Reply-To: <20250905135547.934729-3-antonio.borneo@foss.st.com>
On Fri, 05 Sep 2025 15:55:40 +0200, Antonio Borneo wrote:
> Add the property "skew-delay-direction" to specify on which pin's
> direction (either input, output or both) the value of the generic
> property 'skew-delay' applies.
> For backward compatibility, 'skew-delay' applies on both input and
> output directions when the new property is not present or has
> value '0'.
>
> Signed-off-by: Antonio Borneo <antonio.borneo@foss.st.com>
> ---
> .../devicetree/bindings/pinctrl/pincfg-node.yaml | 13 ++++++++++++-
> 1 file changed, 12 insertions(+), 1 deletion(-)
>
Acked-by: Rob Herring (Arm) <robh@kernel.org>
next prev parent reply other threads:[~2025-09-10 2:08 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-05 13:55 [PATCH v2 0/9] pinctrl: stm32: Support I/O synchronization Antonio Borneo
2025-09-05 13:55 ` [PATCH v2 1/9] pinctrl: pinconf-generic: Add property "skew-delay-direction" Antonio Borneo
2025-09-05 13:55 ` [PATCH v2 2/9] dt-bindings: pincfg-node: " Antonio Borneo
2025-09-10 2:08 ` Rob Herring (Arm) [this message]
2025-09-30 12:23 ` Linus Walleij
2025-10-01 14:36 ` Antonio Borneo
2025-09-05 13:55 ` [PATCH v2 3/9] pinctrl: stm32: Rework stm32_pconf_parse_conf() Antonio Borneo
2025-09-05 13:55 ` [PATCH v2 4/9] pinctrl: stm32: Simplify handling of backup pin status Antonio Borneo
2025-09-05 13:55 ` [PATCH v2 5/9] pinctrl: stm32: Drop useless spinlock save and restore Antonio Borneo
2025-09-05 13:55 ` [PATCH v2 6/9] pinctrl: stm32: Avoid keeping a bool value in a u32 variable Antonio Borneo
2025-09-05 13:55 ` [PATCH v2 7/9] pinctrl: stm32: Support I/O synchronization parameters Antonio Borneo
2025-09-05 13:55 ` [PATCH v2 8/9] dt-bindings: " Antonio Borneo
2025-09-10 2:10 ` Rob Herring (Arm)
2025-09-05 13:55 ` [PATCH v2 9/9] arm64: dts: st: Add I/O sync to eth2 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=175747011863.3632305.14159900534334210899.robh@kernel.org \
--to=robh@kernel.org \
--cc=alexandre.torgue@foss.st.com \
--cc=antonio.borneo@foss.st.com \
--cc=brgl@bgdev.pl \
--cc=christophe.roullier@foss.st.com \
--cc=conor+dt@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=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
all inboxes | Powered by JetHome®