From: Alexander Sverdlin <alexander.sverdlin@gmail.com>
To: Vitor Soares <ivitro@gmail.com>,
"Markus Schneider-Pargmann (TI.com)" <msp@baylibre.com>,
Nishanth Menon <nm@ti.com>, Vignesh Raghavendra <vigneshr@ti.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: Thu, 08 Jan 2026 15:23:55 +0100 [thread overview]
Message-ID: <a47ca860adb760ad2bf9e3e0d233b0b2b6f73200.camel@gmail.com> (raw)
In-Reply-To: <49bfb30f71eae0844676e6b545d67739b6d79539.camel@gmail.com>
Hi Vitor,
On Thu, 2026-01-08 at 14:07 +0000, Vitor Soares wrote:
> On Tue, 2026-01-06 at 17:22 +0100, 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.
> >
> > Fixes: 5b272127884b ("arm64: dts: ti: k3-pinctrl: Enable Schmitt Trigger by
> > default")
> > Signed-off-by: Markus Schneider-Pargmann (TI.com) <msp@baylibre.com>
> >
> Hi Markus,
>
> We're seeing a similar issue on Verdin AM62 with U-Boot 2026.01. The
> board has complete SPL boot failure with no output at all.
>
> This occurs in the same version you bisected (v2026.01 failing).
> Could the Schmitt Trigger changes also affect Verdin AM62?
they do affect AM62, even though not not every HW, I have one HW variant
working properly and one where I observe the problem. Maybe a revert
of 5b272127884b for now would make more sense than just fixing AM62A7.
I unfortunately do not have any reply on this from TI yet.
--
Alexander Sverdlin.
next prev parent reply other threads:[~2026-01-08 14:23 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 [this message]
2026-01-08 16:42 ` Nishanth Menon
2026-01-13 0:29 ` Judith Mendez
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=a47ca860adb760ad2bf9e3e0d233b0b2b6f73200.camel@gmail.com \
--to=alexander.sverdlin@gmail.com \
--cc=a-kaur@ti.com \
--cc=d-gole@ti.com \
--cc=devicetree@vger.kernel.org \
--cc=ivitro@gmail.com \
--cc=k-willis@ti.com \
--cc=khilman@baylibre.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=msp@baylibre.com \
--cc=nm@ti.com \
--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
Powered by JetHome