From: Mark Brown <broonie@sirena.org.uk>
To: dbrownell@users.sourceforge.net
Cc: lrg@slimlogic.co.uk, lkml <linux-kernel@vger.kernel.org>
Subject: Re: [patch 2.6.28-rc7] regulator: catch some registration errors
Date: Tue, 6 Jan 2009 12:58:59 +0000 [thread overview]
Message-ID: <20090106125858.GE6783@sirena.org.uk> (raw)
In-Reply-To: <200901060221.26614.david-b@pacbell.net>
On Tue, Jan 06, 2009 at 02:21:26AM -0800, David Brownell wrote:
> On Tuesday 06 January 2009, Mark Brown wrote:
> > [ Long URL for your i.MX3 cpufreq driver elided ]
> Right, and what's keeping you from providing a "struct device *"
> for that to use?
Well, clearly it can be done but I'd expect review issues from having
the architectures provide a half done representation of the CPU in the
device tree that's essentially private to the cpufreq driver (and then
has no tie in with cpufreq itself).
Personally, I'd be much happier to require a device if there were some
agreement about how CPUs should be done in the device model - at the
minute it all seems very ad-hoc where it's done at all. For the time
being I'd prefer to bodge in a device for doing printouts in the
regulator core rather than forcing users to have a device when we don't
have a clear story on what to use. Neither approach is particularly nice.
next prev parent reply other threads:[~2009-01-06 12:59 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-01 21:35 [patch 2.6.28-rc6+] regulator: bugfixes and messaging cleanup David Brownell
2008-12-01 22:53 ` Mark Brown
2008-12-01 23:58 ` David Brownell
2008-12-02 1:22 ` Mark Brown
2008-12-02 5:50 ` [patch 2.6.28-rc7] regulator: init/link earlier David Brownell
2008-12-02 10:51 ` Mark Brown
2008-12-03 21:45 ` Liam Girdwood
2008-12-02 5:50 ` [patch 2.6.28-rc7] regulator: catch some registration errors David Brownell
2008-12-02 13:32 ` Mark Brown
2009-01-05 23:45 ` David Brownell
2009-01-06 10:10 ` Mark Brown
2009-01-06 10:21 ` David Brownell
2009-01-06 12:58 ` Mark Brown [this message]
2008-12-03 21:48 ` Liam Girdwood
2008-12-04 11:12 ` Mark Brown
2009-01-05 23:45 ` David Brownell
2009-01-06 10:33 ` Mark Brown
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=20090106125858.GE6783@sirena.org.uk \
--to=broonie@sirena.org.uk \
--cc=dbrownell@users.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=lrg@slimlogic.co.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®