From: NeilBrown <neil@brown.name>
To: Chaotian Jing <chaotian.jing@mediatek.com>
Cc: Ulf Hansson <ulf.hansson@linaro.org>,
linux-mmc@vger.kernel.org, linux-kernel@vger.kernel.org,
thirtythreeforty@gmail.com
Subject: Re: [PATCH 4/5] mmc: mtk-sd: enable internal card-detect logic.
Date: Sat, 04 May 2019 18:18:31 +1000 [thread overview]
Message-ID: <87o94i3a5k.fsf@notabene.neil.brown.name> (raw)
In-Reply-To: <1555569583.18628.29.camel@mhfsdcap03>
[-- Attachment #1: Type: text/plain, Size: 1099 bytes --]
On Thu, Apr 18 2019, Chaotian Jing wrote:
> On Tue, 2019-04-16 at 14:47 +1000, NeilBrown wrote:
>> The mtk-sd silicon has integrated card-detect logic that is
>> enabled, at least, on the MT7621 as used in the GNUBEE NAS.
>>
>> If the sdhci isn't marked non-removable and doesn't have a
>> cd-gpio configured, assume the internal cd logic should be used.
>>
>> Signed-off-by: NeilBrown <neil@brown.name>
...
>> @@ -2206,6 +2247,15 @@ static int msdc_drv_probe(struct platform_device *pdev)
>> goto host_free;
>> }
>>
>> + if (!(mmc->caps & MMC_CAP_NONREMOVABLE) &&
>> + !mmc_can_gpio_cd(mmc)) {
>
> Should not do this assume!
> better to add "mediatek,internal-cd" in your DTS, then no impact to
> other Soc.
(Sorry for the delay).
Documentation/devicetree/bindings/mmc/mmc.txt
says:
If no property below is supplied, host native card detect is used.
So this assumption is *exactly* what the documentation said we should
do.
How about I limit this assumption to mt7621 using a flag in the
mtk_mmc_compatible structure?
Thanks,
NeilBrown
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]
next prev parent reply other threads:[~2019-05-04 8:18 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-16 4:47 [PATCH 0/5] mtk-sd enhancement to support MT7621 NeilBrown
2019-04-16 4:47 ` [PATCH 5/5] mmc: mtk-sd: enable internal write-protect logic NeilBrown
2019-04-16 4:47 ` [PATCH 4/5] mmc: mtk-sd: enable internal card-detect logic NeilBrown
2019-04-18 6:39 ` Chaotian Jing
2019-05-04 8:18 ` NeilBrown [this message]
2019-04-16 4:47 ` [PATCH 2/5] mmc: mtk-sd: don't hard-code interrupt trigger type NeilBrown
2019-04-16 8:11 ` Chaotian Jing
2019-04-16 22:12 ` NeilBrown
2019-04-18 6:36 ` Chaotian Jing
2019-04-16 4:47 ` [PATCH 3/5] mmc: mtk-sd: add support for config found in mt7620 family SOCs NeilBrown
2019-04-16 4:47 ` [PATCH 1/5] mmc: mtk-sd: support "voltage-ranges" setting NeilBrown
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=87o94i3a5k.fsf@notabene.neil.brown.name \
--to=neil@brown.name \
--cc=chaotian.jing@mediatek.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mmc@vger.kernel.org \
--cc=thirtythreeforty@gmail.com \
--cc=ulf.hansson@linaro.org \
/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