linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: lrg@slimlogic.co.uk (Liam Girdwood)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 4/4] MXC: imx31pdk: Trying to enabling regulators on mc13783
Date: Thu, 10 Dec 2009 19:39:25 +0000	[thread overview]
Message-ID: <1260473965.3625.218.camel@odin> (raw)
In-Reply-To: <1260473248.2141.75.camel@climbing-alby>

On Thu, 2009-12-10 at 20:27 +0100, Alberto Panizzo wrote:
> Il giorno gio, 10/12/2009 alle 19.10 +0000, Mark Brown ha scritto:
> > On Thu, Dec 10, 2009 at 07:56:44PM +0100, Alberto Panizzo wrote:
> > 
> > > +/* MC13783 */
> > > +#define mV_to_uV(mV) (mV * 1000)
> > 
> > Define this somewhere global, it's generally useful.
> 
> Yes, maybe in include/linux/mfd/mc13783.h 
> 

This is actually quite useful to other drivers too as most seem to work
in mV. What about in regulator/driver.h 

Thanks

Liam

  parent reply	other threads:[~2009-12-10 19:39 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-10 18:37 MXC: mx31pdk: mc13783: Trying to full support mc13783 regulators Alberto Panizzo
2009-12-10 18:42 ` [PATCH 1/4] MXC: imx31pdk: Add support for on board NAND Flash Alberto Panizzo
2009-12-10 18:45   ` [PATCH 2/4] MXC: mx31pdk: Add CSPI2 interface support Alberto Panizzo
2009-12-10 18:50     ` [PATCH 3/4] MXC: mc13783: Developing, trying to full support regulators Alberto Panizzo
2009-12-10 18:56       ` [PATCH 4/4] MXC: imx31pdk: Trying to enabling regulators on mc13783 Alberto Panizzo
2009-12-10 19:10         ` Mark Brown
2009-12-10 19:27           ` Alberto Panizzo
2009-12-10 19:35             ` Mark Brown
2009-12-10 19:39             ` Liam Girdwood [this message]
2009-12-11 12:44           ` Sascha linux-arm
2009-12-11 13:09       ` [PATCH 3/4] MXC: mc13783: Developing, trying to full support regulators Uwe Kleine-König
2009-12-10 19:11 ` MXC: mx31pdk: mc13783: Trying to full support mc13783 regulators Alberto Panizzo
2009-12-10 19:42   ` Russell King - ARM Linux

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=1260473965.3625.218.camel@odin \
    --to=lrg@slimlogic.co.uk \
    --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).