From: Guenter Roeck <linux@roeck-us.net>
To: Mark Brown <broonie@kernel.org>
Cc: atull <atull@opensource.altera.com>,
jdelvare@suse.de, lm-sensors@lm-sensors.org, lgirdwood@gmail.com,
linux-kernel@vger.kernel.org, delicious.quinoa@gmail.com,
dinguyen@opensource.altera.com, yvanderv@opensource.altera.com
Subject: Re: [PATCH v3 3/3] pmbus: ltc2978: add regulator support
Date: Wed, 24 Sep 2014 15:55:46 -0700 [thread overview]
Message-ID: <54234BF2.6040404@roeck-us.net> (raw)
In-Reply-To: <20140924223322.GL16977@sirena.org.uk>
On 09/24/2014 03:33 PM, Mark Brown wrote:
> On Wed, Sep 24, 2014 at 02:13:32PM -0700, Guenter Roeck wrote:
>> On Wed, Sep 24, 2014 at 03:48:40PM -0500, atull wrote:
>
>>>> regulator.47/name:vout_en0
>
>>> These are just default names, but I think I could make the name better.
>>> How about <part #>-<i2c address>-vout<#> such as "ltc2978-5c-vout0"
>
>> Problem with that is that i2c bus numbers are not static, which would
>> make it quite difficult to describe the regulator in devicetree data.
>
>> Any idea what other regulators do in such situations ?
>
> What's there is correct (modulo the _en), the names are local to the
> chip. If the user actually cares they will be providing the name of the
> supply on the board anyway.
>
Great, thanks a lot.
Guenter
prev parent reply other threads:[~2014-09-24 22:55 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-24 17:57 [PATCH v3 0/3] regulator support for pmbus and ltc2978 atull
2014-09-24 17:57 ` [PATCH v3 1/3] pmbus: core: add helpers for byte write and read modify write atull
2014-09-24 17:57 ` [PATCH v3 2/3] pmbus: add regulator support atull
2014-09-24 19:41 ` Dinh Nguyen
2014-09-24 21:08 ` atull
2014-09-24 19:58 ` Guenter Roeck
2014-09-24 21:06 ` atull
2014-09-24 21:22 ` Guenter Roeck
2014-09-24 17:57 ` [PATCH v3 3/3] pmbus: ltc2978: " atull
2014-09-24 20:19 ` Guenter Roeck
2014-09-24 20:48 ` atull
2014-09-24 21:13 ` Guenter Roeck
2014-09-24 22:33 ` Mark Brown
2014-09-24 22:55 ` Guenter Roeck [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=54234BF2.6040404@roeck-us.net \
--to=linux@roeck-us.net \
--cc=atull@opensource.altera.com \
--cc=broonie@kernel.org \
--cc=delicious.quinoa@gmail.com \
--cc=dinguyen@opensource.altera.com \
--cc=jdelvare@suse.de \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lm-sensors@lm-sensors.org \
--cc=yvanderv@opensource.altera.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