From: "Sverdlin, Alexander" <alexander.sverdlin@siemens.com>
To: "alexander.sverdlin@gmail.com" <alexander.sverdlin@gmail.com>,
"jm@ti.com" <jm@ti.com>, "msp@baylibre.com" <msp@baylibre.com>
Cc: "linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] arm64: dts: ti: k3-am62a7-sk: Disable mmc Schmitt Trigger
Date: Tue, 17 Feb 2026 13:19:36 +0000 [thread overview]
Message-ID: <5c604e259e412f9a49f42d6557d52a2d82c1d8f8.camel@siemens.com> (raw)
In-Reply-To: <b649669afe4e2c829389a6bedabe47446d2f3d2b.camel@siemens.com>
On Tue, 2026-02-17 at 13:57 +0100, Alexander Sverdlin wrote:
> > > > > > 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.
>
> I wanted to apply your patch and test on our HW, but I have some doubts, if
> the patch maybe missing something:
>
> - am654_sdhci_write_otapdly() turns out to be unused in any upstream U-Boot version
> - new "omap" variable in am654_sdhci_execute_tuning() is in fact unused as well
typo: "omap" -> "otap"
>
> what do I miss?
--
Alexander Sverdlin
Siemens AG
www.siemens.com
next prev parent reply other threads:[~2026-02-17 13:19 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
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 [this message]
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=5c604e259e412f9a49f42d6557d52a2d82c1d8f8.camel@siemens.com \
--to=alexander.sverdlin@siemens.com \
--cc=alexander.sverdlin@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=jm@ti.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=msp@baylibre.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®