From: Judith Mendez <jm@ti.com>
To: Sai Sree Kartheek Adivi <s-adivi@ti.com>, <nm@ti.com>,
<vigneshr@ti.com>, <kristo@kernel.org>, <robh@kernel.org>,
<krzk+dt@kernel.org>, <conor+dt@kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
<devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Cc: <hnagalla@ti.com>
Subject: Re: [PATCH 2/2] arm64: dts: ti: k3-am64: Set MMC1_CLK pin as OUTPUT
Date: Mon, 28 Sep 2026 12:46:19 -0500 [thread overview]
Message-ID: <decd3316-5c84-4f6c-a3ba-47501634c5c8@ti.com> (raw)
In-Reply-To: <850e724e-539c-47a9-a284-2cc8d362fca7@ti.com>
Sai,
On 9/28/26 12:00 PM, Judith Mendez wrote:
> Hi Sai,
>
> On 9/27/26 10:30 PM, Sai Sree Kartheek Adivi wrote:
>> From: Judith Mendez <jm@ti.com>
>>
>> MMC clock pins must be configured as OUTPUT-only per TRM specification
>> [0]
>> with receiver disabled (RXACTIVE bit = 0). Change MMC1_CLK from PIN_INPUT
>> to PIN_OUTPUT in AM64 device trees to match documentation.
>
> There was an issue showing up in automated testing that I was not sure
> if it was attributed to this patch series. So I was waiting to see the
> error again to debug. Not 100% confident this should go upstream yet.
On top to this, this change also needs to be added for all AM64 based
boards. But as said before, I think we need to wait a bit before
sending this patch (:
~ Judith
prev parent reply other threads:[~2026-09-28 17:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-28 3:30 [PATCH 0/2] k3-am64: Set MMC CLK pins as output Sai Sree Kartheek Adivi
2026-09-28 3:30 ` [PATCH 1/2] arm64: dts: ti: k3-am64: Drop MMC CLKLB config Sai Sree Kartheek Adivi
2026-09-28 3:30 ` [PATCH 2/2] arm64: dts: ti: k3-am64: Set MMC1_CLK pin as OUTPUT Sai Sree Kartheek Adivi
2026-09-28 17:00 ` Judith Mendez
2026-09-28 17:46 ` Judith Mendez [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=decd3316-5c84-4f6c-a3ba-47501634c5c8@ti.com \
--to=jm@ti.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=hnagalla@ti.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=s-adivi@ti.com \
--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®