From: Judith Mendez <jm@ti.com>
To: "Kumar, Udit" <u-kumar1@ti.com>, Nishanth Menon <nm@ti.com>
Cc: Tero Kristo <kristo@kernel.org>, Rob Herring <robh@kernel.org>,
"Krzysztof Kozlowski" <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
"Garrett Giordano" <ggiordano@phytec.com>,
Wadim Egorov <w.egorov@phytec.de>,
"Robert Nelson" <robertcnelson@gmail.com>,
Tony Lindgren <tony@atomide.com>,
"Nora Schiffer" <nora.schiffer@ew.tq-group.com>,
Stefano Radaelli <stefano.r@variscite.com>,
<linux-arm-kernel@lists.infradead.org>,
<devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
Moteen Shah <m-shah@ti.com>
Subject: Re: [PATCH v4 01/15] arm64: dts: ti: k3-am62a: Fix MMC0_CLK register address
Date: Fri, 11 Sep 2026 11:54:31 -0500 [thread overview]
Message-ID: <134505de-78e1-418e-8cd0-855697633696@ti.com> (raw)
In-Reply-To: <9a1146e9-0c00-4348-b1a5-31be7c597eea@ti.com>
Hi Udit,
On 9/11/26 2:57 AM, Kumar, Udit wrote:
>
>
> On 9/10/2026 3:17 AM, Judith Mendez wrote:
>> MMC0_CLKLB and MMC0_CLK have incorrectly swapped register addresses
>> as per datasheet [0]. Set the correct MMC0_CLK address and drop the
>> unneeded MMC0_CLKLB pin configuration.
>>
>> [0] https://www.ti.com/lit/gpn/am62a7 Rev. E: Table 5-1. Pin Attributes
>>
>> Fixes: e041ec6e86e7 ("arm64: dts: ti: k3-am62a7-sk: Enable eMMC support")
>> Cc: <stable@vger.kernel.org>
>> Signed-off-by: Judith Mendez <jm@ti.com>
>> Reviewed-by: Moteen Shah <m-shah@ti.com>
>> ---
>> arch/arm64/boot/dts/ti/k3-am62a7-sk.dts | 3 +--
>> 1 file changed, 1 insertion(+), 2 deletions(-)
>>
>> diff --git a/arch/arm64/boot/dts/ti/k3-am62a7-sk.dts b/arch/arm64/boot/dts/ti/k3-am62a7-sk.dts
>> index d3b3675e7a8fc..b04636cab71c7 100644
>> --- a/arch/arm64/boot/dts/ti/k3-am62a7-sk.dts
>> +++ b/arch/arm64/boot/dts/ti/k3-am62a7-sk.dts
>> @@ -328,8 +328,7 @@ AM62AX_IOPAD(0x0b4, PIN_INPUT_PULLUP, 1) /* (K24) GPMC0_CSn3.I2C2_SDA */
>> main_mmc0_pins_default: main-mmc0-default-pins {
>> pinctrl-single,pins = <
>> AM62AX_IOPAD(0x220, PIN_INPUT, 0) /* (Y3) MMC0_CMD */
>> - AM62AX_IOPAD(0x218, PIN_INPUT, 0) /* (AB1) MMC0_CLKLB */
>> - AM62AX_IOPAD(0x21c, PIN_INPUT, 0) /* (AB1) MMC0_CLK */
>> + AM62AX_IOPAD(0x218, PIN_INPUT, 0) /* (AB1) MMC0_CLK */
>
> Shouldn't be MMC0_CLK be o/p, instead of PIN_INPUT
> Similar to patch [0]
> [0] https://lore.kernel.org/all/20260909214743.899477-4-jm@ti.com/
Yes it should, and it is in the same series as you pointed out. This
current patch only fixes register address as per commit description. (:
~ Judith
>
>
>
>> AM62AX_IOPAD(0x214, PIN_INPUT, 0) /* (AA2) MMC0_DAT0 */
>> AM62AX_IOPAD(0x210, PIN_INPUT_PULLUP, 0) /* (AA1) MMC0_DAT1 */
>> AM62AX_IOPAD(0x20c, PIN_INPUT_PULLUP, 0) /* (AA3) MMC0_DAT2 */
>
next prev parent reply other threads:[~2026-09-11 16:55 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-09 21:47 [PATCH v4 00/15] MMC pinmux configuration fixes Judith Mendez
2026-09-09 21:47 ` [PATCH v4 01/15] arm64: dts: ti: k3-am62a: Fix MMC0_CLK register address Judith Mendez
2026-09-11 7:57 ` Kumar, Udit
2026-09-11 16:54 ` Judith Mendez [this message]
2026-09-14 16:23 ` Kumar, Udit
2026-09-09 21:47 ` [PATCH v4 02/15] arm64: dts: ti: k3-am62l-evm: Remove unnecessary internal pullups for MMC0 Judith Mendez
2026-09-09 21:47 ` [PATCH v4 03/15] arm64: dts: ti: k3-am62a7-sk: Set eMMC clock pin as OUTPUT Judith Mendez
2026-09-09 21:47 ` [PATCH v4 04/15] arm64: dts: ti: k3-am62a7-sk: Set SD " Judith Mendez
2026-09-09 21:47 ` [PATCH v4 05/15] arm64: dts: ti: k3-am62a-phycore-som: Set eMMC " Judith Mendez
2026-09-15 16:54 ` Wadim Egorov
2026-09-09 21:47 ` [PATCH v4 06/15] arm64: dts: ti: k3-am62-lp-sk: Set eMMC clock pins " Judith Mendez
2026-09-09 21:47 ` [PATCH v4 07/15] arm64: dts: ti: k3-am62-pocketbeagle2: Set SD clock pin " Judith Mendez
2026-09-09 21:47 ` [PATCH v4 08/15] arm64: dts: ti: k3-am625-beagleplay: Set MMC clock pins " Judith Mendez
2026-09-09 21:47 ` [PATCH v4 09/15] arm64: dts: ti: k3-am62x-sk-common: Set SD clock pin " Judith Mendez
2026-09-09 21:47 ` [PATCH v4 10/15] arm64: dts: ti: k3-am625-sk-common: Set eMMC " Judith Mendez
2026-09-09 21:47 ` [PATCH v4 11/15] arm64: dts: ti: k3-am62-phycore-som: " Judith Mendez
2026-09-15 16:54 ` Wadim Egorov
2026-09-09 21:47 ` [PATCH v4 12/15] arm64: dts: ti: k3-am625-tqma62xx: Set MMC clock pins " Judith Mendez
2026-09-09 21:47 ` [PATCH v4 13/15] arm64: dts: ti: k3-am625-var-som-symphony: Set SD " Judith Mendez
2026-09-14 15:00 ` Stefano Radaelli
2026-09-09 21:47 ` [PATCH v4 14/15] arm64: dts: ti: k3-am625-var-som: Set MMC " Judith Mendez
2026-09-14 15:04 ` Stefano Radaelli
2026-09-09 21:47 ` [PATCH v4 15/15] arm64: dts: ti: k3-am62x-phyboard-lyra: Set SD clock pin " Judith Mendez
2026-09-15 16:54 ` Wadim Egorov
2026-09-16 4:49 ` [PATCH v4 00/15] MMC pinmux configuration fixes Moteen Shah
2026-09-22 14:24 ` 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=134505de-78e1-418e-8cd0-855697633696@ti.com \
--to=jm@ti.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=ggiordano@phytec.com \
--cc=kristo@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=m-shah@ti.com \
--cc=nm@ti.com \
--cc=nora.schiffer@ew.tq-group.com \
--cc=robertcnelson@gmail.com \
--cc=robh@kernel.org \
--cc=stefano.r@variscite.com \
--cc=tony@atomide.com \
--cc=u-kumar1@ti.com \
--cc=w.egorov@phytec.de \
/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®