From: Thomas Renninger <trenn@suse.de>
To: yakui_zhao <yakui.zhao@intel.com>
Cc: 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>,
"rpurdie@linux.intel.com" <rpurdie@linux.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: Thu, 9 Apr 2009 09:42:05 +0200 [thread overview]
Message-ID: <200904090942.06310.trenn@suse.de> (raw)
In-Reply-To: <1239239539.3635.46.camel@localhost.localdomain>
On Thursday 09 April 2009 03:12:19 am yakui_zhao wrote:
> On Wed, 2009-04-08 at 18:17 +0800, Thomas Renninger wrote:
> > Hi,
> >
> > We have these interfaces:
> > - vendor specific implementation
> > (mostly in drivers/platform/x86/vendor-laptop.c)
> > - ACPI generic backlight only
> > - Opregion (this is the KMS/i915 interface you are talking about
> > or is there another abstraction?)
>
> IMO it is unnecessary to consider the Opregion as the interface. In fact
> it is only for the communication between the ACPI and graphics driver.
> We can send the request by using ACPI generic backlight and then the
> brightness is changed in the graphics driver.
>
> What you said is also OK.
> But I don't know whether this will make the problem complex.
> This issue I raised is related with that no backlight can be controlled
> by xrandr tool after using KMS.
> For example: >http://bugs.freedesktop.org/show_bug.cgi?id=20963
Why should this get a i915 and not a native samsung-laptop driver?
Can someone come up with some example code how the backlight switching
implementation for this one would look like.
This is needed anyway and then it is much easier to think about how to make
sure backlight drivers do not get double registered.
Thomas
prev parent reply other threads:[~2009-04-09 7:41 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
2009-04-09 1:12 ` yakui_zhao
2009-04-09 7:42 ` Thomas Renninger [this message]
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=200904090942.06310.trenn@suse.de \
--to=trenn@suse.de \
--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=rpurdie@linux.intel.com \
--cc=rui.zhang@intel.com \
--cc=sonne@debian.org \
--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.