From: Lennart Poettering <mzxreary@0pointer.de>
To: Matthew Garrett <matthew.garrett@nebula.com>
Cc: "lenb@kernel.org" <lenb@kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"aaron.lu@intel.com" <aaron.lu@intel.com>,
"rjw@sisk.pl" <rjw@sisk.pl>,
"linux-acpi@vger.kernel.org" <linux-acpi@vger.kernel.org>,
"rjw@rjwysocki.net" <rjw@rjwysocki.net>,
"platform-driver-x86@vger.kernel.org"
<platform-driver-x86@vger.kernel.org>
Subject: Re: [PATCH] acpi/video: Add Lenovo IdeaPad Yoga 13 to acpi video detect blacklist
Date: Mon, 14 Oct 2013 18:24:46 +0200 [thread overview]
Message-ID: <20131014162445.GA11682@tango.0pointer.de> (raw)
In-Reply-To: <1381765708.24317.1.camel@x230.lan>
On Mon, 14.10.13 15:48, Matthew Garrett (matthew.garrett@nebula.com) wrote:
> On Mon, 2013-10-14 at 17:36 +0200, Lennart Poettering wrote:
>
> > Sorry, still not getting this. How should this ever work if the intel
> > video driver is compiled as kmod? That means that it isn't clear at all
> > when the kmod is going to be loaded or if it is loaded at all, you
> > cannot delay the registration of the acpi backlight that long, since the
> > time you'd have to wait is basically unbounded...
>
> See the intel_opregion_present() code in drivers/acpi/video.c. The ACPI
> driver won't bind to Intel hardware until i915 indicates that it should
> do so.
Hmm, OK, so this means that the acpi backlight will check whether i915
hw is around, and not whether the i915 driver is actually loaded? That
would work for me I guess. Thanks.
That means on win8 machines with win8 graphics there'll always be a
single backlight device in userspace only?
Lennart
--
Lennart Poettering - Red Hat, Inc.
next prev parent reply other threads:[~2013-10-14 16:24 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-14 0:55 [PATCH] acpi/video: Add Lenovo IdeaPad Yoga 13 to acpi video detect blacklist Lennart Poettering
2013-10-14 1:11 ` Aaron Lu
2013-10-14 2:23 ` Lennart Poettering
2013-10-14 2:36 ` Aaron Lu
2013-10-14 3:49 ` Lennart Poettering
2013-10-14 4:17 ` Aaron Lu
2013-10-14 15:36 ` Lennart Poettering
2013-10-14 15:48 ` Matthew Garrett
2013-10-14 15:48 ` Matthew Garrett
2013-10-14 16:24 ` Lennart Poettering [this message]
2013-10-14 16:26 ` Matthew Garrett
2013-10-14 16:26 ` Matthew Garrett
2013-10-15 23:42 ` Rafael J. Wysocki
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=20131014162445.GA11682@tango.0pointer.de \
--to=mzxreary@0pointer.de \
--cc=aaron.lu@intel.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=matthew.garrett@nebula.com \
--cc=platform-driver-x86@vger.kernel.org \
--cc=rjw@rjwysocki.net \
--cc=rjw@sisk.pl \
/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.