Devicetree
 help / color / mirror / Atom feed
From: Thierry Reding <thierry.reding@kernel.org>
To: Krzysztof Kozlowski <krzk@kernel.org>
Cc: Prathamesh Shete <pshete@nvidia.com>,
	linusw@kernel.org,  robh@kernel.org, krzk+dt@kernel.org,
	conor+dt@kernel.org, jonathanh@nvidia.com,
	 linux-gpio@vger.kernel.org, devicetree@vger.kernel.org,
	linux-tegra@vger.kernel.org,  linux-kernel@vger.kernel.org
Subject: Re: [RESEND V2 1/2] dt-bindings: pinctrl: tegra264: fix DAP2 DIN/DOUT pin names
Date: Wed, 5 Aug 2026 09:27:15 +0200	[thread overview]
Message-ID: <anLiwXh0JGH_bvKv@orome> (raw)
In-Reply-To: <20260804-energetic-gracious-python-a6fe54@quoll>

[-- Attachment #1: Type: text/plain, Size: 1143 bytes --]

On Tue, Aug 04, 2026 at 09:37:14AM +0200, Krzysztof Kozlowski wrote:
> On Mon, Jul 27, 2026 at 02:11:20PM +0000, Prathamesh Shete wrote:
> > The DAP2_DIN and DAP2_DOUT pins were listed with swapped ball suffixes:
> > DAP2_DIN as PV7 and DAP2_DOUT as PW0. On silicon DAP2_DIN is on ball PW0
> > and DAP2_DOUT is on ball PV7. Correct the pin and drive group names to
> > dap2_din_pw0 and dap2_dout_pv7.
> > 
> > Fixes: 30a9d5162f25 ("dt-bindings: pinctrl: Document Tegra264 pin controllers")
> > Signed-off-by: Prathamesh Shete <pshete@nvidia.com>
> 
> This will break the users and only for fixing naming style? Are you sure
> it is worth beraking ABI?

This isn't just fixing the naming style, it's fixing the name of the
pins as they are referred to in a number of different places. With the
wrong ball suffix people might easily be confused as to what pin they
should be using.

So yes, I'd consider this a bug fix and worth an ABI break. The ABI
break is theoretical, too. This pin is currently not listed in any
upstream DTS files and all of the downstream ones I've seen use the
corrected suffix already.

Thierry

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2026-08-05  7:27 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-27 14:11 [RESEND V2 1/2] dt-bindings: pinctrl: tegra264: fix DAP2 DIN/DOUT pin names Prathamesh Shete
2026-07-27 14:11 ` [RESEND V2 2/2] pinctrl: tegra264: fix DAP2 DIN/DOUT pin assignment Prathamesh Shete
2026-07-30  9:18   ` Jon Hunter
2026-07-31  8:06   ` Thierry Reding
2026-07-27 14:20 ` [RESEND V2 1/2] dt-bindings: pinctrl: tegra264: fix DAP2 DIN/DOUT pin names sashiko-bot
2026-07-30  9:17 ` Jon Hunter
2026-07-31  8:06 ` Thierry Reding
2026-08-04  7:37 ` Krzysztof Kozlowski
2026-08-05  7:27   ` Thierry Reding [this message]
2026-08-05  7:45 ` Krzysztof Kozlowski

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=anLiwXh0JGH_bvKv@orome \
    --to=thierry.reding@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=jonathanh@nvidia.com \
    --cc=krzk+dt@kernel.org \
    --cc=krzk@kernel.org \
    --cc=linusw@kernel.org \
    --cc=linux-gpio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-tegra@vger.kernel.org \
    --cc=pshete@nvidia.com \
    --cc=robh@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