From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Jonathan Cameron <Jonathan.Cameron@gmail.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 14:16:25 +0100 [thread overview]
Message-ID: <20090625131625.GC17690@sirena.org.uk> (raw)
In-Reply-To: <4A437792.6040009@gmail.com>
On Thu, Jun 25, 2009 at 01:11:46PM +0000, Jonathan Cameron wrote:
> 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?
Either that or if it becomes a problem we add the ability to match on
bus type as well - since bus type already exists it'd probably be better
to go down that road rather than cause userspace-visible changes. I've
not looked in sufficient detail to confirm that this would cover
everything but I believe it should.
> For that matter, is there anything other than blind luck preventing two
> regulator
> consumers having the same dev_name?
Due to sysfs requirements I think we should be safe with the addition of
bus type matching but like I say I may be missing something.
prev parent reply other threads:[~2009-06-25 13:16 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
2009-06-25 13:16 ` Mark Brown [this message]
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=20090625131625.GC17690@sirena.org.uk \
--to=broonie@opensource.wolfsonmicro.com \
--cc=Jonathan.Cameron@gmail.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®