From: David Lechner <dlechner@baylibre.com>
To: Vignesh Raghavendra <vigneshr@ti.com>, Nishanth Menon <nm@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: Robert Nelson <robertcnelson@gmail.com>,
linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/2] arm64: dts: ti: k3-am67a-beagley-ai: GPIO improvements
Date: Wed, 29 Jul 2026 08:57:19 -0500 [thread overview]
Message-ID: <02b159ad-42d3-4d1b-a73e-13612d9f2845@baylibre.com> (raw)
In-Reply-To: <7ee50408-aa33-4d16-b8ff-f5e2dc59104b@ti.com>
On 7/29/26 4:57 AM, Vignesh Raghavendra wrote:
> Hi David,
>
> On 29/07/26 01:14, David Lechner (TI) wrote:
>> This is picking up a few downstream changes from [1] to make GPIOs
>> easier to use that I missed when using the BeagleY-AI with a mainline
>> kernel.
>>
>> [1]: https://openbeagle.org/beagleboard/linux/-/blob/v6.6.58-ti-arm64-r35/arch/arm64/boot/dts/ti/k3-am67a-beagley-ai-pinmux.dtsi?ref_type=heads
>>
> Above had to be reverted due to reasons mentioned here:
> https://lore.kernel.org/all/20250221091447.595199-2-mwalle@kernel.org/
Thanks. I was starting to suspect something like that.
Is PATCH 2/2 still acceptable?
next prev parent reply other threads:[~2026-07-29 13:57 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-28 19:44 [PATCH 0/2] arm64: dts: ti: k3-am67a-beagley-ai: GPIO improvements David Lechner (TI)
2026-07-28 19:44 ` [PATCH 1/2] arm64: dts: ti: k3-am67a-beagley-ai: Add gpio ranges David Lechner (TI)
2026-07-28 19:57 ` sashiko-bot
2026-07-28 21:30 ` David Lechner
2026-07-28 19:44 ` [PATCH 2/2] arm64: dts: ti: k3-am67a-beagley-ai: Add gpio line names David Lechner (TI)
2026-07-29 14:07 ` Robert Nelson
2026-07-29 9:57 ` [PATCH 0/2] arm64: dts: ti: k3-am67a-beagley-ai: GPIO improvements Vignesh Raghavendra
2026-07-29 13:57 ` David Lechner [this message]
2026-07-29 14:05 ` Robert Nelson
2026-07-30 4:55 ` Vignesh Raghavendra
2026-08-04 5:06 ` (subset) " Vignesh Raghavendra
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=02b159ad-42d3-4d1b-a73e-13612d9f2845@baylibre.com \
--to=dlechner@baylibre.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--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=robertcnelson@gmail.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