linux-mtd.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Pawel Moll <pawel.moll@arm.com>
Cc: Artem Bityutskiy <Artem.Bityutskiy@linux.intel.com>,
	"linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>,
	David Woodhouse <dwmw2@infradead.org>
Subject: Re: [PATCH v2 1/2] mtd: maps: physmap: Add VPP regulator control
Date: Mon, 23 Jul 2012 20:12:18 +0100	[thread overview]
Message-ID: <20120723191218.GC12438@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <1343070299.19880.41.camel@hornet>

[-- Attachment #1: Type: text/plain, Size: 975 bytes --]

On Mon, Jul 23, 2012 at 08:04:59PM +0100, Pawel Moll wrote:
> On Mon, 2012-07-23 at 19:45 +0100, Mark Brown wrote:

> #ifdef CONFIG_REGULATOR
>         /* If we're using the regulator framework, try to fetch a regulator */
>         host->vcc = regulator_get(&dev->dev, "vmmc");
>         if (IS_ERR(host->vcc))
>                 host->vcc = NULL;
>         else {
>                 int mask = mmc_regulator_get_ocrmask(host->vcc);

Oh, yeah.  Well, MMC regulator integration has historically been
entertaining so I guess any move towards standardisation is good :/

> > It'll happen if anyone does the work; I've not currently got any useful
> > systems that run DT and don't have a particularly large amount of spare
> > time.  People were muttering about it, though, for much the reasons you
> > mentioned.

> Ok, I take the hint, will look into it.

That'd be great, people were really talking about it so it may be that
someone will get to it soon, I don't know though.

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

  reply	other threads:[~2012-07-23 19:12 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-18 13:21 [PATCH v2 0/2] Regulator control of physmap-ed chip's VPP Pawel Moll
2012-07-18 13:22 ` [PATCH v2 1/2] mtd: maps: physmap: Add VPP regulator control Pawel Moll
2012-07-23 17:46   ` Mark Brown
2012-07-23 18:24     ` Pawel Moll
2012-07-23 18:32       ` Mark Brown
2012-07-23 18:42         ` Pawel Moll
2012-07-23 18:45           ` Mark Brown
2012-07-23 19:04             ` Pawel Moll
2012-07-23 19:12               ` Mark Brown [this message]
2012-07-18 13:22 ` [PATCH 2/2] mtd: maps: physmap_of: " Pawel Moll
2012-07-18 16:02 ` [PATCH v2 0/2] Regulator control of physmap-ed chip's VPP Artem Bityutskiy

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=20120723191218.GC12438@opensource.wolfsonmicro.com \
    --to=broonie@opensource.wolfsonmicro.com \
    --cc=Artem.Bityutskiy@linux.intel.com \
    --cc=dwmw2@infradead.org \
    --cc=linux-mtd@lists.infradead.org \
    --cc=pawel.moll@arm.com \
    /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).