From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Adrian Hunter <adrian.hunter@intel.com>,
Ulf Hansson <ulf.hansson@linaro.org>
Cc: "linux-mmc@vger.kernel.org" <linux-mmc@vger.kernel.org>
Subject: Re: [PATCH v3] sdhci: Advertise 2.0v supply on SDIO host interface
Date: Thu, 11 Jan 2018 14:48:43 +0200 [thread overview]
Message-ID: <1515674923.7000.914.camel@linux.intel.com> (raw)
In-Reply-To: <78b0dccb-f9a9-8916-db4f-1473ec021c9a@intel.com>
On Thu, 2018-01-11 at 09:57 +0200, Adrian Hunter wrote:
> On 10/01/18 22:06, Ulf Hansson wrote:
> > On 10 January 2018 at 19:04, Andy Shevchenko
> > <andriy.shevchenko@linux.intel.com> wrote:
> > > On Wed, 2018-01-10 at 18:01 +0100, Ulf Hansson wrote:
> > > > On 10 January 2018 at 16:32, Andy Shevchenko
> > > > <andriy.shevchenko@linux.intel.com> wrote:
> > > > > On Intel Edison the Broadcom WiFi card, which is connected to
> > > > > SDIO,
> > > > > requires 2.0v, while the host, according to Intel Merrifield
> > > > > TRM,
> > > > > supports 1.8v supply only.
> > > > > + /*
> > > > > + * Without a regulator, SDHCI does not support 2.0v
> > > > > but we
> > > > > get
> > > > > + * here because we advertised 2.0v support for
> > > > > compatibility
> > > > > + * with the SDIO card's OCR. Map it to 1.8v for the
> > > > > purpose
> > > > > of
> > > > > + * turning on the power.
> > > > > + */
> > > > > + if (IS_ERR(host->mmc->supply.vmmc) && vdd ==
> > > > > ilog2(MMC_VDD_20_21))
> > > > > + vdd = ilog2(MMC_VDD_165_195);
> > > >
> > > > Why not instead extend the range in sdhci_set_power_noreg() to
> > > > also
> > > > check for MMC_VDD_20_21?
> > > >
> > > > Or is there a problem with that?
> > >
> > > Do we have any grounds to do this in generic code?
> > >
> > > Moreover, if we check for 2.0v what should we do in generic code?
> > > For my understanding
> > >
> > > case _20_21:
> > > pwr = _180;
> >
> > Yeah, why is that a problem?
>
> Shouldn't be a problem. Just add a comment:
>
> /*
> * Without a regulator, SDHCI does not support 2.0v so
> we only
> * get here if the driver deliberately added the 2.0v
> range to
> * ocr_avail. Map it to 1.8V for the purpose of turning
> on the
> * power.
> */
> case MMC_VDD_20_21:
> pwr = SDHCI_POWER_180;
> break;
OK.
I will send v4 soon after giving some testing.
> > What does other variants do in this regards?
>
> Use regulators or 3V I expect.
Yep, correct.
--
Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Intel Finland Oy
prev parent reply other threads:[~2018-01-11 12:59 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-10 15:32 [PATCH v3] sdhci: Advertise 2.0v supply on SDIO host interface Andy Shevchenko
2018-01-10 17:01 ` Ulf Hansson
2018-01-10 18:04 ` Andy Shevchenko
2018-01-10 20:06 ` Ulf Hansson
2018-01-10 20:16 ` Andy Shevchenko
2018-01-11 7:57 ` Adrian Hunter
2018-01-11 12:48 ` Andy Shevchenko [this message]
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=1515674923.7000.914.camel@linux.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=adrian.hunter@intel.com \
--cc=linux-mmc@vger.kernel.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.