mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Judith Mendez <jm@ti.com>
To: "Markus Schneider-Pargmann (TI.com)" <msp@baylibre.com>,
	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>,
	Alexander Sverdlin <alexander.sverdlin@gmail.com>
Cc: Vishal Mahaveer <vishalm@ti.com>,
	Kevin Hilman <khilman@baylibre.com>, Dhruva Gole <d-gole@ti.com>,
	Sebin Francis <sebin.francis@ti.com>,
	"Kendall Willis" <k-willis@ti.com>,
	Akashdeep Kaur <a-kaur@ti.com>,
	<linux-arm-kernel@lists.infradead.org>,
	<devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] arm64: dts: ti: k3-am62a7-sk: Disable mmc Schmitt Trigger
Date: Mon, 12 Jan 2026 18:29:54 -0600	[thread overview]
Message-ID: <c47697b4-6ebb-4af9-be96-c964d990835d@ti.com> (raw)
In-Reply-To: <20260106-topic-am62a-mmc-pinctrl-v6-19-next-v1-1-1190ac29aadb@baylibre.com>

On 1/6/26 10:22 AM, Markus Schneider-Pargmann (TI.com) wrote:
> Remove Schmitt Trigger from mmc pins. With Schmitt Trigger enabled
> u-boot SPL is not able to read u-boot from mmc:
> 
>      Trying to boot from MMC2
>      Error reading cluster
>      spl_load_image_fat: error reading image u-boot.img, err - -22
>      Error: -22
>      SPL: Unsupported Boot Device!
>      SPL: failed to boot from all boot devices
>      ### ERROR ### Please RESET the board ###
> 
> I bisected this issue between u-boot v2025.10 and v2026.01 and found the
> devicetree merge to be the problem. At a closer look I found the
> k3-pinctrl.h changes. Disabling the Schmitt Trigger fixes the u-boot SPL
> failure to read from mmc.

I have tested 4 AM62A SK boards and I cannot replicate the issue
you are seeing. I do not see an issue with Schmitt Trigger in U-boot
nor Linux /:

Can you please run a quick tap sweep on MMC1 and MMC0 interfaces like
so? https://gist.github.com/jmenti/f4a73a8323e44bf717c6d2c528c499ca

This will give me an idea if whether we should be talking about
revisiting characterization with ST_ENA=1.

Also, are you able to replicate the issue on more than one board? Or is
this the only board you see the issue on?

~ Judith

  parent reply	other threads:[~2026-01-13  0:29 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-06 16:22 Markus Schneider-Pargmann (TI.com)
2026-01-06 17:25 ` Alexander Sverdlin
2026-01-06 20:25   ` Markus Schneider-Pargmann
2026-01-07 14:23     ` Alexander Sverdlin
2026-01-07 22:57     ` Alexander Sverdlin
2026-01-08 16:40       ` Nishanth Menon
2026-01-08 17:54         ` Sverdlin, Alexander
2026-01-07 14:49   ` Alexander Sverdlin
2026-01-08 19:04     ` Markus Schneider-Pargmann
2026-01-08 14:07 ` Vitor Soares
2026-01-08 14:23   ` Alexander Sverdlin
2026-01-08 16:42   ` Nishanth Menon
2026-01-13  0:29 ` Judith Mendez [this message]
2026-01-14  9:16   ` Markus Schneider-Pargmann
2026-01-14 22:04     ` Judith Mendez
2026-02-03 10:35       ` Markus Schneider-Pargmann
2026-02-05  2:03         ` Judith Mendez
2026-02-05  7:24           ` Francesco Dolcini
2026-02-05 17:07             ` Judith Mendez
2026-02-05 17:57               ` Alexander Sverdlin
2026-02-17 12:57           ` Sverdlin, Alexander
2026-02-17 13:19             ` Sverdlin, Alexander
2026-02-17 13:23             ` Sverdlin, Alexander
2026-02-20  0:10               ` Judith Mendez
2026-02-20  0:42                 ` Judith Mendez
2026-02-26 19:59                   ` Markus Schneider-Pargmann
2026-03-16 12:22                   ` Sverdlin, Alexander

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=c47697b4-6ebb-4af9-be96-c964d990835d@ti.com \
    --to=jm@ti.com \
    --cc=a-kaur@ti.com \
    --cc=alexander.sverdlin@gmail.com \
    --cc=conor+dt@kernel.org \
    --cc=d-gole@ti.com \
    --cc=devicetree@vger.kernel.org \
    --cc=k-willis@ti.com \
    --cc=khilman@baylibre.com \
    --cc=kristo@kernel.org \
    --cc=krzk+dt@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=msp@baylibre.com \
    --cc=nm@ti.com \
    --cc=robh@kernel.org \
    --cc=sebin.francis@ti.com \
    --cc=vigneshr@ti.com \
    --cc=vishalm@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®