From: Stefan Agner <stefan@agner.ch>
To: Ulf Hansson <ulf.hansson@linaro.org>
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 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, 05 Jul 2018 13:43:47 +0200 [thread overview]
Message-ID: <a0c658d298aa8254b0ceb514793608ae@agner.ch> (raw)
In-Reply-To: <CAPDyKFovmZxR=Bv0rogas+RTkzkSwbcyRyu1pD4m0LYvExbY8A@mail.gmail.com>
On 05.07.2018 13:23, Ulf Hansson wrote:
> On 4 July 2018 at 17:07, Stefan Agner <stefan@agner.ch> wrote:
>> If pinctrl nodes for 100/200MHz are missing, the controller should
>> not select any mode which need signal frequencies 100MHz or higher.
>> To prevent such speed modes the driver currently uses the quirk flag
>> SDHCI_QUIRK2_NO_1_8_V. This works nicely for SD cards since 1.8V
>> signaling is required for all faster modes and slower modes use 3.3V
>> signaling only.
>>
>> However, there are eMMC modes which use 1.8V signaling and run below
>> 100MHz, e.g. DDR52 at 1.8V. With using SDHCI_QUIRK2_NO_1_8_V this
>> mode is prevented. When using a fixed 1.8V regulator as vqmmc-supply
>> the stack has no valid mode to use. In this tenuous situation the
>> kernel continuously prints voltage switching errors:
>> mmc1: Switching to 3.3V signalling voltage failed
>>
>> Avoid using SDHCI_QUIRK2_NO_1_8_V and prevent faster modes by
>> altering the SDHCI capability register. With that the stack is able
>> to select 1.8V modes even if no faster pinctrl states are available:
>> # cat /sys/kernel/debug/mmc1/ios
>> ...
>> timing spec: 8 (mmc DDR52)
>> signal voltage: 1 (1.80 V)
>> ...
>>
>> Link: http://lkml.kernel.org/r/20180628081331.13051-1-stefan@agner.ch
>> Signed-off-by: Stefan Agner <stefan@agner.ch>
>
> I am fine with this. Do you want me to apply this for now, to get it tested?
>
Yes.
> I guess its also material for stable and as fix?
>
I guess. We probably want to wait until it gets some more testing?
> In regards to the printed warning, it sounds to me like a different
> issue, which we can solve on top. Right?
Yes different issue, which we can handle separately.
--
Stefan
next prev parent reply other threads:[~2018-07-05 11:43 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-04 15:07 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
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 [this message]
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=a0c658d298aa8254b0ceb514793608ae@agner.ch \
--to=stefan@agner.ch \
--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=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
Powered by JetHome