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 13:40:04 +0000 [thread overview]
Message-ID: <20101122134004.GA6870@srcf.ucam.org> (raw)
In-Reply-To: <1290432949.1272.16768.camel@rex>
On Mon, Nov 22, 2010 at 01:35:48PM +0000, Richard Purdie wrote:
> Its the reverse situation I worry about. Are there situations where
> there are multiple connectors on the PCI device and the ACPI interface
> just controls one of them but controls for the other connectors may
> exist?
Yes, that's certainly possible and it'd be desirable to fix this up, but
the same problem also applies to platform interfaces and it's typically
unfixable there. My userspace implementation looks at the connector type
to determine the best approach - if it's not LVDS or eDP it ignores the
firmware and platform interfaces, so you'll fall back to the raw
interface if it can provide support for your connector (presumably via
ddcci, although we don't have this implemented yet)
--
Matthew Garrett | mjg59@srcf.ucam.org
next prev parent reply other threads:[~2010-11-22 13:40 UTC|newest]
Thread overview: 13+ 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 ` [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:25 ` Matthew Garrett
2010-11-19 20:35 ` Andrew Morton
2010-11-22 10:17 ` Richard Purdie
2010-11-22 12:30 ` Matthew Garrett
2010-11-22 13:35 ` Richard Purdie
2010-11-22 13:40 ` Matthew Garrett [this message]
-- strict thread matches above, loose matches on Subject: below --
2011-01-14 19:24 Matthew Garrett
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=20101122134004.GA6870@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 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).