From: "Sebastien Bourdelin" <sebastien.bourdelin@gmail.com>
To: "Sascha Hauer" <s.hauer@pengutronix.de>
Cc: <barebox@lists.infradead.org>, <oss-contrib@rtone.fr>,
"Sebastien Bourdelin" <sebastien.bourdelin@rtone.fr>
Subject: Re: [PATCH 4/4] mci: bcm2835: set timeout value to 100ms
Date: Wed, 06 Nov 2024 13:57:51 +0100 [thread overview]
Message-ID: <D5F434LTU1LZ.1KK4GTAAYPQEM@gmail.com> (raw)
In-Reply-To: <Zyi9nvr3acntKtkc@pengutronix.de>
On Mon Nov 4, 2024 at 1:27 PM CET, Sascha Hauer wrote:
> On Thu, Oct 31, 2024 at 10:27:21AM +0100, Sebastien Bourdelin wrote:
> > From: Sebastien Bourdelin <sebastien.bourdelin@rtone.fr>
> >
> > As mentionned in the Raspberry Pi4 bootrom Changelog [1]:
> > "Increase timeout of early SD/EMMC commands to 100ms".
> > The BCM2711 SDHCI can take up to 100ms to complete a command.
> >
> > Without this change, we had noticed that Barebox sometime stay stucked
> > on a timeout error while trying to boot Linux from the eMMC.
> >
> > [1] https://github.com/raspberrypi/rpi-eeprom/blob/master/firmware-2711/release-notes.md#2022-03-10---promote-the-2022-03-10-beta-release-to-lateststable
> >
> > Signed-off-by: Sebastien Bourdelin <sebastien.bourdelin@rtone.fr>
> > ---
> > drivers/mci/mci-bcm2835.c | 4 ++++
> > 1 file changed, 4 insertions(+)
> >
> > diff --git a/drivers/mci/mci-bcm2835.c b/drivers/mci/mci-bcm2835.c
> > index cbf99ee7ca..3b086ed22c 100644
> > --- a/drivers/mci/mci-bcm2835.c
> > +++ b/drivers/mci/mci-bcm2835.c
> > @@ -128,6 +128,10 @@ static int bcm2835_mci_request(struct mci_host *mci, struct mci_cmd *cmd,
> > block_data |= data->blocksize;
> > }
> >
> > + /* BCM2xxx SDHCI might take up to 100ms to complete a command */
> > + if (cmd != NULL)
> > + cmd->busy_timeout = 100;
>
> Do we need this for all commands or just some specific ones?
I actually have no idea, the CM4s datasheet doesn't give much
informations regarding the eMMC controller and we just found that
information in the rpi-eeprom changelog, and saw it was also the defaut
timeout value used in U-boot [1].
After this change, we haven't been able to reproduce the issue.
We know for sure this issue happens at least on a read
command.
[1] https://github.com/u-boot/u-boot/blob/master/drivers/mmc/sdhci.c#L195
>
> cmd is always non NULL, no need to check.
Ok, i can send a v2 for that, just let me know if my explanation for
your first question is enough.
>
> Sascha
next prev parent reply other threads:[~2024-11-06 13:34 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-31 9:27 [PATCH 0/4] Add a struct mci_cmd::busy_timeout member Sebastien Bourdelin
2024-10-31 9:27 ` [PATCH 1/4] mci: add a busy_timeout member to the struct mci_cmd Sebastien Bourdelin
2024-11-06 13:57 ` Ahmad Fatoum
2024-10-31 9:27 ` [PATCH 2/4] mci: zeroed all structs mci_cmd instances Sebastien Bourdelin
2024-11-06 13:57 ` Ahmad Fatoum
2024-10-31 9:27 ` [PATCH 3/4] mci: sdhci: use the busy_timeout value in the sdhci_wait_idle functions Sebastien Bourdelin
2024-11-06 14:00 ` Ahmad Fatoum
2024-10-31 9:27 ` [PATCH 4/4] mci: bcm2835: set timeout value to 100ms Sebastien Bourdelin
2024-11-04 12:27 ` Sascha Hauer
2024-11-06 12:57 ` Sebastien Bourdelin [this message]
2024-11-06 14:01 ` Ahmad Fatoum
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=D5F434LTU1LZ.1KK4GTAAYPQEM@gmail.com \
--to=sebastien.bourdelin@gmail.com \
--cc=barebox@lists.infradead.org \
--cc=oss-contrib@rtone.fr \
--cc=s.hauer@pengutronix.de \
--cc=sebastien.bourdelin@rtone.fr \
/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