mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Mark Brown <broonie@kernel.org>
To: "Kim, Milo" <Milo.Kim@ti.com>
Cc: Liam Girdwood <lgirdwood@gmail.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2] regulator: lp872x: support the device tree feature
Date: Thu, 16 May 2013 19:46:27 +0400	[thread overview]
Message-ID: <20130516154627.GN24524@sirena.org.uk> (raw)
In-Reply-To: <A874F61F95741C4A9BA573A70FE3998F82E5CF3D@DQHE06.ent.ti.com>

[-- Attachment #1: Type: text/plain, Size: 1386 bytes --]

On Fri, May 10, 2013 at 07:17:48AM +0000, Kim, Milo wrote:

> Patch v2.
>   Move the opmode code of the device tree from 'of_regulator' to the lp872x
>   because its mode depends on the device.
>   Supported modes in LP8720/5 are 'fast' and 'normal'.

> Patch v1.
>   Initial patch

Please keep these changelogs after the --- so they don't get included in
the final changelog by git am.

> +Optional properties:
> +- general-config: the value of LP872X_GENERAL_CFG register (u8)
> +- update-config: define it when LP872X_GENERAL_CFG register should be updated

A bit more information on this one wouldn't hurt but the information
will be in the datasheet I guess.

> +- dvs-gpio: GPIO number for DVS control

If this is the AP side GPIO then it ought to be a standard GPIO
specifier rather than a GPIO number.  If this is the pin on the PMIC
then it probably ought to be spelled out a bit more clearly.

> +- dvs-vsel: DVS selector. 0 = SEL_V1, 1 = SEL_V2.
> +- dvs-state: initial DVS pin state. 0 = DVS_LOG, 1 = DVS_HIGH.

Any custom properties are supposed to be namespaced, for example
"ti,general-config".

> +Child node
> +- regulator-id: the value of enum lp872x_regulator_id. (u8)

These would need to be listed as part of the binding, though it'd be
much more friendly to use plain text names and of_regulator_match() to
look them up.  That makes the binding much more legible.

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

      reply	other threads:[~2013-05-16 15:47 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-10  7:17 Kim, Milo
2013-05-16 15:46 ` 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=20130516154627.GN24524@sirena.org.uk \
    --to=broonie@kernel.org \
    --cc=Milo.Kim@ti.com \
    --cc=lgirdwood@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    /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®