From: Tomi Valkeinen <tomi.valkeinen@ti.com>
To: Russ Dill <Russ.Dill@ti.com>
Cc: Tony Lindgren <tony@atomide.com>,
linux-omap@vger.kernel.org,
Robert Nelson <robertcnelson@gmail.com>,
Jason Kridner <jkridner@beagleboard.org>
Subject: Re: [PATCH] OMAP: Beagle: fix TFP410 powerdown GPIO init
Date: Thu, 14 Jun 2012 15:20:35 +0300 [thread overview]
Message-ID: <1339676435.2229.28.camel@deskari> (raw)
In-Reply-To: <CA+Bv8Xbqi7y3v2O7u8B31tv4JCTfQq3wWFojfK4UuAqDoYhB-Q@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1718 bytes --]
On Thu, 2012-06-14 at 04:40 -0700, Russ Dill wrote:
> On Thu, Jun 14, 2012 at 1:13 AM, Tomi Valkeinen <tomi.valkeinen@ti.com> wrote:
> > On Thu, 2012-06-14 at 00:59 -0700, Russ Dill wrote:
> >> On Thu, Jun 14, 2012 at 12:18 AM, Tomi Valkeinen <tomi.valkeinen@ti.com> wrote:
> >> > On Wed, 2012-06-13 at 23:58 -0700, Russ Dill wrote:
> >> >> On Wed, Jun 13, 2012 at 2:20 AM, Tomi Valkeinen <tomi.valkeinen@ti.com> wrote:
> >> >> > Commit e813a55eb9c9bc6c8039fb16332cf43402125b30 ("OMAP: board-files:
> >> >> > remove custom PD GPIO handling for DVI output") moved TFP410 chip's
> >> >> > powerdown-gpio handling from the board files to the tfp410 driver. One
> >> >> > gpio_request_one(powerdown-gpio, ...) was mistakenly left unremoved in
> >> >> > the Beagle board file. This causes the tfp410 driver to fail to request
> >> >> > the gpio on Beagle, causing the driver to fail and thus the DVI output
> >> >> > doesn't work.
> >> >>
> >> >> Can you take the one I sent earlier instead?
> >> >>
> >> >> http://www.spinics.net/lists/linux-omap/msg69913.html
> >> >
> >> > Hmm, that probably doesn't apply. The power-down GPIO is now handled in
> >> > the tfp410 driver, not in the board files.
> >>
> >> Give me a branch to rebase it onto and I will.
> >
> > v3.5-rc2
>
> This one (v4) already applies to v3.5-rc2
>
> http://www.spinics.net/lists/linux-omap/msg70042.html
My ack for v4:
Acked-by: Tomi Valkeinen <tomi.valkeinen@ti.com>
And I'd reword the description, "fix" instead of cleanup. The "boot
warnings" are errors. I don't think the DVI output works at all with
beagle in the current mainline.
Btw, please cc me when sending patches related to display.
Tomi
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2012-06-14 12:20 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-13 9:20 [PATCH] OMAP: Beagle: fix TFP410 powerdown GPIO init Tomi Valkeinen
2012-06-14 6:58 ` Russ Dill
2012-06-14 7:18 ` Tomi Valkeinen
2012-06-14 7:59 ` Russ Dill
2012-06-14 8:13 ` Tomi Valkeinen
2012-06-14 8:17 ` Russ Dill
2012-06-14 8:20 ` Tomi Valkeinen
2012-06-14 11:40 ` Russ Dill
2012-06-14 12:20 ` Tomi Valkeinen [this message]
2012-06-20 13:48 ` Tony Lindgren
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=1339676435.2229.28.camel@deskari \
--to=tomi.valkeinen@ti.com \
--cc=Russ.Dill@ti.com \
--cc=jkridner@beagleboard.org \
--cc=linux-omap@vger.kernel.org \
--cc=robertcnelson@gmail.com \
--cc=tony@atomide.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