From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Felipe Balbi <balbi@ti.com>
Cc: Tero Kristo <t-kristo@ti.com>, linux-omap@vger.kernel.org, lrg@ti.com
Subject: Re: [RFC 0/4] TWL external controller support
Date: Sat, 9 Jul 2011 19:56:51 +0900 [thread overview]
Message-ID: <20110709105649.GA17036@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <20110709104007.GM31978@legolas.emea.dhcp.ti.com>
On Sat, Jul 09, 2011 at 01:40:08PM +0300, Felipe Balbi wrote:
> a hack for a hack... what's the difference ? If it's only to solve a
> limitation temporarily anyways... although it would be better to discuss
> how to add such support to the framework already.
I'm completely unable to identify an issue in the framework that this
patch addresses - the API already supports multiple devices supplying
regulators, it's extremely difficult to understand what motivates the
change.
next prev parent reply other threads:[~2011-07-09 10:56 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-08 15:56 [RFC 0/4] TWL external controller support Tero Kristo
2011-07-08 15:56 ` [RFC 1/4] twl-regulator: extend for SMPS regulators and external controllers Tero Kristo
2011-07-08 18:26 ` Liam Girdwood
2011-07-09 1:21 ` Mark Brown
2011-07-08 15:56 ` [RFC 2/4] omap3beagle: Instantiate VDD1 and VDD2 regulators Tero Kristo
2011-07-08 16:22 ` Felipe Balbi
2011-07-08 15:56 ` [RFC 3/4] omap: attach external controller to VDD1/VDD2 Tero Kristo
2011-07-08 16:23 ` Felipe Balbi
2011-07-08 15:56 ` [RFC 4/4] OMAP3: beagle rev-c4: enable OPP6 Tero Kristo
2011-07-08 16:23 ` Koen Kooi
2011-07-08 16:25 ` [RFC 0/4] TWL external controller support Felipe Balbi
2011-07-09 1:24 ` Mark Brown
2011-07-09 10:40 ` Felipe Balbi
2011-07-09 10:56 ` Mark Brown [this message]
2011-07-11 8:23 ` Tero Kristo
2011-07-11 10:05 ` Mark Brown
2011-07-11 10:48 ` Tero Kristo
2011-07-11 12:11 ` Mark Brown
2011-07-11 13:06 ` Tero Kristo
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=20110709105649.GA17036@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=balbi@ti.com \
--cc=linux-omap@vger.kernel.org \
--cc=lrg@ti.com \
--cc=t-kristo@ti.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 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.