public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: Judith Mendez <jm@ti.com>
To: Judith Mendez <jm@ti.com>, Nishanth Menon <nm@ti.com>,
	Vignesh Raghavendra <vigneshr@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>,
	<linux-arm-kernel@lists.infradead.org>,
	<devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
	Moteen Shah <m-shah@ti.com>, Andrew Davis <afd@ti.com>
Subject: [PATCH v2 0/3] Fix MMC pin pull configurations
Date: Mon, 23 Feb 2026 17:37:28 -0600	[thread overview]
Message-ID: <20260223233731.2690472-1-jm@ti.com> (raw)

This series corrects MMC pin pull-up/pull-down configurations across
TI AM62L EVM, AM62P SK, & AM62 LP SK boards to properly match their
hardware design.

Most boards have external pull-ups on MMC pins, but DT configuration
was also enabling internal pulls. Having both internal and external
pulls active causes several issues:
- Unnecessary power consumption due to stronger pull resistance
- Floating pins violating SPEC recommendations

All changes are based on the respective board schematics referenced
in each patch.

Changes since v1:
- improved all commit descriptions
- removed incorrect claim: potential issues for modes with tighter
  timing requirements due to mismatched pull strengths between D0 and
  remaining data pins
- drop patch 2/4. While there is a host side mismatch between D0 and
  D1-D7 pins, leaving internal pullup on D0 equals a stronger pull,
  helping with poor board design issues and better matching D0 pullup
  strength with D1-D7 after taking into account eMMC card pullups on
  D1-D7 pins
- rebased against ti-k3-dts-next

Link to v1:
https://lore.kernel.org/all/20260212184246.2316659-1-jm@ti.com/

Judith Mendez (3):
  arm64: dts: ti: k3-am62p5-sk: Disable MMC1 internal pulls on data pins
  arm64: dts: ti: k3-am62l-evm: Disable MMC1 internal pulls on data pins
  arm64: dts: ti: k3-am62-lp-sk: Enable internal pulls for MMC0 data
    pins

 arch/arm64/boot/dts/ti/k3-am62-lp-sk.dts | 14 +++++++-------
 arch/arm64/boot/dts/ti/k3-am62l3-evm.dts |  6 +++---
 arch/arm64/boot/dts/ti/k3-am62p5-sk.dts  |  6 +++---
 3 files changed, 13 insertions(+), 13 deletions(-)

-- 
2.52.0



             reply	other threads:[~2026-02-23 23:37 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-23 23:37 Judith Mendez [this message]
2026-02-23 23:37 ` [PATCH v2 1/3] arm64: dts: ti: k3-am62p5-sk: Disable MMC1 internal pulls on data pins Judith Mendez
2026-02-23 23:37 ` [PATCH v2 2/3] arm64: dts: ti: k3-am62l-evm: " Judith Mendez
2026-02-23 23:37 ` [PATCH v2 3/3] arm64: dts: ti: k3-am62-lp-sk: Enable internal pulls for MMC0 " Judith Mendez
2026-03-19  8:02 ` [PATCH v2 0/3] Fix MMC pin pull configurations Francesco Dolcini
2026-03-23 15:43   ` Judith Mendez
2026-03-27  4:56 ` 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=20260223233731.2690472-1-jm@ti.com \
    --to=jm@ti.com \
    --cc=afd@ti.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=m-shah@ti.com \
    --cc=nm@ti.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