From: Greg KH <greg@kroah.com>
To: Jesse Barnes <jbarnes@virtuousgeek.org>
Cc: linux-kernel@vger.kernel.org, intel-gfx@lists.freedesktop.org,
"Dmitry Torokhov" <dmitry.torokhov@gmail.com>,
"Soeren Sonnenburg" <bugreports@nn7.de>,
"Jérémie Huchet" <jeremie@lamah.info>,
"Matthew Garrett" <mjg59@srcf.ucam.org>
Subject: Re: [PATCH] Samsung laptop driver
Date: Fri, 21 Aug 2009 16:33:38 -0700 [thread overview]
Message-ID: <20090821233338.GA28241@kroah.com> (raw)
In-Reply-To: <20090821161952.1b84480c@jbarnes-g45>
On Fri, Aug 21, 2009 at 04:19:52PM -0700, Jesse Barnes wrote:
> On Fri, 21 Aug 2009 15:59:25 -0700
> Greg KH <greg@kroah.com> wrote:
> > Jesse, I don't know how this is going to play with your recently added
> > backlight support for the i915 driver. As you don't have control over
> > the LEDs and other stuff that this driver is going to support, I think
> > we need some way to keep the i915 driver from messing with the
> > backlight values, don't you think?
>
> Right, it should be fine. The i915 driver should only take control and
> provide a backlight when:
> - no ACPI method is available
> - no platform method is available (like this one)
> - backlight is exposed through the GPU or i2c
>
> So I'm a lot happier now that you've figured out the proper platform
> interface. :) The test code I sent out earlier didn't work for Mike
> because his VBIOS (properly it turns out) indicated that there was an
> external agent in charge of the backlight.
Great, then all should be good, thanks for letting me know.
Now I wonder if Mike's laptop can be controlled through my new driver,
that would be an interesting test. I'll ping him about it.
thanks,
greg k-h
next prev parent reply other threads:[~2009-08-21 23:38 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-21 22:59 [PATCH] Samsung laptop driver Greg KH
2009-08-21 23:19 ` Jesse Barnes
2009-08-21 23:33 ` Greg KH [this message]
2009-08-22 9:23 ` Alan Jenkins
2009-08-26 16:18 ` Greg KH
2009-08-22 10:07 ` [Intel-gfx] " Bruno Prémont
2009-08-26 16:32 ` Greg KH
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=20090821233338.GA28241@kroah.com \
--to=greg@kroah.com \
--cc=bugreports@nn7.de \
--cc=dmitry.torokhov@gmail.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jbarnes@virtuousgeek.org \
--cc=jeremie@lamah.info \
--cc=linux-kernel@vger.kernel.org \
--cc=mjg59@srcf.ucam.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