public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Jean-Christophe PLAGNIOL-VILLARD <plagnioj@jcrosoft.com>
Cc: "Ying-Chun Liu (PaulLiu)" <paul.liu@linaro.org>,
	linux-arm-kernel@lists.infradead.org,
	linaro-dev@lists.linaro.org, Samuel Ortiz <sameo@linux.intel.com>,
	patches@linaro.org, linux-kernel@vger.kernel.org,
	Liam Girdwood <lrg@ti.com>, Nancy Chen <Nancy.Chen@freescale.com>
Subject: Re: [PATCH v9] Regulator: Add Anatop regulator driver
Date: Wed, 7 Mar 2012 13:45:52 +0000	[thread overview]
Message-ID: <20120307134551.GL3107@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <20120307132225.GB17745@game.jcrosoft.org>

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

On Wed, Mar 07, 2012 at 02:22:25PM +0100, Jean-Christophe PLAGNIOL-VILLARD wrote:

> > +- compatible: Must be "fsl,anatop-regulator"
> > +- vol-bit-shift: Bit shift for the register
> > +- vol-bit-width: Number of bits used in the register
> > +- min-bit-val: Minimum value of this register
> > +- min-voltage: Minimum voltage of this regulator
> > +- max-voltage: Maximum voltage of this regulator

> specific properites need to be prefix by the vendor

This really doesn't seem at all sane for a device which is already
vendor specific, it's just noise in the bindings.

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

  reply	other threads:[~2012-03-07 13:45 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-07 13:24 [PATCH v9] Regulator: Add Anatop regulator driver Ying-Chun Liu (PaulLiu)
2012-03-07 13:22 ` Jean-Christophe PLAGNIOL-VILLARD
2012-03-07 13:45   ` Mark Brown [this message]
2012-03-07 15:36     ` Jean-Christophe PLAGNIOL-VILLARD
2012-03-07 16:28       ` 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=20120307134551.GL3107@opensource.wolfsonmicro.com \
    --to=broonie@opensource.wolfsonmicro.com \
    --cc=Nancy.Chen@freescale.com \
    --cc=linaro-dev@lists.linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lrg@ti.com \
    --cc=patches@linaro.org \
    --cc=paul.liu@linaro.org \
    --cc=plagnioj@jcrosoft.com \
    --cc=sameo@linux.intel.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