From: Sascha Hauer <s.hauer@pengutronix.de>
To: Ahmad Fatoum <a.fatoum@pengutronix.de>
Cc: barebox@lists.infradead.org, Michael Tretter <m.tretter@pengutronix.de>
Subject: Re: [PATCH master] mci: dw_mmc: drop CD from mask programmed into interrupt status register
Date: Mon, 23 Feb 2026 12:41:42 +0100 [thread overview]
Message-ID: <aZw89shLd9_le_l5@pengutronix.de> (raw)
In-Reply-To: <fbe0f299-7942-4599-92b4-d2d5fbbf1e28@pengutronix.de>
On Mon, Feb 23, 2026 at 12:40:33PM +0100, Ahmad Fatoum wrote:
> Hello Sascha,
>
> On 2/23/26 12:37 PM, Sascha Hauer wrote:
> > On Mon, Feb 09, 2026 at 05:40:44PM +0100, Ahmad Fatoum wrote:
> >> We don't usually care for the card detect in barebox and just
> >> unconditionally try to access the card. If it fails, a probe can be
> >> attempted later via setting mmcX.probe=1.
> >>
> >> The dw_mmc driver diverges from this and enables all kinds
> >> of interrupts in the interrupt status polled after submitting commands,
> >> including card-detect.
> >>
> >> This appears to be problematic, when we have a GPIO card detect and are
> >> not using the card detect hardware function.
> >>
> >> Align behavior with Linux and skip polling for hardware card-detect when
> >> we have a GPIO card detect. The current behavior was inherited from
> >> U-Boot, which still does it this way and it's possible it would be affected
> >> by this issue as well, once U-Boot updates to use DTs >= v6.19-rc1, provided
> >> that the ROCK 5 support in U-Boot uses CONFIG_OF_UPSTREAM.
> >>
> >> Fixes: a3bf6c16f77d ("dts: update to v6.19-rc1")
> >> Reported-by: Michael Tretter <m.tretter@pengutronix.de>
> >> Signed-off-by: Ahmad Fatoum <a.fatoum@pengutronix.de>
> >> ---
> >> drivers/mci/dw_mmc.c | 33 ++++++++++++++++++++++++++++++++-
> >> drivers/mci/dw_mmc.h | 1 +
> >> 2 files changed, 33 insertions(+), 1 deletion(-)
> >
> > Given that this doesn't resolve Michaels issue I won't apply it for
> > master. Anyway, the patch might still be correct, so what should I do
> > with it?
>
> Let's leave it unapplied for now until the reported issue is fixed (I
> heard you have access to the HW in question, so I am hopful :-).
Indeed :)
>
> Once the original issue is fixed, this can be applied of top if it was
> not found to be breaking anything.
Ok.
Sascha
--
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 |
prev parent reply other threads:[~2026-02-23 11:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-09 16:40 Ahmad Fatoum
2026-02-09 16:45 ` Ahmad Fatoum
2026-02-10 8:29 ` Michael Tretter
2026-02-23 11:37 ` Sascha Hauer
2026-02-23 11:40 ` Ahmad Fatoum
2026-02-23 11:41 ` Sascha Hauer [this message]
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=aZw89shLd9_le_l5@pengutronix.de \
--to=s.hauer@pengutronix.de \
--cc=a.fatoum@pengutronix.de \
--cc=barebox@lists.infradead.org \
--cc=m.tretter@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