From: Russell King - ARM Linux <linux@arm.linux.org.uk>
To: Tony Lindgren <tony@atomide.com>
Cc: linux-omap@vger.kernel.org,
Tomi Valkeinen <tomi.valkeinen@ti.com>,
linux-arm-kernel@lists.infradead.org
Subject: Re: OMAP display subsystem - does it work?
Date: Sat, 28 Dec 2013 23:30:53 +0000 [thread overview]
Message-ID: <20131228233053.GJ32243@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <20131221005941.GI32243@n2100.arm.linux.org.uk>
On Sat, Dec 21, 2013 at 12:59:41AM +0000, Russell King - ARM Linux wrote:
> On Fri, Dec 20, 2013 at 08:55:03AM -0800, Tony Lindgren wrote:
> > Yeah this seems to do the trick for me for the built-in DSS on LDP.
> >
> > Tony
> >
> > 8< -----------------------------------
> > From: Tony Lindgren <tony@atomide.com>
> > Date: Fri, 20 Dec 2013 08:53:27 -0800
> > Subject: [PATCH] ARM: OMAP2+: Fix LCD panel backlight regression for LDP legacy booting
> >
> > Looks like the LCD panel on LDP has been broken quite a while, and
> > recently got fixed. However, there's still an issue where the panel
> > backlight does not come on if the LCD drivers are built into the
> > kernel.
> >
> > Fix the issue by registering the DPI LCD panel only after the twl4030
> > GPIO has probed.
> >
> > Reported-by: Russell King <rmk+kernel@arm.linux.org.uk>
> > Signed-off-by: Tony Lindgren <tony@atomide.com>
> >
> > --- a/arch/arm/mach-omap2/board-ldp.c
> > +++ b/arch/arm/mach-omap2/board-ldp.c
> > @@ -248,7 +248,7 @@ static int ldp_twl_gpio_setup(struct device *dev, unsigned gpio, unsigned ngpio)
> > /* Backlight enable GPIO */
> > ldp_lcd_pdata.backlight_gpio = gpio + 15;
> >
> > - return 0;
> > + return platform_device_register(&ldp_lcd_device);
> > }
> >
> > static struct twl4030_gpio_platform_data ldp_gpio_data = {
> > @@ -346,7 +346,6 @@ static struct omap2_hsmmc_info mmc[] __initdata = {
> >
> > static struct platform_device *ldp_devices[] __initdata = {
> > &ldp_gpio_keys_device,
> > - &ldp_lcd_device,
> > };
> >
> > #ifdef CONFIG_OMAP_MUX
>
> I've added it to the test build for tonight (only as an uncommitted
> modification) so we'll see what happens tomorrow morning.
BTW, yes, this does result in the display working again on the LDP.
next prev parent reply other threads:[~2013-12-28 23:31 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-18 12:00 OMAP display subsystem - does it work? Russell King - ARM Linux
2013-12-18 13:54 ` Tomi Valkeinen
2013-12-18 15:29 ` Russell King - ARM Linux
2013-12-18 16:03 ` Tomi Valkeinen
2013-12-18 18:23 ` Tony Lindgren
2013-12-19 5:23 ` Tomi Valkeinen
2013-12-19 16:56 ` Tony Lindgren
2013-12-20 7:45 ` Tomi Valkeinen
2013-12-19 17:56 ` Russell King - ARM Linux
2013-12-19 18:22 ` Tony Lindgren
2013-12-20 11:27 ` Russell King - ARM Linux
2013-12-20 11:48 ` Russell King - ARM Linux
2013-12-20 13:43 ` Tomi Valkeinen
2013-12-20 16:04 ` Tony Lindgren
2013-12-20 16:55 ` Tony Lindgren
2013-12-21 0:59 ` Russell King - ARM Linux
2013-12-28 23:30 ` Russell King - ARM Linux [this message]
2013-12-23 7:53 ` Tomi Valkeinen
2013-12-27 18:11 ` Tony Lindgren
2013-12-23 7:49 ` Tomi Valkeinen
2013-12-20 16:10 ` Tony Lindgren
2013-12-19 17:53 ` 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=20131228233053.GJ32243@n2100.arm.linux.org.uk \
--to=linux@arm.linux.org.uk \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=tomi.valkeinen@ti.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;
as well as URLs for NNTP newsgroup(s).