From: "João Paulo Silva Gonçalves" <joao.goncalves@toradex.com>
To: "nm@ti.com" <nm@ti.com>, "vigneshr@ti.com" <vigneshr@ti.com>
Cc: "ulf.hansson@linaro.org" <ulf.hansson@linaro.org>,
"adrian.hunter@intel.com" <adrian.hunter@intel.com>,
"linux-mmc@vger.kernel.org" <linux-mmc@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Francesco Dolcini <francesco.dolcini@toradex.com>
Subject: Re: SDHCI AM654 driver delaying boot time
Date: Fri, 10 Nov 2023 14:55:51 +0000 [thread overview]
Message-ID: <5d4785dc46f7798fe96366d6128e068f623ce1c2.camel@toradex.com> (raw)
In-Reply-To: <81fee24c-47d2-4c2d-8f88-35fd1ea1d639@ti.com>
On Fri, 2023-11-10 at 10:08 +0530, Vignesh Raghavendra wrote:
> Hi Joao
>
> On 09/11/23 23:21, Nishanth Menon wrote:
> > On 18:56-20231108, João Paulo Silva Gonçalves wrote:
> > > Hello all,
> > >
> > > We are trying to minimize boot time for our AM62 devices. Unfortunately, we have identified a delay of approximately 1.5 seconds caused by the
> > > sdhci_am654 driver. This delay is a result of a timeout within the driver (MAX_POWER_ON_TIMEOUT) and was introduced in commit 7ca0f16 ("mmc:
> > > sdhci_am654: Add workaround for card detect debounce timer"). This issue arises only when there is no SD card present in the MMC slot. We tested the
> > > driver with a lower timeout value and everything worked. However, as indicated in the commit message, this timeout may be related to the way the sdhci
> > > controller hardware IP works. Currently, the driver employs a sort of a "busy loop" to wait for this timeout to pass delaying the boot. Why is
> > > need to busy loop for this timeout? Is it possible to wait for it in the backgroud? Am I am missing something here?
>
> sdhci_am654_write_power_on() does have usleep_range() of 1 to 10ms. If
> that isn't sufficient to preempt and allow other drivers to probe, then
> probably worth setting sleep_us in read_poll_timeout() call.
>
>
> >
> > I am not an mmc expert, but, Isn't this sequence part of the programmer
> > manual in the TRM[1]? Either way, one additional issue I did end up with
> > when I was doing beagleplay[2] was when i booted off emmc and runtime PM
> > disabled SD/MMC interface, the MMC IP's CD mode would'nt work since the
> > IP isn't clocked. So I switched the mux mode to GPIO to use mmc CD
> > there. I haven't timed that approach where
> > SDHCI_AM654_QUIRK_FORCE_CDTEST would get set.
> >
> > [1] https://www.ti.com/lit/pdf/spruiv7
> > [2] https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/arch/arm64/boot/dts/ti/k3-am625-beagleplay.dts#n835
>
>
> Above is a good experiment to see if it helps boot time. Can you set
> SDCD line to GPIO and hook up using cd-gpios? You would also need to
> set ti,fails-without-test-cd
>
I will try what Nishanth said about the gpio and also increase sleep_us.
Thank for the insights!
Regards,
Joao Paulo Goncalves
next prev parent reply other threads:[~2023-11-10 17:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-08 18:56 SDHCI AM654 driver delaying boot time João Paulo Silva Gonçalves
2023-11-09 17:51 ` Nishanth Menon
2023-11-10 4:38 ` Vignesh Raghavendra
2023-11-10 14:55 ` João Paulo Silva Gonçalves [this message]
2023-11-10 14:19 ` Francesco Dolcini
2023-11-14 8:25 ` Adrian Hunter
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=5d4785dc46f7798fe96366d6128e068f623ce1c2.camel@toradex.com \
--to=joao.goncalves@toradex.com \
--cc=adrian.hunter@intel.com \
--cc=francesco.dolcini@toradex.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mmc@vger.kernel.org \
--cc=nm@ti.com \
--cc=ulf.hansson@linaro.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