From: "Mendez, Judith" <jm@ti.com>
To: <sashiko-reviews@lists.linux.dev>
Cc: <robh@kernel.org>, <conor+dt@kernel.org>, <devicetree@vger.kernel.org>
Subject: Re: [PATCH 7/8] arm64: dts: ti: k3-am64-sk: Disable MMC1 internal pulls
Date: Mon, 3 Aug 2026 17:26:11 -0500 [thread overview]
Message-ID: <9bd53787-0d73-4367-9453-b2ae8eeb3ee0@ti.com> (raw)
In-Reply-To: <20260729201317.3208B1F000E9@smtp.kernel.org>
Hi all,
Addressing Sashiko review.
On 7/29/2026 3:13 PM, sashiko-bot@kernel.org wrote:
> Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
> - [Medium] Unintended removal of pulldown and incorrect receiver state for `MMC1_CLK`.
> --
>
> --- Patch [7]: [PATCH 7/8] arm64: dts: ti: k3-am64-sk: Disable MMC1 internal pulls ---
> commit 3a83d1bd44a1ef684b5bd29a93a2127e82509201
> Author: Judith Mendez <jm@ti.com>
>
> arm64: dts: ti: k3-am64-sk: Disable MMC1 internal pulls
>
> This commit drops internal pullups on MMC data and CMD pins to prevent violating
> minimum pull resistance specifications, as external pullups are already present
> on the board. It also removes the CD pullup to reduce power consumption.
>
>> diff --git a/arch/arm64/boot/dts/ti/k3-am642-sk.dts b/arch/arm64/boot/dts/ti/k3-am642-sk.dts
>> --- a/arch/arm64/boot/dts/ti/k3-am642-sk.dts
>> +++ b/arch/arm64/boot/dts/ti/k3-am642-sk.dts
>> @@ -198,13 +198,13 @@ &main_pmx0 {
>> main_mmc1_pins_default: main-mmc1-default-pins {
>> bootph-all;
>> pinctrl-single,pins = <
>> - AM64X_IOPAD(0x0298, PIN_INPUT_PULLUP, 0) /* (D19) MMC1_SDCD */
>> - AM64X_IOPAD(0x0294, PIN_INPUT_PULLUP, 0) /* (J19) MMC1_CMD */
>> - AM64X_IOPAD(0x028c, PIN_INPUT_PULLDOWN, 0) /* (L20) MMC1_CLK */
>> + AM64X_IOPAD(0x0298, PIN_INPUT, 0) /* (D19) MMC1_SDCD */
>> + AM64X_IOPAD(0x0294, PIN_INPUT, 0) /* (J19) MMC1_CMD */
>> + AM64X_IOPAD(0x028c, PIN_INPUT, 0) /* (L20) MMC1_CLK */
>
> [Severity: Medium]
> The commit message mentions removing internal pullups because of external
> pullups on the board, but MMC1_CLK in main_mmc1_pins_default was configured
> with PIN_INPUT_PULLDOWN. Does this blanket change unintentionally leave the clock
> pin floating when the MMC controller tri-states the clock line (for example,
> during idle or suspend)?
MMC1_CLK has a 49.9K external pulldown, so there should be no issue
dropping the internal pulldown.
>
> Additionally, keeping this as PIN_INPUT leaves the receiver enabled. If the
> clock line floats without a pulldown, could the floating voltage cause the input
> receiver to rapidly toggle and increase power consumption? Should this pin be
> configured as OUTPUT-only instead?
I think I missed one patch for setting MMC1_CLK pin as output for am64x,
will check and add patch in respin.
~ Judith
next prev parent reply other threads:[~2026-08-03 22:26 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-29 19:59 [PATCH 0/8] MMC pinmux configuration fixes Judith Mendez
2026-07-29 19:59 ` [PATCH 1/8] arm64: dts: ti: k3-am62a: Fix MMC0_CLK register address Judith Mendez
2026-07-29 19:59 ` [PATCH 2/8] arm64: dts: ti: k3-am62a: Set MMC clock pins as OUTPUT Judith Mendez
2026-07-29 19:59 ` [PATCH 3/8] arm64: dts: ti: k3-am62: " Judith Mendez
2026-07-29 20:08 ` sashiko-bot
2026-08-03 22:13 ` Mendez, Judith
2026-07-29 19:59 ` [PATCH 4/8] arm64: dts: ti: k3-am62l-evm: Remove unnecessary internal pullups for MMC0 Judith Mendez
2026-07-29 19:59 ` [PATCH 5/8] arm64: dts: ti: k3-am64: Enable IO expander interrupt Judith Mendez
2026-07-29 20:09 ` sashiko-bot
2026-08-03 22:33 ` Mendez, Judith
2026-07-29 19:59 ` [PATCH 6/8] arm64: dts: ti: k3-am64: Let MMC1 clock loopback use hardware default Judith Mendez
2026-07-29 19:59 ` [PATCH 7/8] arm64: dts: ti: k3-am64-sk: Disable MMC1 internal pulls Judith Mendez
2026-07-29 20:13 ` sashiko-bot
2026-08-03 22:26 ` Mendez, Judith [this message]
2026-07-29 19:59 ` [PATCH 8/8] arm64: dts: ti: k3-am642-evm: Remove unnecessary internal pullups for MMC1 Judith Mendez
2026-07-31 10:56 ` [PATCH 0/8] MMC pinmux configuration fixes Vignesh Raghavendra
2026-08-03 22:11 ` 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=9bd53787-0d73-4367-9453-b2ae8eeb3ee0@ti.com \
--to=jm@ti.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=robh@kernel.org \
--cc=sashiko-reviews@lists.linux.dev \
/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