From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Russell King - ARM Linux <linux@arm.linux.org.uk>
Cc: Tony Lindgren <tony@atomide.com>,
linux-arm-kernel@lists.arm.linux.org.uk,
David Brownell <dbrownell@users.sourceforge.net>,
linux-omap@vger.kernel.org
Subject: Re: [PATCH 2/8] ARM: OMAP3: Initialize regulators for Beagle and Overo
Date: Fri, 29 May 2009 11:05:26 +0100 [thread overview]
Message-ID: <20090529100525.GC13820@sirena.org.uk> (raw)
In-Reply-To: <20090528194834.GV20736@n2100.arm.linux.org.uk>
On Thu, May 28, 2009 at 08:48:34PM +0100, Russell King - ARM Linux wrote:
> On Thu, May 28, 2009 at 07:00:13PM +0100, Mark Brown wrote:
> > Eh, no, not really. It's the same as the clock API in this regard - if
> > you want the struct device can be NULL and you can do a name based
> > lookup only but then you have to pass the name around in platform data
> > to support configurability. If the clock API implements some other
> > solutions we'll probably follow them but I'm not aware of any.
> That's not quite what we're talking about. With clkdev, you specify
> device name itself, rather than address-of-struct-device. Using the
> device name gives you independence from the initialization or creation
> of the struct device (if indeed the struct device is created at all.)
Hrm, that does seem like a neat approach for avoiding the problems with
buses like I2C - I'll look into adding support for it, but at this point
it's not likely to be in time for the next merge window. Thanks!
next prev parent reply other threads:[~2009-05-29 10:05 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-25 17:46 [PATCH 0/8] omap3 board updates for merge window after 2.6.30 Tony Lindgren
2009-05-25 17:48 ` [PATCH 1/8] ARM: OMAP3: mmc-twl4030 uses regulator framework Tony Lindgren
2009-05-25 22:47 ` Daniel Ribeiro
2009-05-26 12:59 ` Mark Brown
2009-05-27 16:55 ` [PATCH 1/8] ARM: OMAP3: mmc-twl4030 uses regulator framework, v2 Tony Lindgren
2009-05-25 17:49 ` [PATCH 2/8] ARM: OMAP3: Initialize regulators for Beagle and Overo Tony Lindgren
2009-05-28 16:20 ` Russell King - ARM Linux
2009-05-28 17:33 ` Tony Lindgren
2009-05-28 18:00 ` Mark Brown
2009-05-28 19:48 ` Russell King - ARM Linux
2009-05-29 10:05 ` Mark Brown [this message]
2009-05-25 17:51 ` [PATCH 3/8] ARM: OMAP3: pandora: setup regulator framework for MMC Tony Lindgren
2009-05-25 17:52 ` [PATCH 4/8] ARM: OMAP3: RX51: Connect VAUX3 to MMC2 Tony Lindgren
2009-05-25 17:53 ` [PATCH 5/8] ARM: OMAP3: Add support for OMAP3 Zoom2 board Tony Lindgren
2009-05-28 16:05 ` Russell King - ARM Linux
2009-05-28 21:13 ` [PATCH 5/8] ARM: OMAP3: Add support for OMAP3 Zoom2 board, v2 Tony Lindgren
2009-05-28 21:16 ` Russell King - ARM Linux
2009-05-28 21:39 ` Tony Lindgren
2009-05-25 17:55 ` [PATCH 6/8] ARM: OMAP3: Defconfig for Zoom2 board Tony Lindgren
2009-05-25 17:56 ` [PATCH 7/8] ARM: OMAP3: Add omap3 EVM support Tony Lindgren
2009-05-28 16:06 ` Russell King - ARM Linux
2009-05-28 21:14 ` [PATCH 7/8] ARM: OMAP3: Add omap3 EVM support, v2 Tony Lindgren
2009-05-25 17:57 ` [PATCH 8/8] ARM: OMAP3: Add omap3 EVM defconfig Tony Lindgren
2009-05-27 19:47 ` [PATCH] ARM: OMAP3: pandora: add support for mode devices Grazvydas Ignotas
2009-05-27 20:24 ` Tony Lindgren
2009-05-27 23:39 ` [PATCH 0/8] omap3 board updates for merge window after 2.6.30 Tony Lindgren
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=20090529100525.GC13820@sirena.org.uk \
--to=broonie@opensource.wolfsonmicro.com \
--cc=dbrownell@users.sourceforge.net \
--cc=linux-arm-kernel@lists.arm.linux.org.uk \
--cc=linux-omap@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=tony@atomide.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