From: "Karel Balej" <balejk@matfyz.cz>
To: "Adrian Hunter" <adrian.hunter@intel.com>,
"Ulf Hansson" <ulf.hansson@linaro.org>
Cc: phone-devel@vger.kernel.org,
~postmarketos/upstreaming@lists.sr.ht,
"Duje Mihanović" <duje.mihanovic@skole.hr>,
stable@vger.kernel.org, linux-mmc <linux-mmc@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
"Daniel Mack" <daniel@zonque.org>,
"Haojian Zhuang" <haojian.zhuang@gmail.com>,
"Robert Jarzmik" <robert.jarzmik@free.fr>,
"Jisheng Zhang" <jszhang@kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>
Subject: Re: [RFC PATCH] mmc: sdhci-pxav3: set NEED_RSP_BUSY capability
Date: Tue, 11 Mar 2025 12:25:56 +0100 [thread overview]
Message-ID: <D8DEEUPB16WF.154Y3AEPXT4L1@matfyz.cz> (raw)
In-Reply-To: <727c857f-0234-417b-af5d-69b3ae064d0f@intel.com>
Adrian Hunter, 2025-03-11T09:34:28+02:00:
> On 10/03/25 16:07, Karel Balej wrote:
>> Set the MMC_CAP_NEED_RSP_BUSY capability for the sdhci-pxav3 host to
>> prevent conversion of R1B responses to R1. Without this, the eMMC card
>> in the samsung,coreprimevelte smartphone using the Marvell PXA1908 SoC
>
> So that SoC is from 2015?
Rather at least 2014 as that's the release year of the phone.
> Is there anything more recent using this driver?
Looking at the in-tree DTs using the compatibles offered by it, it seems
that not really.
K. B.
next prev parent reply other threads:[~2025-03-11 11:27 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-10 14:07 [RFC PATCH] mmc: sdhci-pxav3: set NEED_RSP_BUSY capability Karel Balej
2025-03-11 7:34 ` Adrian Hunter
2025-03-11 11:25 ` Karel Balej [this message]
2025-03-14 13:50 ` Adrian Hunter
2025-03-15 16:18 ` Duje Mihanović
2025-03-17 10:51 ` Ulf Hansson
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=D8DEEUPB16WF.154Y3AEPXT4L1@matfyz.cz \
--to=balejk@matfyz.cz \
--cc=adrian.hunter@intel.com \
--cc=daniel@zonque.org \
--cc=duje.mihanovic@skole.hr \
--cc=haojian.zhuang@gmail.com \
--cc=jszhang@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mmc@vger.kernel.org \
--cc=phone-devel@vger.kernel.org \
--cc=robert.jarzmik@free.fr \
--cc=stable@vger.kernel.org \
--cc=ulf.hansson@linaro.org \
--cc=~postmarketos/upstreaming@lists.sr.ht \
/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