From: Damien Lespiau <damien.lespiau@intel.com>
To: intel-gfx@lists.freedesktop.org
Cc: benjamin.widawsky@intel.com
Subject: Re: Supporting fused display configurations
Date: Thu, 5 Dec 2013 14:03:36 +0000 [thread overview]
Message-ID: <20131205140336.GA30349@strange.icx.intel.com> (raw)
In-Reply-To: <1386251782-21176-1-git-send-email-damien.lespiau@intel.com>
On Thu, Dec 05, 2013 at 01:56:15PM +0000, Damien Lespiau wrote:
> A while ago, Ben added support for Quanta devices that had the display hardware
> fused off. We can a bit more general than that by reading the FUSE_STRAP
> register and setting num_pipes to 0 when detecting such condition.
I'm an idiot and relied on auto-completion that completed num_ to
num_planes instead of num_pipes... v2 to follow...
--
Damien
next prev parent reply other threads:[~2013-12-05 14:05 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-05 13:56 Supporting fused display configurations Damien Lespiau
2013-12-05 13:56 ` [PATCH 1/7] drm/i915: Make the intel_device_info structure kept in dev_priv writable Damien Lespiau
2013-12-05 13:56 ` [PATCH 2/7] drm/i915: Move num_plane to the intel_device_info structure Damien Lespiau
2013-12-05 13:56 ` [PATCH 3/7] drm/i915: Consolidate FUSE_STRAP in one set of defines Damien Lespiau
2013-12-05 13:56 ` [PATCH 4/7] drm/i915: Disable display when fused off Damien Lespiau
2013-12-05 14:11 ` [PATCH 4/7 v2] " Damien Lespiau
2013-12-05 13:56 ` [PATCH 5/7] drm/i915: Support fused off pipe C configurations Damien Lespiau
2013-12-05 14:13 ` [PATCH 5/7 v2] " Damien Lespiau
2013-12-05 13:56 ` [PATCH 6/7] drm/i915: Remove the Quanta special case Damien Lespiau
2013-12-05 13:56 ` [PATCH 7/7] drm/i915: Use I915_MAX_PIPES in the pipe/plane_to_crtc_mapping definitions Damien Lespiau
2013-12-05 14:03 ` Damien Lespiau [this message]
2013-12-05 14:09 ` Supporting fused display configurations Chris Wilson
2013-12-05 14:21 ` Damien Lespiau
2013-12-05 18:19 ` Ben Widawsky
2013-12-05 18:25 ` Damien Lespiau
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=20131205140336.GA30349@strange.icx.intel.com \
--to=damien.lespiau@intel.com \
--cc=benjamin.widawsky@intel.com \
--cc=intel-gfx@lists.freedesktop.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 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.