From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: "Nayak, Rajendra" <rnayak@ti.com>
Cc: "linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>,
Liam Girdwood <lrg@slimlogic.co.uk>,
Samuel Ortiz <sameo@linux.intel.com>
Subject: Re: [PATCH 1/2] twl6030: regulator: Fix vsel calculations in set/get voltage apis
Date: Thu, 18 Feb 2010 11:42:37 +0000 [thread overview]
Message-ID: <20100218114237.GE3542@rakim.wolfsonmicro.main> (raw)
In-Reply-To: <5A47E75E594F054BAF48C5E4FC4B92AB03215B11D9@dbde02.ent.ti.com>
On Thu, Feb 18, 2010 at 05:09:53PM +0530, Nayak, Rajendra wrote:
> Mark, I get your point. The table values were derived from what the spec
> suggests, but I agree that its confusing that in theory the formula
> suggests there could be more selectors than whats present in the table.
> I will check if its indeed possible to support all possible selectors
> between say a min/max range. And then have maybe seperate kind of tables
> for twl6030 which only specify min/max range and then use the formula to
> generate the right selector.
Another option if you do need the supported voltage list would be to
rename the table and have a separate function to do set on twl6030 which
makes the intended usage clear.
next prev parent reply other threads:[~2010-02-18 11:42 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-17 15:24 [PATCH 1/2] twl6030: regulator: Fix vsel calculations in set/get voltage apis Rajendra Nayak
2010-02-17 15:24 ` [PATCH 2/2] twl6030: regulator: Configure STATE register instead of REMAP Rajendra Nayak
2010-02-17 16:15 ` Mark Brown
2010-02-18 12:33 ` Liam Girdwood
2010-02-17 16:15 ` [PATCH 1/2] twl6030: regulator: Fix vsel calculations in set/get voltage apis Mark Brown
2010-02-18 6:32 ` Nayak, Rajendra
2010-02-18 9:48 ` Mark Brown
2010-02-18 10:19 ` Nayak, Rajendra
2010-02-18 10:40 ` Mark Brown
2010-02-18 11:39 ` Nayak, Rajendra
2010-02-18 11:42 ` Mark Brown [this message]
2010-02-19 6:39 ` Nayak, Rajendra
2010-02-19 9:27 ` 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=20100218114237.GE3542@rakim.wolfsonmicro.main \
--to=broonie@opensource.wolfsonmicro.com \
--cc=linux-omap@vger.kernel.org \
--cc=lrg@slimlogic.co.uk \
--cc=rnayak@ti.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.