linux-spi.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Richard Purdie <rpurdie-Fm38FmjxZ/leoWH0uzbU5w@public.gmane.org>
To: David Brownell <david-b-yBeKhBN/0LDR7s880joybQ@public.gmane.org>
Cc: spi-devel-general-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org,
	Harald Welte <laforge-4Bgg8jF3iZdg9hUCZPvPmw@public.gmane.org>,
	linux-arm-kernel-xIg/pKzrS19vn6HldHNs0ANdhmdF6hFW@public.gmane.org
Subject: Re: [PATCH 7/12] neo1973: JBT6K74 LCM control	interface driver
Date: Fri, 21 Dec 2007 00:01:11 +0000	[thread overview]
Message-ID: <1198195271.4651.52.camel@localhost.localdomain> (raw)
In-Reply-To: <200712201431.58932.david-b-yBeKhBN/0LDR7s880joybQ@public.gmane.org>

On Thu, 2007-12-20 at 14:31 -0800, David Brownell wrote:
> The "backlight" directory is a bit misnamed, since it also holds
> the LCD_CLASS_DEVICE stuff which is just "lowlevel LCD controls".
> You'll observe the LTV driver controls power and gamma just like
> this JBT driver does...
> 
> Of course there aren't yet many "lowlevel LCD controls" drivers,
> and this driver might suggest revisiting that class.  There's one
> LCD controller I know of with integral PWM contrast control, which
> might help motivate relocating that class code.  How about a new
> "lcm" directory?  :)

Backlights and lcd controllers mainly reside in drivers/video/backlight
although there are a number of backlight drivers spread about the tree.
I'm effectively the maintainer of the lcd class alongside backlights
since I've tried to keep the two roughly in sync style wise. 

> Looks much better IMO.  I still think that since this exposes
> "low level controls" it should depend on LCD_CLASS_DEVICE, since
> that's allegedly what that infrastructure is there for.  But I
> expect that feedback would be resolved by folk maintaining that
> part of the driver stack.

I'm not sure the LCD class would be very helpful to this driver. As you
say, this really suggests shortcomings of the LCD class but with only
one LCD driver in mainline changing that class to work better for LCDs
is possible.

The main question is whether the functionality here is suitably generic
to turn into a class? Personally I'm not sure it is but I'm open to
opinions (and patches).

Cheers,

Richard






-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/

  parent reply	other threads:[~2007-12-21  0:01 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-12-18 11:08 [PATCH 7/12] neo1973: JBT6K74 LCM control interface driver Harald Welte
     [not found] ` <20071218110800.GN29882-jI4mzJ+yNOMOwssVsN95jSCwEArCW2h5@public.gmane.org>
2007-12-18 23:59   ` David Brownell
     [not found]     ` <20071218235954.5351225EA51-ZcXrCSuhvln6VZ3dlLfH/g4gEjPzgfUyLrfjE7I9kuVHxeISYlDBzl6hYfS7NtTn@public.gmane.org>
2007-12-19  9:57       ` Harald Welte
     [not found]         ` <20071219095721.GU29882-jI4mzJ+yNOMOwssVsN95jSCwEArCW2h5@public.gmane.org>
2007-12-19 20:04           ` David Brownell
2007-12-19 21:16   ` David Brownell
     [not found]     ` <200712191316.45435.david-b-yBeKhBN/0LDR7s880joybQ@public.gmane.org>
2007-12-20 15:06       ` Harald Welte
     [not found]         ` <20071220150659.GP29882-jI4mzJ+yNOMOwssVsN95jSCwEArCW2h5@public.gmane.org>
2007-12-20 22:31           ` David Brownell
     [not found]             ` <200712201431.58932.david-b-yBeKhBN/0LDR7s880joybQ@public.gmane.org>
2007-12-21  0:01               ` Richard Purdie [this message]
     [not found]                 ` <1198195271.4651.52.camel-bi+AKbBUZKY6gyzm1THtWbp2dZbC/Bob@public.gmane.org>
2007-12-21  9:39                   ` display/lcm/backlight/framebuffer interaction (was [PATCH 7/12] neo1973: JBT6K74 LCM control interface driver) Harald Welte
     [not found]                     ` <20071221093934.GO6625-jI4mzJ+yNOMOwssVsN95jSCwEArCW2h5@public.gmane.org>
2007-12-21 10:50                       ` Richard Purdie

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=1198195271.4651.52.camel@localhost.localdomain \
    --to=rpurdie-fm38fmjxz/leowh0uzbu5w@public.gmane.org \
    --cc=david-b-yBeKhBN/0LDR7s880joybQ@public.gmane.org \
    --cc=laforge-4Bgg8jF3iZdg9hUCZPvPmw@public.gmane.org \
    --cc=linux-arm-kernel-xIg/pKzrS19vn6HldHNs0ANdhmdF6hFW@public.gmane.org \
    --cc=spi-devel-general-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
    /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).