From: Jonathan Cameron <Jonathan.Cameron@gmail.com>
To: Mark Brown <broonie@opensource.wolfsonmicro.com>
Cc: Liam Girdwood <lrg@slimlogic.co.uk>,
linux-kernel@vger.kernel.org, Mike Rapoport <mike@compulab.co.il>
Subject: Re: [PATCH] regulator: Allow consumer supplies to be set up with dev_name()
Date: Thu, 25 Jun 2009 13:11:46 +0000 [thread overview]
Message-ID: <4A437792.6040009@gmail.com> (raw)
In-Reply-To: <1245257799-29752-1-git-send-email-broonie@opensource.wolfsonmicro.com>
Mark Brown wrote:
> Follow the approach suggested by Russell King and implemented by him in
> the clkdev API and allow consumer device supply mapings to be set up
> using the dev_name() for the consumer instead of the struct device.
> In order to avoid making existing machines instabuggy and creating merge
> issues the use of struct device is still supported for the time being.
>
> This resolves problems working with buses such as I2C which make the
> struct device available late providing that the final device name is
> known, which is the case for most embedded systems with fixed setups.
>
> Consumers must still use the struct device when calling regulator_get().
>
>
Hi,
This patch is an excellent solution to the problem.
I just wonder if we need to suggest subsystem maintainers make sure that
their
device names are suitably unique and identifiable? For example, i2c device
tend to have names like 0-0032. Perhaps we need something to identify
that they
are indeed i2c devices?
For that matter, is there anything other than blind luck preventing two
regulator
consumers having the same dev_name?
---
Jonathan Cameron
next prev parent reply other threads:[~2009-06-25 13:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-17 16:56 Mark Brown
2009-06-18 10:54 ` Liam Girdwood
2009-06-18 11:00 ` Mark Brown
2009-06-25 13:11 ` Jonathan Cameron [this message]
2009-06-25 13:16 ` 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=4A437792.6040009@gmail.com \
--to=jonathan.cameron@gmail.com \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lrg@slimlogic.co.uk \
--cc=mike@compulab.co.il \
/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®