public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Andrew Zabolotny <zap@homelink.ru>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Backlight and LCD module patches [1]
Date: Tue, 13 Jul 2004 23:11:38 -0700	[thread overview]
Message-ID: <20040714061138.GC11803@kroah.com> (raw)
In-Reply-To: <20040627002152.20e2da7d.zap@homelink.ru>

On Sun, Jun 27, 2004 at 12:21:52AM +0400, Andrew Zabolotny wrote:
> On Thu, 24 Jun 2004 14:34:52 -0700
> Greg KH <greg@kroah.com> wrote:
> 
> > How about just having every l/b driver containing a pointer to the
> > fbinfo that it is associated with?  Isn't there some way you can keep
> > the pointer that you need around within the place that you need to use
> > it from eventually?
> It's not a question of b/l driver needing the framebuffer driver; it's the
> other way around: the framebuffer driver needs the b/l drivers (needs so
> much that it can fail initialization in some cases if it doesn't find the
> corresponding b/l device).

Ok, then put a pointer in the fb driver to the backlight.
And a pointer in the backlight to the fb.  What's wrong with that?

> If you'll ask why not embed the b/l controls directly into the framebuffer
> drivers, the reason is simple: some video controllers just don't have a
> predefined way of controlling the b/l, so in every implementation it's
> different.

Just do it for the ones that you do know, what's wrong with that?

thanks,

greg k-h

  reply	other threads:[~2004-07-14  6:26 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-06-17 18:35 Backlight and LCD module patches [1] Andrew Zabolotny
2004-06-17 19:47 ` Greg KH
2004-06-17 21:55   ` Andrew Zabolotny
2004-06-17 22:05     ` Greg KH
2004-06-18  5:55       ` Andrew Zabolotny
2004-06-24 21:34         ` Greg KH
2004-06-26 20:21           ` Andrew Zabolotny
2004-07-14  6:11             ` Greg KH [this message]
2004-07-14 19:14               ` Andrew Zabolotny

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=20040714061138.GC11803@kroah.com \
    --to=greg@kroah.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=zap@homelink.ru \
    /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