linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: lee.jones@linaro.org (Lee Jones)
To: linux-arm-kernel@lists.infradead.org
Subject: AB8500 Regulators
Date: Mon, 30 Jul 2012 17:32:10 +0100	[thread overview]
Message-ID: <5016B70A.1030601@linaro.org> (raw)
In-Reply-To: <20120730152618.GI4468@opensource.wolfsonmicro.com>

On 30/07/12 16:26, Mark Brown wrote:
> On Mon, Jul 30, 2012 at 02:49:43PM +0100, Lee Jones wrote:
>
>> I wrote a patch which pulled each of these initial values into
>> Device Tree, but you NACK:ed it believing that most of the options
>> could be dealt with using the API. There is currently no API to set
>> up ST-Ericsson's configuration. So what's the best thing to do? How
>> do all of the other regulator drivers deal with non-standard
>> configuration? Or is it unheard of to use non-standard start-up
>> values?
>
> Well, a good start would be to work out what those register writes
> actually do and then we can have a discussion on how to do whatever
> that is.

Most of the configuration seems to pertain to voltage selection and 
making regulators valid. I assume this means you can enable them via 
their own registers and the enablement will take hold. This seems like 
pretty routine stuff as far as regulator configuration goes.

-- 
Lee Jones
Linaro ST-Ericsson Landing Team Lead
Linaro.org ? Open source software for ARM SoCs
Follow Linaro: Facebook | Twitter | Blog

  reply	other threads:[~2012-07-30 16:32 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-30 13:49 AB8500 Regulators Lee Jones
2012-07-30 15:26 ` Mark Brown
2012-07-30 16:32   ` Lee Jones [this message]
2012-07-30 17:48     ` Mark Brown
2012-07-31  8:46       ` Lee Jones
2012-07-31 11:08         ` Mark Brown
2012-07-31 12:26           ` Lee Jones
2012-07-31 13:47             ` Mark Brown
2012-07-31 14:21               ` Lee Jones
2012-07-31 14: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=5016B70A.1030601@linaro.org \
    --to=lee.jones@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).