All of lore.kernel.org
 help / color / mirror / Atom feed
From: Richard Purdie <rpurdie@linux.intel.com>
To: Thomas Renninger <trenn@suse.de>
Cc: yakui_zhao <yakui.zhao@intel.com>,
	Matthew Garrett <mjg59@srcf.ucam.org>,
	Jesse Barnes <jbarnes@virtuousgeek.org>,
	"intel-gfx@lists.freedesktop.org"
	<intel-gfx@lists.freedesktop.org>,
	"dri-devel@lists.sourceforge.net"
	<dri-devel@lists.sourceforge.net>,
	"sonne@debian.org" <sonne@debian.org>,
	"Zhang, Rui" <rui.zhang@intel.com>, Len Brown <lenb@kernel.org>,
	linux-acpi <linux-acpi@vger.kernel.org>
Subject: Re: [RFC] [intel-gfx] :The backlight issue when KMS is used
Date: Wed, 08 Apr 2009 11:50:03 +0100	[thread overview]
Message-ID: <1239187803.5339.13.camel@dax.rpnet.com> (raw)
In-Reply-To: <200904081217.15667.trenn@suse.de>

On Wed, 2009-04-08 at 12:17 +0200, Thomas Renninger wrote:
> Matthew and Jesse are looking for following approach:
> Let all drivers try to register for the generic backlight interface.
> As we do not know which driver will get loaded first, you want to 
> detect whether another driver already registered the backlight
> interface and implement a priority to eventually let the newly
> loaded driver unregister the other driver's backlight device, notify
> this driver via a notifier chain and then register the own backlight
> interface (is that correct?).
> 
> Priority could look like:
> 1) vendor specific drivers
> 2) ACPI generic drivers
> 3) Graphics card's specific kernel drivers (IGD/Opregion and possibly
>    others)
> 3 has highest prio.
> 
> If I got that right, I do not like:
>   - the complexity that has to be added to the generic backlight
>     interface and each backlight driver.

I'm not arguing for or against any approach here but if we need to have
this priority handoff system, I'd like to see it as a wrapper around the
backlight class and the class itself is unlikely to need changes. The
wrapper would register one backlight device with the generic class and
then redirect the function calls as needed.

Cheers,

Richard


  reply	other threads:[~2009-04-08 10:50 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1238737778.3582.163.camel@localhost.localdomain>
     [not found] ` <20090403092408.66809996@hobbes>
     [not found]   ` <20090403162906.GB23243@srcf.ucam.org>
     [not found]     ` <1239075911.3582.206.camel@localhost.localdomain>
     [not found]       ` <20090407055717.GA14710@srcf.ucam.org>
     [not found]         ` <1239089123.3582.228.camel@localhost.localdomain>
     [not found]           ` <1239092434.7661.87.camel@rzhang-dt>
     [not found]             ` <20090407082256.GA17012@srcf.ucam.org>
2009-04-07  8:48               ` [RFC] [intel-gfx] :The backlight issue when KMS is used Zhang Rui
2009-04-07 23:27                 ` Jesse Barnes
2009-04-08  0:59                 ` yakui_zhao
2009-04-08  7:54                 ` Thomas Renninger
     [not found]           ` <20090407073845.GA15635@srcf.ucam.org>
2009-04-08  0:56             ` yakui_zhao
2009-04-08 10:17               ` Thomas Renninger
2009-04-08 10:50                 ` Richard Purdie [this message]
2009-04-09  1:12                 ` yakui_zhao
2009-04-09  7:42                   ` Thomas Renninger

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=1239187803.5339.13.camel@dax.rpnet.com \
    --to=rpurdie@linux.intel.com \
    --cc=dri-devel@lists.sourceforge.net \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=jbarnes@virtuousgeek.org \
    --cc=lenb@kernel.org \
    --cc=linux-acpi@vger.kernel.org \
    --cc=mjg59@srcf.ucam.org \
    --cc=rui.zhang@intel.com \
    --cc=sonne@debian.org \
    --cc=trenn@suse.de \
    --cc=yakui.zhao@intel.com \
    /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.