public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jonathan Cameron <Jonathan.Cameron@gmail.com>
To: LKML <linux-kernel@vger.kernel.org>
Cc: Liam Girdwood <lrg@kernel.org>, Mark Brown <broonie@sirena.org.uk>
Subject: Regulator: Use case query (many devices need to reg their voltage requirements?)
Date: Sat, 10 Jan 2009 15:27:48 +0000	[thread overview]
Message-ID: <4968BE74.1070903@gmail.com> (raw)

Dear All,

A quick request for comments w.r.t. specifying voltage requirements
of drivers that do not need to dynamically change their supply voltage.

Obviously for a given embedded system, it is possible to work out on
paper what regulator configuration works for all components connected to
a particular regulator as long as these connections are static.

A number of different embedded system now use main boards (core etc) in
conjunction with daughter boards.  In these cases different modules may
be inserted to support different daughter board options from a single kernel
(and combinations if possible).  Thus we have a situation in which the
appropriate voltage level can only be established if the various drivers
specify what they need. The board config may specify numerous devices
only some of which may actually be present.

This leads to additional complexity in numerous drivers as they have to act
as dynamic drivers (terminology from regulator docs) even though they don't
actually vary the voltage, merely specify what ranges they can work with.

Is this the best way to handle this situation, or do people have other
suggestions?

Thanks

Jonathan Cameron


             reply	other threads:[~2009-01-10 15:27 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-10 15:27 Jonathan Cameron [this message]
2009-01-10 17:46 ` Regulator: Use case query (many devices need to reg their voltage requirements?) Mark Brown
2009-01-10 18:05   ` Jonathan Cameron
2009-01-10 18:58     ` 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=4968BE74.1070903@gmail.com \
    --to=jonathan.cameron@gmail.com \
    --cc=broonie@sirena.org.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lrg@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