mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: <orito.takao@socionext.com>
To: <ulf.hansson@linaro.org>
Cc: <robh+dt@kernel.org>, <mark.rutland@arm.com>,
	<linux-mmc@vger.kernel.org>, <devicetree@vger.kernel.org>,
	<linux-kernel@vger.kernel.org>, <masami.hiramatsu@linaro.org>,
	<jaswinder.singh@linaro.org>, <sugaya.taichi@socionext.com>,
	<kasai.kazuhiro@socionext.com>, <kanematsu.shinji@socionext.com>
Subject: Re: [PATCH 2/2] mmc: sdhci-milbeaut: add Milbeaut SD controller driver
Date: Tue, 7 May 2019 09:18:40 +0000	[thread overview]
Message-ID: <20190507181831.9D75.F0D17A80@socionext.com> (raw)
In-Reply-To: <CAPDyKFrBJeBNOPh9H3Yn-6-um2B-9Gt6_pW8Qh0ZGQB26-tq+Q@mail.gmail.com>


Thank you for reviewing my patches.

> [...]
> 
> > +
> > +static void sdhci_milbeaut_power_off(struct sdhci_host *host)
> > +{
> > +       struct f_sdhost_priv *priv = sdhci_priv(host);
> > +
> > +       gpiod_set_value(priv->power_gpio, 0);
> > +       udelay(1000);
> > +}
> > +
> > +static void sdhci_milbeaut_power_on(struct sdhci_host *host)
> > +{
> > +       struct f_sdhost_priv *priv = sdhci_priv(host);
> > +
> > +       gpiod_set_value(priv->power_gpio, 1);
> > +}
> > +
> 
> As stated for the DT doc patch, please use a fixed GPIO regulator
> instead. In this way you will also get a the OCR mask based upon the
> GPIO regulator, which is parsed out by the mmc core when sdhci calls
> mmc_regulator_get_supply().

I see. I will update this part too at the view point of using regurator.

Thanks
Orito

> 
> Otherwise, this looks good to me.
> 
> [...]
> 
> Kind regards
> Uffe

-- 
Takao Orito <orito.takao@socionext.com>

      reply	other threads:[~2019-05-07  9:18 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-26  2:06 Takao Orito
2019-04-29 10:31 ` Ulf Hansson
2019-05-07  9:18   ` orito.takao [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=20190507181831.9D75.F0D17A80@socionext.com \
    --to=orito.takao@socionext.com \
    --cc=devicetree@vger.kernel.org \
    --cc=jaswinder.singh@linaro.org \
    --cc=kanematsu.shinji@socionext.com \
    --cc=kasai.kazuhiro@socionext.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mmc@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=masami.hiramatsu@linaro.org \
    --cc=robh+dt@kernel.org \
    --cc=sugaya.taichi@socionext.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

all inboxes | Powered by JetHome®