This is a discussion on Re: [Linux-fbdev-devel] [RFC] driving a LCD panel via I2C - Kernel ; On Mon, 2007-09-24 at 12:34 +0200, Haavard Skinnemoen wrote: > On Mon, 24 Sep 2007 10:58:08 +0200 (CEST) > "Rodolfo Giometti" wrote: > > I have an LCD panel on a custom PXA27x based board and it must be > ...
On Mon, 2007-09-24 at 12:34 +0200, Haavard Skinnemoen wrote:
> On Mon, 24 Sep 2007 10:58:08 +0200 (CEST)
> "Rodolfo Giometti"
> > I have an LCD panel on a custom PXA27x based board and it must be
> > turned on/off by some special commands via a GPIO throught a I2C chip.
> > I'd like some suggestion about I can easily manage this situation.
> I have a similar panel in the sense that it needs a bunch of SPI
> commands to get started. I implemented a LCD driver
> (drivers/video/backlight) for it so that it is automatically turned
> on/off at bootup/shutdown, and can be manually turned on/off
> through /sys/class/lcd/ltv350qv/power. AFAIK the driver is currently
> sitting in the backlight tree scheduled for inclusion in 2.6.24.
It is, its queued as
Its also worth noting that corgi-bl.c has a variant (akita) that uses a
gpio over an I2C IO expander for the backlight control. The code paths
are a little convoluted since other gpios are used by other drivers. The
base driver is in arch/arm/mach-pxa/akita-ioexp.c, the set_intensity
function is in arch/arm/mach-pxa/corgi_lcd.c and the base backlight
device in arch/arm/mach-pxa/spitz.c. I will be moving the set_intensity
to spitz.c to make things a little clearer.
Also, I'm in the process of turning corgi-bl.c into a generic backlight
driver which might help you, see:
Now, the GPIO framework could help too (it didn't exist when I wrote
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to email@example.com
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/