From: Francesco Dolcini <francesco@dolcini.it>
To: Nishanth Menon <nm@ti.com>, 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>
Cc: Francesco Dolcini <francesco.dolcini@toradex.com>,
linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: [PATCH v1 0/2] arm64: dts: ti: k3-am62-verdin-[ivy|zinnia]: fix main_gpio0/main_gpio1 line names size
Date: Tue, 22 Sep 2026 17:25:47 +0200 [thread overview]
Message-ID: <20260922152551.270845-1-francesco@dolcini.it> (raw)
From: Francesco Dolcini <francesco.dolcini@toradex.com>
zinnia and ivy redefines gpio-line-names for main_gpio0/main_gpio1, sized
87/88 entries instead of the SoC's actual 92/52 ti,ngpio. Resize both
arrays to match, keeping every existing label at its original index.
missed from previous https://lore.kernel.org/all/20260914190943.50843-1-francesco@dolcini.it/
Francesco Dolcini (2):
arm64: dts: ti: k3-am62-verdin-ivy: fix main_gpio0/main_gpio1 line
names size
arm64: dts: ti: k3-am62-verdin-zinnia: fix main_gpio0/main_gpio1 line
names size
.../arm64/boot/dts/ti/k3-am62-verdin-ivy.dtsi | 41 +++----------------
.../boot/dts/ti/k3-am62-verdin-zinnia.dtsi | 41 +++----------------
2 files changed, 10 insertions(+), 72 deletions(-)
--
2.47.3
next reply other threads:[~2026-09-22 15:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-22 15:25 Francesco Dolcini [this message]
2026-09-22 15:25 ` [PATCH v1 1/2] arm64: dts: ti: k3-am62-verdin-ivy: fix main_gpio0/main_gpio1 line names size Francesco Dolcini
2026-09-22 15:25 ` [PATCH v1 2/2] arm64: dts: ti: k3-am62-verdin-zinnia: " Francesco Dolcini
2026-09-28 17:21 ` [PATCH v1 0/2] arm64: dts: ti: k3-am62-verdin-[ivy|zinnia]: " Nishanth Menon
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=20260922152551.270845-1-francesco@dolcini.it \
--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