From: Francesco Dolcini <francesco@dolcini.it>
To: "Mendez, Judith" <jm@ti.com>
Cc: Francesco Dolcini <francesco@dolcini.it>,
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>,
Francesco Dolcini <francesco.dolcini@toradex.com>,
linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, Moteen Shah <m-shah@ti.com>,
stable@vger.kernel.org
Subject: Re: [PATCH v1] arm64: dts: ti: k3-am62-verdin: Set MMC clock pins as OUTPUT
Date: Fri, 14 Aug 2026 09:15:49 +0200 [thread overview]
Message-ID: <20260814071549.GA5246@francesco-nb> (raw)
In-Reply-To: <b4ed6b46-07c3-4ebf-9fc8-b9ae0dc03a51@ti.com>
On Thu, Aug 13, 2026 at 02:57:52PM -0500, Mendez, Judith wrote:
> Hi Francesco,
>
> On 8/13/2026 6:12 AM, Francesco Dolcini wrote:
> > From: Francesco Dolcini <francesco.dolcini@toradex.com>
> >
> > MMC clock pins must be configured as OUTPUT-only per TRM [0] with
> > receiver disabled (RXACTIVE bit = 0). Change MMC CLK pins from
> > PIN_INPUT to PIN_OUTPUT to match documentation.
> >
> > Link: https://www.ti.com/lit/pdf/spruiv7 Rev. C: Table 12-246. MMCSDi I/O Signals [0]
> > Fixes: 316b80246b16 ("arm64: dts: ti: add verdin am62")
> > Cc: stable@vger.kernel.org
> > Signed-off-by: Francesco Dolcini <francesco.dolcini@toradex.com>
>
> Assuming defaults are set.
We have
AM62X_IOPAD(0x11c, PIN_INPUT, 0) /* (#N/A) MMC2_CLKB */
is this what you are referring to here and in the other discussion
thread?
Francesco
next prev parent reply other threads:[~2026-08-14 7:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-13 11:12 [PATCH v1] arm64: dts: ti: k3-am62-verdin: Set MMC clock pins as OUTPUT Francesco Dolcini
2026-08-13 19:57 ` Mendez, Judith
2026-08-14 7:15 ` Francesco Dolcini [this message]
2026-08-17 22:54 ` Mendez, Judith
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=20260814071549.GA5246@francesco-nb \
--to=francesco@dolcini.it \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=francesco.dolcini@toradex.com \
--cc=jm@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=m-shah@ti.com \
--cc=nm@ti.com \
--cc=robh@kernel.org \
--cc=stable@vger.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