From: David Brownell <david-b@pacbell.net>
To: Richard Purdie <rpurdie@rpsys.net>
Cc: Haavard Skinnemoen <hskinnemoen@atmel.com>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Samsung LTV350QV LCD driver
Date: Tue, 29 May 2007 14:38:11 -0700 [thread overview]
Message-ID: <200705291438.11581.david-b@pacbell.net> (raw)
In-Reply-To: <1180472477.5822.87.camel@localhost.localdomain>
On Tuesday 29 May 2007, Richard Purdie wrote:
> On Tue, 2007-05-29 at 21:52 +0200, Haavard Skinnemoen wrote:
> > This patch adds support for powering on and off the Samsung LTV350QV
> > LCD panel via SPI. The driver responds to framebuffer power
> > management, it powers off the panel on reboot/halt/poweroff, and it
> > can also be controlled through sysfs. The panel is powered up when the
> > module is loaded and off when the module is unloaded.
> >
> > Signed-off-by: Haavard Skinnemoen <hskinnemoen@atmel.com>
>
> The LCD class device bits look fine to me. The only change I'd request
> is not to change the order of things in drivers/video/backlight/Kconfig.
> If you do want to reword one of those entries (which is what I think you
> wanted to do), send it as a separate patch please.
One significant issue was screwed up sequencing causing
tools like 'xconfig' to display things wrong. Appended
is a patch fixing just that goof.
> David, any objections to the SPI bits?
They seemed fine to me, other than the write_reg() macro
having an embedded 'goto' ... explicitly against the
Documentation/CodingStyle guidelines. ("Chapter 12",
point 1 = "macros that affect code flow".)
I like seeing more of the SPI drivers go upstream. ;)
- Dave
>
> Richard
>
====== CUT HERE
Switch the order of LCD_CLASS_DEVICE and BACKLIGHT_CLASS_DEVICE,
so that it's possible to insert LCD devices without borking the
dependency displays of xconfig and other config tools.
Signed-off-by: David Brownell <dbrownell@users.sourceforge.net>
---
drivers/video/backlight/Kconfig | 26 ++++++++++++++++----------
1 file changed, 16 insertions(+), 10 deletions(-)
--- g26.orig/drivers/video/backlight/Kconfig 2007-05-29 14:31:41.000000000 -0700
+++ g26/drivers/video/backlight/Kconfig 2007-05-29 14:33:29.000000000 -0700
@@ -8,26 +8,32 @@ menuconfig BACKLIGHT_LCD_SUPPORT
Enable this to be able to choose the drivers for controlling the
backlight and the LCD panel on some platforms, for example on PDAs.
-config BACKLIGHT_CLASS_DEVICE
- tristate "Lowlevel Backlight controls"
+#
+# LCD
+#
+config LCD_CLASS_DEVICE
+ tristate "Lowlevel LCD controls"
depends on BACKLIGHT_LCD_SUPPORT
default m
help
- This framework adds support for low-level control of the LCD
- backlight. This includes support for brightness and power.
+ This framework adds support for low-level control of LCD.
+ Some framebuffer devices connect to platform-specific LCD modules
+ in order to have a platform-specific way to control the flat panel
+ (contrast and applying power to the LCD (not to the backlight!)).
To have support for your specific LCD panel you will have to
select the proper drivers which depend on this option.
-config LCD_CLASS_DEVICE
- tristate "Lowlevel LCD controls"
+#
+# Backlight
+#
+config BACKLIGHT_CLASS_DEVICE
+ tristate "Lowlevel Backlight controls"
depends on BACKLIGHT_LCD_SUPPORT
default m
help
- This framework adds support for low-level control of LCD.
- Some framebuffer devices connect to platform-specific LCD modules
- in order to have a platform-specific way to control the flat panel
- (contrast and applying power to the LCD (not to the backlight!)).
+ This framework adds support for low-level control of the LCD
+ backlight. This includes support for brightness and power.
To have support for your specific LCD panel you will have to
select the proper drivers which depend on this option.
next prev parent reply other threads:[~2007-05-29 21:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-29 19:52 Haavard Skinnemoen
2007-05-29 21:01 ` Richard Purdie
2007-05-29 21:38 ` David Brownell [this message]
2007-05-29 22:19 ` Richard Purdie
2007-05-30 10:46 ` [PATCH v2] " Haavard Skinnemoen
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=200705291438.11581.david-b@pacbell.net \
--to=david-b@pacbell.net \
--cc=hskinnemoen@atmel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rpurdie@rpsys.net \
/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
Powered by JetHome