From: Herton Ronaldo Krzesinski <herton@mandriva.com.br>
To: Matthew Garrett <mjg59@srcf.ucam.org>
Cc: platform-driver-x86@vger.kernel.org, linux-acpi@vger.kernel.org
Subject: Re: [PATCH 2/2] ACPI video: add initial blacklist to use vendor drivers for backlight
Date: Tue, 18 Jan 2011 17:24:57 -0200 [thread overview]
Message-ID: <20110118172457.600e8974@gotham.conectiva> (raw)
In-Reply-To: <20110118185659.GA29173@srcf.ucam.org>
On Tue, 18 Jan 2011 18:56:59 +0000
Matthew Garrett <mjg59@srcf.ucam.org> wrote:
> On Tue, Jan 18, 2011 at 04:41:54PM -0200, Herton Ronaldo Krzesinski wrote:
>
> > This adds a list for shuttle devices I tested which doesn't have working
> > backlight support in acpi video, but works with workaround done in
> > shuttle-wmi driver, so for them, add dmi blacklist to use vendor driver.
>
> How about a hook to call from the shuttle-wmi driver to disable it? That
> way we wouldn't need the blacklist in the ACPI driver.
The problem is that acpi video driver needs to know the blacklist before it
registers its backlight class, not possible to do at run time (eg., disabling
it after video.ko is loaded). I don't know if there is a good solution to
this, besides adding this blacklist in video module.
>
> --
> Matthew Garrett | mjg59@srcf.ucam.org
--
[]'s
Herton
next prev parent reply other threads:[~2011-01-18 19:24 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-18 18:41 [PATCH 1/2] Add shuttle-wmi driver Herton Ronaldo Krzesinski
2011-01-18 18:41 ` [PATCH 2/2] ACPI video: add initial blacklist to use vendor drivers for backlight Herton Ronaldo Krzesinski
2011-01-18 18:56 ` Matthew Garrett
2011-01-18 19:24 ` Herton Ronaldo Krzesinski [this message]
2011-01-18 19:30 ` Matthew Garrett
2011-01-18 19:37 ` Herton Ronaldo Krzesinski
2011-01-18 19:44 ` Matthew Garrett
2011-04-07 8:36 ` Anisse Astier
2011-04-12 3:40 ` Len Brown
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=20110118172457.600e8974@gotham.conectiva \
--to=herton@mandriva.com.br \
--cc=linux-acpi@vger.kernel.org \
--cc=mjg59@srcf.ucam.org \
--cc=platform-driver-x86@vger.kernel.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