From: Francesco Dolcini <francesco@dolcini.it>
To: Nishanth Menon <nm@ti.com>
Cc: Vignesh Raghavendra <vigneshr@ti.com>,
Tero Kristo <kristo@kernel.org>, Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Francesco Dolcini <francesco@dolcini.it>,
Francesco Dolcini <francesco.dolcini@toradex.com>,
linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] arm64: dts: ti: k3-am62-verdin: fix main_gpio0/main_gpio1 line names size
Date: Tue, 22 Sep 2026 16:46:28 +0200 [thread overview]
Message-ID: <20260922144628.GA261268@francesco-nb> (raw)
In-Reply-To: <179008726793.4044824.6786355019611253673.b4-ty@b4>
Hello Nishanth,
On Tue, Sep 22, 2026 at 09:29:48AM -0500, Nishanth Menon wrote:
> On Mon, 14 Sep 2026 21:09:42 +0200, Francesco Dolcini wrote:
> > gpio-line-names sized main_gpio0/main_gpio1 for 87/88 lines, the SoC's
> > ti,ngpio values before they were corrected to 92/52 in commit
> > 28c8f2189d80 ("arm64: dts: ti: k3-am62-main: Fix GPIO numbers in DT"),
> > four months before this file was written. Resize both arrays to match,
> > keeping every existing label at its original index.
> >
> >
> > [...]
>
> I have applied the following to branch ti-k3-dts-next on [1].
>
> I have assumed you'd not want this fix for ivy/zinnia which redefines
> the gpio-line-names. Let me know if that is not the case or if additional
> fixes are needed.
I missed them, I'll send 2 more patches to fix it. Thanks for the
head-up, appreciated.
Francesco
prev parent reply other threads:[~2026-09-22 14:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-14 19:09 Francesco Dolcini
2026-09-22 14:29 ` Nishanth Menon
2026-09-22 14:46 ` Francesco Dolcini [this message]
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=20260922144628.GA261268@francesco-nb \
--to=francesco@dolcini.it \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=francesco.dolcini@toradex.com \
--cc=kristo@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nm@ti.com \
--cc=robh@kernel.org \
--cc=vigneshr@ti.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®