All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jamey Hicks <jamey.hicks@hp.com>
To: linux-fbdev-devel@lists.sourceforge.net
Subject: lcd and backlight module class
Date: Thu, 23 Oct 2003 10:39:38 -0400	[thread overview]
Message-ID: <3F97E82A.20001@hp.com> (raw)

A while back I posted a note to arm-linux-kernel about developing some 
low-level API's to separate out platform-specific code from drivers such 
as sa1100fb.c.
  
http://lists.arm.linux.org.uk/pipermail/linux-arm-kernel/2003-July/016235.html

As a particular example, the sa1100fb driver is cluttered with the 
platform initialization and control code for the many SA11x0-based 
platforms supported by the ARM linux kernel.  My thought is that the new 
device model gives a good framework to decouple the fbdev drivers and 
the platforms.  I've been busy with other things, so progress on this 
has been slower than I hoped.  But I have prototyped it.  For usespace 
access to these controls, I envision sysfs attributes.  I also think 
that the fb drivers might register an interface with the lcd/backlight 
classes so that they can be notified if an LCD is hotplugged.  It  would 
also help loosen the dependence on link/initialization order.

Anyway, please review and comment on this patch:

http://www.arm.linux.org.uk/developer/patches/viewpatch.php?id=1696/1

There are uses of lcd module in subsequent ipaq patches, such as this
one:
http://www.arm.linux.org.uk/developer/patches/viewpatch.php?id=1699/1

Thanks,
Jamey Hicks







-------------------------------------------------------
This SF.net email is sponsored by: The SF.net Donation Program.
Do you like what SourceForge.net is doing for the Open
Source Community?  Make a contribution, and help us add new
features and functionality. Click here: http://sourceforge.net/donate/

                 reply	other threads:[~2003-10-24  4:17 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=3F97E82A.20001@hp.com \
    --to=jamey.hicks@hp.com \
    --cc=linux-fbdev-devel@lists.sourceforge.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.