From: Ahmad Fatoum <a.fatoum@pengutronix.de>
To: Sascha Hauer <sha@pengutronix.de>
Cc: barebox@lists.infradead.org
Subject: Re: [PATCH master] mci: bcm2835: reset host controller on barebox shutdown
Date: Fri, 30 Sep 2022 15:18:29 +0100 [thread overview]
Message-ID: <e6743279-3842-5595-66bc-4b2d793ab8ba@pengutronix.de> (raw)
In-Reply-To: <20220930122414.GZ986@pengutronix.de>
On 30.09.22 13:24, Sascha Hauer wrote:
> On Fri, Sep 30, 2022 at 01:19:40PM +0200, Ahmad Fatoum wrote:
>> We don't usually disable MMC controllers on barebox shutdown, because
>> they don't DMA on their own, unlike e.g. network controllers.
>>
>> Booting Linux v5.17.0 on a Raspberry Pi 4 in 32-bit mode still has the
>> MMC host controller driver complain:
>>
>> [ 22.464887] mmc1: Got data interrupt 0x00000002 even though no
>> data operation was in progress.
>>
>> Fix this by resetting the SDHCI once barebox is done with it.
>>
>> Signed-off-by: Ahmad Fatoum <a.fatoum@pengutronix.de>
>> ---
>> drivers/mci/mci-bcm2835.c | 12 ++++++++++++
>> 1 file changed, 12 insertions(+)
>
> Applied, thanks
Please drop again. The warning is spurious and it just happened to not
show up in my testing runs afterwards. I am looking into a proper fix
and will let it do more reboot cycles to make sure issue is indeed
resolved.
>
> Sascha
>
>>
>> diff --git a/drivers/mci/mci-bcm2835.c b/drivers/mci/mci-bcm2835.c
>> index f092156f9a83..c5b226ba033c 100644
>> --- a/drivers/mci/mci-bcm2835.c
>> +++ b/drivers/mci/mci-bcm2835.c
>> @@ -385,6 +385,8 @@ static int bcm2835_mci_probe(struct device_d *hw_dev)
>> host->sdhci.read32 = bcm2835_sdhci_read32;
>> host->sdhci.write32 = bcm2835_sdhci_write32;
>>
>> + hw_dev->priv = host;
>> +
>> mci_of_parse(&host->mci);
>>
>> iores = dev_request_mem_resource(hw_dev, 0);
>> @@ -420,6 +422,15 @@ static int bcm2835_mci_probe(struct device_d *hw_dev)
>> return mci_register(&host->mci);
>> }
>>
>> +static void bcm2835_mci_remove(struct device_d *dev)
>> +{
>> + struct bcm2835_mci_host *host = dev->priv;
>> +
>> + sdhci_write32(&host->sdhci,
>> + SDHCI_CLOCK_CONTROL__TIMEOUT_CONTROL__SOFTWARE_RESET,
>> + 0x00);
>> +}
>> +
>> static __maybe_unused struct of_device_id bcm2835_mci_compatible[] = {
>> {
>> .compatible = "brcm,bcm2835-sdhci",
>> @@ -433,6 +444,7 @@ static __maybe_unused struct of_device_id bcm2835_mci_compatible[] = {
>> static struct driver_d bcm2835_mci_driver = {
>> .name = "bcm2835_mci",
>> .probe = bcm2835_mci_probe,
>> + .remove = bcm2835_mci_remove,
>> .of_compatible = DRV_OF_COMPAT(bcm2835_mci_compatible),
>> };
>>
>> --
>> 2.30.2
>>
>>
>>
>
--
Pengutronix e.K. | |
Steuerwalder Str. 21 | http://www.pengutronix.de/ |
31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
next prev parent reply other threads:[~2022-09-30 14:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-30 11:19 Ahmad Fatoum
2022-09-30 12:24 ` Sascha Hauer
2022-09-30 14:18 ` Ahmad Fatoum [this message]
2022-10-04 7:55 ` Sascha Hauer
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=e6743279-3842-5595-66bc-4b2d793ab8ba@pengutronix.de \
--to=a.fatoum@pengutronix.de \
--cc=barebox@lists.infradead.org \
--cc=sha@pengutronix.de \
/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