From: Jani Nikula <jani.nikula@linux.intel.com>
To: Damien Lespiau <damien.lespiau@intel.com>,
Patrik Jakobsson <patrik.jakobsson@linux.intel.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH v3] drm/i915/skl/kbl: Add support for pipe fusing
Date: Tue, 02 Feb 2016 17:08:31 +0200 [thread overview]
Message-ID: <87oabz2lqo.fsf@intel.com> (raw)
In-Reply-To: <20160128113332.GD6553@strange.ger.corp.intel.com>
On Thu, 28 Jan 2016, Damien Lespiau <damien.lespiau@intel.com> wrote:
> On Wed, Jan 20, 2016 at 03:31:20PM +0100, Patrik Jakobsson wrote:
>> On SKL and KBL we can have pipe A/B/C disabled by fuse settings. The
>> pipes must be fused in descending order (e.g. C, B+C, A+B+C). We simply
>> decrease info->num_pipes if we find a valid fused out config.
>>
>> v2: Don't store the pipe disabled mask in device info (Damien)
>>
>> v3: Don't check FUSE_STRAP register for pipe c disabled
>>
>> Cc: Damien Lespiau <damien.lespiau@intel.com>
>> Signed-off-by: Patrik Jakobsson <patrik.jakobsson@linux.intel.com>
>
> Reviewed-by: Damien Lespiau <damien.lespiau@intel.com>
Pushed to drm-intel-next-queued, thanks for the patch and review.
BR,
Jani.
>
> (listing the valid cases would have made things simpler?)
--
Jani Nikula, Intel Open Source Technology Center
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx
prev parent reply other threads:[~2016-02-02 15:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-20 14:31 [PATCH v3] drm/i915/skl/kbl: Add support for pipe fusing Patrik Jakobsson
2016-01-21 13:20 ` ✓ Fi.CI.BAT: success for drm/i915/skl/kbl: Add support for pipe fusing (rev3) Patchwork
2016-01-28 11:33 ` [PATCH v3] drm/i915/skl/kbl: Add support for pipe fusing Damien Lespiau
2016-02-02 15:08 ` Jani Nikula [this message]
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=87oabz2lqo.fsf@intel.com \
--to=jani.nikula@linux.intel.com \
--cc=damien.lespiau@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=patrik.jakobsson@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