All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thierry Reding <thierry.reding@avionic-design.de>
To: Andrew Chew <AChew@nvidia.com>
Cc: "peter.ujfalusi@ti.com" <peter.ujfalusi@ti.com>,
	Alex Courbot <acourbot@nvidia.com>,
	"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>
Subject: Re: [PATCH 1/1] ARM: OMAP: board-4430sdp: Provide regulator to pwm-backlight
Date: Wed, 13 Mar 2013 08:09:02 +0100	[thread overview]
Message-ID: <20130313070902.GB25940@avionic-0098.mockup.avionic-design.de> (raw)
In-Reply-To: <643E69AA4436674C8F39DCC2C05F7638629CA516BD@HQMAIL03.nvidia.com>

[-- Attachment #1: Type: text/plain, Size: 2140 bytes --]

On Tue, Mar 12, 2013 at 12:11:54PM -0700, Andrew Chew wrote:
> > From: Thierry Reding [mailto:thierry.reding@avionic-design.de]
> > Sent: Tuesday, March 12, 2013 12:01 AM
> > To: Andrew Chew
> > Cc: peter.ujfalusi@ti.com; Alex Courbot; linux-omap@vger.kernel.org
> > Subject: Re: [PATCH 1/1] ARM: OMAP: board-4430sdp: Provide regulator to
> > pwm-backlight
> > 
> > * PGP Signed by an unknown key
> > 
> > On Mon, Mar 11, 2013 at 06:54:26PM -0700, Andrew Chew wrote:
> > > The pwm-backlight driver now takes a mandatory regulator that is
> > > gotten during driver probe.  Initialize a dummy regulator to satisfy
> > > this requirement.
> > >
> > > Signed-off-by: Andrew Chew <achew@nvidia.com>
> > > ---
> > > This patch, along with many more soon to follow, attempts to satisfy
> > > the new mandatory regulator that pwm-backlight will grab during probe.
> > > The only board in mach-omap2 to use the pwm-backlight appears to be the
> > 4430sdp.
> > >
> > > I thought I'd start small and use this board as an example.
> > >
> > > I tested similar code in my Tegra board, so it should be okay.  Of
> > > course, I don't have a 4430sdp to test with.
> > 
> > Hi Andrew,
> > 
> > This looks good, one minor comment below. I think it might make sense to
> > post this patch as part of a series that includes the change to the pwm-
> > backlight driver. This will make things easier on potential testers.
> > You can later extend that series to include all the other users and eventually
> > the whole series can be merged.
> 
> Do you mean I should do a single patch series, accumulating other boards
> as I go?

Yes, that way everything needed will be in one patch series and people
can easily apply that to their trees. It will also make things easier if
we decide to merge all of them through one tree in the end.

> And by the way, do I have your reviewed-by for the pwm-backlight regulator
> patch?

I think it looks good, but I'll go over it again in your repost of the
whole series. I don't think you need my Reviewed-by, though, since I
maintain the pwm-backlight driver. =)

Thierry

[-- Attachment #2: Type: application/pgp-signature, Size: 836 bytes --]

  reply	other threads:[~2013-03-13  7:09 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-12  1:54 [PATCH 1/1] ARM: OMAP: board-4430sdp: Provide regulator to pwm-backlight Andrew Chew
2013-03-12  7:01 ` Thierry Reding
2013-03-12 19:11   ` Andrew Chew
2013-03-13  7:09     ` Thierry Reding [this message]
2013-03-12  9:24 ` Peter Ujfalusi
2013-03-12 22:21   ` Andrew Chew

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=20130313070902.GB25940@avionic-0098.mockup.avionic-design.de \
    --to=thierry.reding@avionic-design.de \
    --cc=AChew@nvidia.com \
    --cc=acourbot@nvidia.com \
    --cc=linux-omap@vger.kernel.org \
    --cc=peter.ujfalusi@ti.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.