public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Heiko Stuebner <heiko@sntech.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 4/4] dw_mmc: turn on the IO supply
Date: Tue, 02 Apr 2019 10:25:27 +0200	[thread overview]
Message-ID: <1691278.pilLj144Nr@phil> (raw)
In-Reply-To: <CAPCnQJ=o0+YDQJNzznnsxE104yq2pNgSTv1PQzcNTgb7=rrmLw@mail.gmail.com>

Am Sonntag, 31. März 2019, 21:45:15 CEST schrieb Urja Rannikko:
> Hi,
> 
> On Fri, Mar 29, 2019 at 2:09 PM Heiko Stübner <heiko@sntech.de> wrote:
> > > +#ifdef CONFIG_DM_REGULATOR
> >
> > this should be
> >         #if CONFIG_IS_ENABLED(DM_REGULATOR)
> 
> Ok, just FYI that fragment was based on the one in tmio-common.c,
> so maybe that should also be fixed(?).

yep, looks like it. While it doesn't cause compile errors right now,
it might after all create runtime errors otherwise.


Heiko


> >
> > because otherwise an SPL-build using the mmc driver may fail with
> >
> > drivers/mmc/dw_mmc.c: In function ‘dwmci_set_ios’:
> > drivers/mmc/dw_mmc.c:475:9: error: ‘struct mmc’ has no member named ‘vqmmc_supply’
> >   if (mmc->vqmmc_supply) {
> >          ^~
> > drivers/mmc/dw_mmc.c:477:27: error: ‘struct mmc’ has no member named ‘vqmmc_supply’
> >     regulator_set_value(mmc->vqmmc_supply, 1800000);
> >                            ^~
> > drivers/mmc/dw_mmc.c:479:27: error: ‘struct mmc’ has no member named ‘vqmmc_supply’
> >     regulator_set_value(mmc->vqmmc_supply, 3300000);
> >                            ^~
> > drivers/mmc/dw_mmc.c:481:44: error: ‘struct mmc’ has no member named ‘vqmmc_supply’
> >    ret = regulator_set_enable_if_allowed(mmc->vqmmc_supply, true);
> >
> >
> > > +     if (mmc->vqmmc_supply) {
> > > +             if (mmc->signal_voltage == MMC_SIGNAL_VOLTAGE_180)
> > > +                     regulator_set_value(mmc->vqmmc_supply, 1800000);
> > > +             else
> > > +                     regulator_set_value(mmc->vqmmc_supply, 3300000);
> > > +
> > > +             ret = regulator_set_enable_if_allowed(mmc->vqmmc_supply, true);
> > > +             if (ret)
> > > +                     return ret;
> > > +     }
> > > +#endif
> > > +
> > >       return 0;
> > >  }
> > >
> 
> 

  reply	other threads:[~2019-04-02  8:25 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-22 19:14 [U-Boot] [PATCH 0/4] Veyron Speedy / ASUS C201 fixes Urja Rannikko
2019-03-22 19:14 ` [U-Boot] [PATCH 1/4] pinctrl: exit pinconfig_post_bind if there are no subnodes Urja Rannikko
2019-03-30 21:18   ` Simon Glass
2019-04-21 18:41   ` [U-Boot] [U-Boot, " Philipp Tomsich
2019-04-23 14:33   ` Philipp Tomsich
2019-03-22 19:14 ` [U-Boot] [PATCH 2/4] rk3288-board: remove pinctrl call for debug uart Urja Rannikko
2019-03-30 21:18   ` Simon Glass
2019-03-31 21:54     ` Urja Rannikko
2019-04-21 18:41   ` [U-Boot] [U-Boot, " Philipp Tomsich
2019-04-23 14:33   ` Philipp Tomsich
2019-03-22 19:14 ` [U-Boot] [PATCH 3/4] rk3288-board: cosmetic: document selecting RK PWM Urja Rannikko
2019-03-30 21:18   ` Simon Glass
2019-03-31 21:46     ` Urja Rannikko
2019-03-22 19:14 ` [U-Boot] [PATCH 4/4] dw_mmc: turn on the IO supply Urja Rannikko
2019-03-29 14:09   ` Heiko Stübner
2019-03-31 19:45     ` Urja Rannikko
2019-04-02  8:25       ` Heiko Stuebner [this message]
2019-04-01 17:44   ` [U-Boot] [PATCH v2] " Urja Rannikko
2019-04-11 20:07     ` Urja Rannikko
2019-05-13 12:25       ` Urja Rannikko
2019-05-13 12:54     ` Heiko Stuebner
2019-05-13 13:25       ` [U-Boot] [PATCH v3] " Urja Rannikko
2019-05-18 16:08         ` Simon Glass
2019-05-20  7:03         ` Peng Fan
2019-07-26  7:06           ` Kever Yang
2019-07-30  0:47             ` Peng Fan
2019-03-29 13:56 ` [U-Boot] [PATCH 0/4] Veyron Speedy / ASUS C201 fixes Heiko Stübner
2019-03-31 19:34   ` Urja Rannikko
2019-03-31 20:44     ` Heiko Stübner
2019-03-31 22:19 ` Urja Rannikko
2019-04-11 20:14 ` Urja Rannikko

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=1691278.pilLj144Nr@phil \
    --to=heiko@sntech.de \
    --cc=u-boot@lists.denx.de \
    /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