From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Russell King - ARM Linux <linux@arm.linux.org.uk>
Cc: Linus Walleij <linus.walleij@stericsson.com>,
linux-mmc@vger.kernel.org, linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] mmci: supply per-instance regulator name
Date: Thu, 2 Dec 2010 13:08:09 +0000 [thread overview]
Message-ID: <20101202130809.GD859@rakim.wolfsonmicro.main> (raw)
In-Reply-To: <20101202122827.GG29347@n2100.arm.linux.org.uk>
On Thu, Dec 02, 2010 at 12:28:27PM +0000, Russell King - ARM Linux wrote:
> The way the MMCI code is, it only requests one regulator per AMBA
> device, and therefore only one regulator per struct device. So I
> don't think the current code needs changing in any way provided the
> struct device is used to find the corresponding regulator.
Hrm. In that case I'm not sure what the problem Linus' patch fixes is -
the driver is already requesting using the struct device, I was assuming
that the supplies weren't being requested in a fine grained enough
fashion.
WARNING: multiple messages have this Message-ID (diff)
From: broonie@opensource.wolfsonmicro.com (Mark Brown)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] mmci: supply per-instance regulator name
Date: Thu, 2 Dec 2010 13:08:09 +0000 [thread overview]
Message-ID: <20101202130809.GD859@rakim.wolfsonmicro.main> (raw)
In-Reply-To: <20101202122827.GG29347@n2100.arm.linux.org.uk>
On Thu, Dec 02, 2010 at 12:28:27PM +0000, Russell King - ARM Linux wrote:
> The way the MMCI code is, it only requests one regulator per AMBA
> device, and therefore only one regulator per struct device. So I
> don't think the current code needs changing in any way provided the
> struct device is used to find the corresponding regulator.
Hrm. In that case I'm not sure what the problem Linus' patch fixes is -
the driver is already requesting using the struct device, I was assuming
that the supplies weren't being requested in a fine grained enough
fashion.
next prev parent reply other threads:[~2010-12-02 13:08 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-02 11:35 [PATCH] mmci: supply per-instance regulator name Linus Walleij
2010-12-02 11:35 ` Linus Walleij
2010-12-02 11:57 ` Russell King - ARM Linux
2010-12-02 11:57 ` Russell King - ARM Linux
2010-12-02 12:06 ` Mark Brown
2010-12-02 12:06 ` Mark Brown
2010-12-02 12:03 ` Mark Brown
2010-12-02 12:03 ` Mark Brown
2010-12-02 12:28 ` Russell King - ARM Linux
2010-12-02 12:28 ` Russell King - ARM Linux
2010-12-02 13:08 ` Mark Brown [this message]
2010-12-02 13:08 ` Mark Brown
2010-12-02 13:23 ` Linus Walleij
2010-12-02 13:23 ` Linus Walleij
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=20101202130809.GD859@rakim.wolfsonmicro.main \
--to=broonie@opensource.wolfsonmicro.com \
--cc=linus.walleij@stericsson.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-mmc@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
/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.