lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20070924123408.596a3c69@dhcp-255-175.norway.atmel.com>
Date:	Mon, 24 Sep 2007 12:34:08 +0200
From:	Haavard Skinnemoen <hskinnemoen@...el.com>
To:	linux-fbdev-devel@...ts.sourceforge.net
Cc:	giometti@...eenne.com, i2c@...sensors.org,
	linux-kernel@...r.kernel.org, rpurdie@...ys.net
Subject: Re: [Linux-fbdev-devel] [RFC] driving a LCD panel via I2C

On Mon, 24 Sep 2007 10:58:08 +0200 (CEST)
"Rodolfo Giometti" <giometti@...eenne.com> wrote:

> Hello,
> 
> 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.

> Maybe can I add a special I2C function to get i2c_client pointer and
> then using it to send on/off commands to the LCD?

Just implement it as a regular I2C chip driver which registers a device
with the LCD framework when it is successfully probed.

HÃ¥vard
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ