From: adrian.hunter@intel.com (Adrian Hunter)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: tegra: beaver: allow SD card voltage to be changed
Date: Tue, 28 Jun 2016 16:27:29 +0300 [thread overview]
Message-ID: <57727B41.1080506@intel.com> (raw)
In-Reply-To: <576CF9F3.7090406@nvidia.com>
On 24/06/16 12:14, Jon Hunter wrote:
> Hi Adrian,
>
> On 14/06/16 15:19, Jon Hunter wrote:
>
> ...
>
>>>> So the controller itself supports UHS-I modes, but a given board may not
>>>> have the regulator to support them. We need a way to determine if the
>>>> board can support the UHS-I modes. Now we could check to see if the
>>>> regulator is present in the Tegra SDHCI driver and if not remove the cap
>>>> flags. However, I was not sure if this is applicable to other sdhci
>>>> controllers and so there should be a generic solution for this?
>>>
>>> There is SDHCI_QUIRK2_NO_1_8_V but it doesn't cover the eMMC 1.8V DDR52 case
>>> at present. Dong Aisheng wanted to plug that gap but I wanted to get rid of
>>> SDHCI_QUIRK2_NO_1_8_V:
>>>
>>> http://marc.info/?l=linux-mmc&m=146132847206423&w=2
>>
>> Ok, that would require the tegra sdhci driver to set this quirk for a
>> board, which is do-able, I guess. However, given the above I am not sure
>> what path you are suggesting we take to resolve this? Does not sound
>> like we should be looking at using SDHCI_QUIRK2_NO_1_8_V anyway.
>
> Any feedback here? Are you still planning to get rid of
> SDHCI_QUIRK2_NO_1_8_V or should we use this?
Don't use SDHCI_QUIRK2_NO_1_8_V.
I sent some patches that make it easier for drivers to do whatever they want:
http://marc.info/?l=linux-mmc&m=146712062816835
next prev parent reply other threads:[~2016-06-28 13:27 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-29 21:01 [PATCH] ARM: tegra: beaver: allow SD card voltage to be changed Lucas Stach
2016-05-13 7:25 ` Lucas Stach
2016-05-13 17:27 ` Thierry Reding
2016-05-13 19:08 ` Lucas Stach
2016-05-19 14:29 ` Jon Hunter
2016-06-13 10:22 ` Jon Hunter
2016-06-14 6:20 ` Adrian Hunter
2016-06-14 8:23 ` Jon Hunter
2016-06-14 10:05 ` Adrian Hunter
2016-06-14 14:19 ` Jon Hunter
2016-06-24 9:14 ` Jon Hunter
2016-06-28 13:27 ` Adrian Hunter [this message]
2016-05-19 14:31 ` Jon Hunter
2016-05-19 16:12 ` Stephen Warren
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=57727B41.1080506@intel.com \
--to=adrian.hunter@intel.com \
--cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).