From: Ulf Hansson <ulf.hansson@linaro.org>
To: Stefan Agner <stefan@agner.ch>
Cc: Adrian Hunter <adrian.hunter@intel.com>,
Fabio Estevam <fabio.estevam@nxp.com>,
Haibo Chen <haibo.chen@nxp.com>,
Aisheng Dong <aisheng.dong@nxp.com>,
Michael Trimarchi <michael@amarulasolutions.com>,
Russell King <rmk+kernel@armlinux.org.uk>,
"linux-mmc@vger.kernel.org" <linux-mmc@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2] mmc: sdhci-esdhc-imx: allow 1.8V modes without 100/200MHz pinctrl states
Date: Thu, 5 Jul 2018 13:29:48 +0200 [thread overview]
Message-ID: <CAPDyKFpWzWeXxDfHXpFBboCtJKH97pPotTcmuFigZhET7zA26g@mail.gmail.com> (raw)
In-Reply-To: <69f6122b8a69f1ab41d2ef8274321689@agner.ch>
[...]
>>> Btw, I still get the switching error once during boot-up:
>>> mmc1: Switching to 3.3V signalling voltage failed
>>
>> I guess the this happens then also at system resume?
>>
>> The core tries first with 3.3 then if it fails, it continues with 1.8V, etc.
>>
>>>
>>> This is due to the call from mmc_set_initial_signal_voltage. It is a bit
>>> unfortunate since this is printed as a warning. Not sure if that could
>>> be prevented somehow?
>>
>> Seems like SDHCI_SIGNALING_330 should not be set, unless 3.3V I/O is
>> supported. That should avoid SDHCI from trying and instead just
>> returning an error code immediately.
>>
>> This seems like a generic issues for all SDHCI variant drivers.
>
> Hm, can we resolve this in a generic fashion?
>
> E.g something like this in sdhci_setup_host():
>
> if (!regulator_is_supported_voltage(mmc->supply.vqmmc, 3200000,
> 3450000))
> host->flags &= ~SDHCI_SIGNALING_330;
Something like that seems right, but a wider range should be allowed.
2.7V to 3.6V is allowed according to the specs.
Also, vqmmc is optional, so in case it doesn't exist we must not clear
the SDHCI_SIGNALING_330 bit.
Kind regards
Uffe
next prev parent reply other threads:[~2018-07-05 11:29 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-04 15:07 [PATCH v2] mmc: sdhci-esdhc-imx: allow 1.8V modes without 100/200MHz pinctrl states Stefan Agner
2018-07-04 15:18 ` Stefan Agner
2018-07-05 9:48 ` Ulf Hansson
2018-07-05 11:22 ` Stefan Agner
2018-07-05 11:29 ` Ulf Hansson [this message]
2018-07-05 2:40 ` A.s. Dong
2018-07-05 7:18 ` Stefan Agner
2018-07-05 11:23 ` Ulf Hansson
2018-07-05 11:43 ` Stefan Agner
2018-07-05 13:10 ` Ulf Hansson
2018-07-05 14:22 ` Stefan Agner
2018-07-09 11:31 ` 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=CAPDyKFpWzWeXxDfHXpFBboCtJKH97pPotTcmuFigZhET7zA26g@mail.gmail.com \
--to=ulf.hansson@linaro.org \
--cc=adrian.hunter@intel.com \
--cc=aisheng.dong@nxp.com \
--cc=fabio.estevam@nxp.com \
--cc=haibo.chen@nxp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mmc@vger.kernel.org \
--cc=michael@amarulasolutions.com \
--cc=rmk+kernel@armlinux.org.uk \
--cc=stefan@agner.ch \
/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;
as well as URLs for NNTP newsgroup(s).