* Re: drivers/platform/x86: Backlight-Add-backlight-type-v2.patch
[not found] <AANLkTikwo++xG7SXzNPwmZgU2jbdLiMr0Wi+vaxFqb7o@mail.gmail.com>
@ 2010-10-27 11:39 ` Corentin Chary
2010-10-27 12:13 ` Matthew Garrett
0 siblings, 1 reply; 3+ messages in thread
From: Corentin Chary @ 2010-10-27 11:39 UTC (permalink / raw)
To: sedat.dilek
Cc: LKML, platform-driver-x86, DRI, Matthew Garrett, acpi4asus-user,
Michel Dänzer, linux-wireless
On Wed, Oct 27, 2010 at 1:06 PM, Sedat Dilek <sedat.dilek@googlemail.com> wrote:
> Hi,
>
> while testing linux-next I wanted to reactivate the backlight type
> patches laying in my build-dir.
>
> Within 2.6.36-rcX cycle I had successfully tested the backlight type
> patch [1] with an additional patch for radeon by Michel (posted to
> dri-devel ML, see [2]).
>
> The main patch needs a little refreshing.
>
> v2: drivers/platform/x86/asus-laptop.c: Refreshed to fit linux-next
> (next-20101027)
>
>
> Kind Regards,
> - Sedat -
>
> [1] https://patchwork.kernel.org/patch/163971/
> [2] https://patchwork.kernel.org/patch/182352/
>
Hi,
I think rfkill has the same problem, on some platforms, the platform
driver will add a rfkill switch, but the network (wlan/wimax/whatever)
driver may also add one. AFAIK, the platform one is more likely to be
able to power down the device completly.
For the current patch, a common pattern seems to be : video/ -> RAW,
platform/ -> PLATFORM. Couldn't we make some guess by checking the
parent of the backlight instead of doing this by hand for every
drivers ?
Thanks,
--
Corentin Chary
http://xf.iksaif.net
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: drivers/platform/x86: Backlight-Add-backlight-type-v2.patch
@ 2010-10-27 15:58 Joey Lee
0 siblings, 0 replies; 3+ messages in thread
From: Joey Lee @ 2010-10-27 15:58 UTC (permalink / raw)
To: corentin.chary
Cc: michel, sedat.dilek, dri-devel, acpi4asus-user, mjg, linux-kernel,
linux-wireless, platform-driver-x86
Hi Corentin,
於 三，2010-10-27 於 13:39 +0200，Corentin Chary 提到：
> On Wed, Oct 27, 2010 at 1:06 PM, Sedat Dilek <sedat.dilek@googlemail.com> wrote:
> > Hi,
> >
> > while testing linux-next I wanted to reactivate the backlight type
> > patches laying in my build-dir.
> >
> > Within 2.6.36-rcX cycle I had successfully tested the backlight type
> > patch [1] with an additional patch for radeon by Michel (posted to
> > dri-devel ML, see [2]).
> >
> > The main patch needs a little refreshing.
> >
> > v2: drivers/platform/x86/asus-laptop.c: Refreshed to fit linux-next
> > (next-20101027)
> >
> >
> > Kind Regards,
> > - Sedat -
> >
> > [1] https://patchwork.kernel.org/patch/163971/
> > [2] https://patchwork.kernel.org/patch/182352/
> >
>
> Hi,
>
> I think rfkill has the same problem, on some platforms, the platform
> driver will add a rfkill switch, but the network (wlan/wimax/whatever)
> driver may also add one. AFAIK, the platform one is more likely to be
> able to power down the device completly.
>
Agreed your point!
x86/laptop or wmi driver borrow rfkill interface for power control but
confuse with userland applications.
Thank's
Joey Lee
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2010-10-27 16:18 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
[not found] <AANLkTikwo++xG7SXzNPwmZgU2jbdLiMr0Wi+vaxFqb7o@mail.gmail.com>
2010-10-27 11:39 ` drivers/platform/x86: Backlight-Add-backlight-type-v2.patch Corentin Chary
2010-10-27 12:13 ` Matthew Garrett
2010-10-27 15:58 Joey Lee
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).