The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Roger Quadros <quadros.roger@gmail.com>
Cc: pHilipp Zabel <philipp.zabel@gmail.com>,
	lrg@slimlogic.co.uk, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] regulator: Add GPIO enable control to fixed voltage regulator driver
Date: Fri, 31 Jul 2009 14:50:36 +0100	[thread overview]
Message-ID: <20090731135036.GA626@rakim.wolfsonmicro.main> (raw)
In-Reply-To: <b90c0690907310643n432c4504i1df5abaf8118e0b7@mail.gmail.com>

On Fri, Jul 31, 2009 at 04:43:40PM +0300, Roger Quadros wrote:
> On Fri, Jul 31, 2009 at 4:34 PM, Mark
> Brown<broonie@opensource.wolfsonmicro.com> wrote:

> > Feh, better print a warning for GPIO 0 for at least a kernel release.
> > Fortunately we've got no mainline users of fixed voltage regulators.

> I think most architectures start their GPIO numbering from 0.
> By 'a release', do you mean next Kernel release will be indexing GPIOs from 1?

No; I mean the driver should print a warning when using GPIO 0 as a way
of managing the transition.  Otherwise any existing users will find the
driver suddenly starts using a GPIO.

  reply	other threads:[~2009-07-31 13:50 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-31 12:55 [PATCH] regulator: Add GPIO enable control to fixed voltage regulator driver Roger Quadros
2009-07-31 13:10 ` Mark Brown
2009-07-31 13:25   ` pHilipp Zabel
2009-07-31 13:34     ` Mark Brown
2009-07-31 13:43       ` Roger Quadros
2009-07-31 13:50         ` Mark Brown [this message]
     [not found]           ` <b90c0690907310713w5c8b7fe3l4253f03f78f06491@mail.gmail.com>
     [not found]             ` <20090731141547.GA6505@rakim.wolfsonmicro.main>
2009-07-31 14:22               ` Roger Quadros
2009-07-31 14:34                 ` Roger Quadros

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=20090731135036.GA626@rakim.wolfsonmicro.main \
    --to=broonie@opensource.wolfsonmicro.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lrg@slimlogic.co.uk \
    --cc=philipp.zabel@gmail.com \
    --cc=quadros.roger@gmail.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