Linux MultiMedia Card development
 help / color / mirror / Atom feed
From: Judith Mendez <jm@ti.com>
To: Josua Mayer <josua@solid-run.com>,
	Adrian Hunter <adrian.hunter@intel.com>,
	Ulf Hansson <ulf.hansson@linaro.org>
Cc: <linux-mmc@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
	<rabeeh@solid-run.com>, <jon@solid-run.com>,
	<stable@vger.kernel.org>
Subject: Re: [PATCH v2] Revert "mmc: sdhci_am654: Add sdhci_am654_start_signal_voltage_switch"
Date: Wed, 5 Feb 2025 13:39:07 -0600	[thread overview]
Message-ID: <93d7e958-be62-45b3-ba8f-d3e4cf2839bf@ti.com> (raw)
In-Reply-To: <20250127-am654-mmc-regression-v2-1-9bb39fb12810@solid-run.com>

Hi all,

On 1/27/25 2:12 PM, Josua Mayer wrote:
> This reverts commit 941a7abd4666912b84ab209396fdb54b0dae685d.
> 
> This commit uses presence of device-tree properties vmmc-supply and
> vqmmc-supply for deciding whether to enable a quirk affecting timing of
> clock and data.
> The intention was to address issues observed with eMMC and SD on AM62
> platforms.
> 
> This new quirk is however also enabled for AM64 breaking microSD access
> on the SolidRun HimmingBoard-T which is supported in-tree since v6.11,
> causing a regression. During boot microSD initialization now fails with
> the error below:
> 
> [    2.008520] mmc1: SDHCI controller on fa00000.mmc [fa00000.mmc] using ADMA 64-bit
> [    2.115348] mmc1: error -110 whilst initialising SD card
> 
> The heuristics for enabling the quirk are clearly not correct as they
> break at least one but potentially many existing boards.
> 
> Revert the change and restore original behaviour until a more
> appropriate method of selecting the quirk is derived.


Somehow I missed these emails, apologies.

Thanks for reporting this issue Josua.

We do need this patch for am62x devices since it fixes timing issues
with a variety of SD cards on those boards, but if there is a
regression, too bad, patch had to be reverted.

I will look again into how to implement this quirk, I think using the
voltage regulator nodes to discover if we need this quirk might not have
been a good idea, based on your explanation. I believe I did test the
patch on am64x SK and am64x EVM boards and saw no boot issue there,
so the issue seems related to the voltage regulator nodes existing in DT
(the heuristics for enabling the quirk) as you call it.

Again, thanks for reporting, will look into fixing this issue for am62x
again soon.

~ Judith



  parent reply	other threads:[~2025-02-05 19:39 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-27 20:12 [PATCH v2] Revert "mmc: sdhci_am654: Add sdhci_am654_start_signal_voltage_switch" Josua Mayer
2025-02-03 14:04 ` Ulf Hansson
2025-02-05 19:39 ` Judith Mendez [this message]
2025-03-19 10:22   ` Sverdlin, Alexander
2025-03-19 16:25     ` Judith Mendez
2025-03-19 17:07       ` Judith Mendez
2025-03-19 17:19       ` Sverdlin, Alexander
2025-03-19 17:27         ` Judith Mendez

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=93d7e958-be62-45b3-ba8f-d3e4cf2839bf@ti.com \
    --to=jm@ti.com \
    --cc=adrian.hunter@intel.com \
    --cc=jon@solid-run.com \
    --cc=josua@solid-run.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mmc@vger.kernel.org \
    --cc=rabeeh@solid-run.com \
    --cc=stable@vger.kernel.org \
    --cc=ulf.hansson@linaro.org \
    /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