From: Matthew Garrett <mjg59@srcf.ucam.org>
To: Richard Purdie <rpurdie@linux.intel.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
linux-kernel@vger.kernel.org, nouveau@lists.freedesktop.org,
dri-devel@lists.freedesktop.org, intel-gfx@lists.freedesktop.org,
linux-acpi@vger.kernel.org, lenb@kernel.org
Subject: Re: [PATCH 1/5] Backlight: Add backlight type
Date: Mon, 22 Nov 2010 12:30:50 +0000 [thread overview]
Message-ID: <20101122123050.GA5385@srcf.ucam.org> (raw)
In-Reply-To: <1290421020.1272.16707.camel@rex>
On Mon, Nov 22, 2010 at 10:17:00AM +0000, Richard Purdie wrote:
> I also want to make sure you think this patch is going to scale with
> multiple GPU output machines? Thats the main reason I've held off any
> patch like this as it doesn't help solve that problem as far as I can
> tell. Yes, we have the device parent information and I see later in the
> patch series you ensure the backlight is registered against the
> connector which is good. If you have an ACPI "firmware" control that you
> say should always be preferred, how do we know which connector device
> that corresponds to in the multiple output case? From that point of view
> this model falls apart?
The ACPI device will point at the correct PCI device. Associating it
with the appropriate connector is theoretically possible in the case of
open drivers, but I hadn't seen it as a high priority since (in
practice) there's no situations where an ACPI interface will be able to
control more than one backlight.
--
Matthew Garrett | mjg59@srcf.ucam.org
next prev parent reply other threads:[~2010-11-22 12:30 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-19 15:53 [PATCH 1/5] Backlight: Add backlight type Matthew Garrett
2010-11-19 15:53 ` [PATCH 2/5] i915: Add native backlight control Matthew Garrett
2010-11-19 15:53 ` Matthew Garrett
2010-11-19 15:53 ` [PATCH 3/5] radeon: Expose backlight class device for legacy LVDS encoder Matthew Garrett
2010-11-19 15:53 ` [PATCH 4/5] nouveau: Change the backlight parent device to the connector, not the PCI dev Matthew Garrett
2010-11-19 15:53 ` [PATCH 5/5] ACPI: Tie ACPI backlight devices to PCI devices if possible Matthew Garrett
2010-11-19 20:05 ` [PATCH 1/5] Backlight: Add backlight type Andrew Morton
2010-11-19 20:05 ` Andrew Morton
2010-11-19 20:25 ` Matthew Garrett
2010-11-19 20:35 ` Andrew Morton
2010-11-22 10:17 ` Richard Purdie
2010-11-22 12:30 ` Matthew Garrett [this message]
2010-11-22 13:35 ` Richard Purdie
2010-11-22 13:40 ` Matthew Garrett
2011-01-14 19:24 Matthew Garrett
2011-01-15 14:41 Sedat Dilek
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=20101122123050.GA5385@srcf.ucam.org \
--to=mjg59@srcf.ucam.org \
--cc=akpm@linux-foundation.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nouveau@lists.freedesktop.org \
--cc=rpurdie@linux.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.