From: Jani Nikula <jani.nikula@linux.intel.com>
To: Dave Airlie <airlied@gmail.com>, Paulo Zanoni <przanoni@gmail.com>
Cc: "intel-gfx@lists.freedesktop.org"
<intel-gfx@lists.freedesktop.org>,
Paulo Zanoni <paulo.r.zanoni@intel.com>
Subject: Re: [PATCH] drm/i915: don't try DP_LINK_BW_5_4 on HSW ULX
Date: Wed, 30 Apr 2014 09:55:00 +0300 [thread overview]
Message-ID: <87d2fztigr.fsf@intel.com> (raw)
In-Reply-To: <CAPM=9tw_-ze6Czu1oS4P=NPq6LYVVcrEyrJ_smkC0xrSZLWkPQ@mail.gmail.com>
On Wed, 30 Apr 2014, Dave Airlie <airlied@gmail.com> wrote:
> On 30 April 2014 00:00, Paulo Zanoni <przanoni@gmail.com> wrote:
>> From: Paulo Zanoni <paulo.r.zanoni@intel.com>
>>
>> Because the docs say ULX doesn't support it on HSW.
>
> i read the exact same thing,
>
> Reviewed-by: Dave Airlie <airlied@redhat.com>
Pushed to -fixes, thanks for the patch and review.
BR,
Jani.
>
>>
>> Signed-off-by: Paulo Zanoni <paulo.r.zanoni@intel.com>
>> ---
>> drivers/gpu/drm/i915/i915_drv.h | 3 +++
>> drivers/gpu/drm/i915/intel_dp.c | 3 ++-
>> include/drm/i915_pciids.h | 4 ++--
>> 3 files changed, 7 insertions(+), 3 deletions(-)
>>
>>
>> This patch is completely untested!!!
>>
>>
>> diff --git a/drivers/gpu/drm/i915/i915_drv.h b/drivers/gpu/drm/i915/i915_drv.h
>> index e81feab..bdc612c 100644
>> --- a/drivers/gpu/drm/i915/i915_drv.h
>> +++ b/drivers/gpu/drm/i915/i915_drv.h
>> @@ -1816,6 +1816,9 @@ struct drm_i915_cmd_table {
>> #define IS_ULT(dev) (IS_HSW_ULT(dev) || IS_BDW_ULT(dev))
>> #define IS_HSW_GT3(dev) (IS_HASWELL(dev) && \
>> ((dev)->pdev->device & 0x00F0) == 0x0020)
>> +/* ULX machines are also considered ULT. */
>> +#define IS_HSW_ULX(dev) ((dev)->pdev->device == 0x0A0E || \
>> + (dev)->pdev->device == 0x0A1E)
>> #define IS_PRELIMINARY_HW(intel_info) ((intel_info)->is_preliminary)
>>
>> /*
>> diff --git a/drivers/gpu/drm/i915/intel_dp.c b/drivers/gpu/drm/i915/intel_dp.c
>> index 34ed143..87b0a51 100644
>> --- a/drivers/gpu/drm/i915/intel_dp.c
>> +++ b/drivers/gpu/drm/i915/intel_dp.c
>> @@ -105,7 +105,8 @@ intel_dp_max_link_bw(struct intel_dp *intel_dp)
>> case DP_LINK_BW_2_7:
>> break;
>> case DP_LINK_BW_5_4: /* 1.2 capable displays may advertise higher bw */
>> - if ((IS_HASWELL(dev) || INTEL_INFO(dev)->gen >= 8) &&
>> + if (((IS_HASWELL(dev) && !IS_HSW_ULX(dev)) ||
>> + INTEL_INFO(dev)->gen >= 8) &&
>> intel_dp->dpcd[DP_DPCD_REV] >= 0x12)
>> max_link_bw = DP_LINK_BW_5_4;
>> else
>> diff --git a/include/drm/i915_pciids.h b/include/drm/i915_pciids.h
>> index 24f3cad..5cd9165 100644
>> --- a/include/drm/i915_pciids.h
>> +++ b/include/drm/i915_pciids.h
>> @@ -191,8 +191,8 @@
>> INTEL_VGA_DEVICE(0x0A06, info), /* ULT GT1 mobile */ \
>> INTEL_VGA_DEVICE(0x0A16, info), /* ULT GT2 mobile */ \
>> INTEL_VGA_DEVICE(0x0A26, info), /* ULT GT3 mobile */ \
>> - INTEL_VGA_DEVICE(0x0A0E, info), /* ULT GT1 reserved */ \
>> - INTEL_VGA_DEVICE(0x0A1E, info), /* ULT GT2 reserved */ \
>> + INTEL_VGA_DEVICE(0x0A0E, info), /* ULX GT1 mobile */ \
>> + INTEL_VGA_DEVICE(0x0A1E, info), /* ULX GT2 mobile */ \
>> INTEL_VGA_DEVICE(0x0A2E, info), /* ULT GT3 reserved */ \
>> INTEL_VGA_DEVICE(0x0D06, info), /* CRW GT1 mobile */ \
>> INTEL_VGA_DEVICE(0x0D16, info), /* CRW GT2 mobile */ \
>> --
>> 1.9.2
>>
>> _______________________________________________
>> Intel-gfx mailing list
>> Intel-gfx@lists.freedesktop.org
>> http://lists.freedesktop.org/mailman/listinfo/intel-gfx
> _______________________________________________
> Intel-gfx mailing list
> Intel-gfx@lists.freedesktop.org
> http://lists.freedesktop.org/mailman/listinfo/intel-gfx
--
Jani Nikula, Intel Open Source Technology Center
prev parent reply other threads:[~2014-04-30 6:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-29 14:00 [PATCH] drm/i915: don't try DP_LINK_BW_5_4 on HSW ULX Paulo Zanoni
2014-04-29 14:08 ` Daniel Vetter
2014-04-29 21:43 ` Dave Airlie
2014-04-30 6:55 ` 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=87d2fztigr.fsf@intel.com \
--to=jani.nikula@linux.intel.com \
--cc=airlied@gmail.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=paulo.r.zanoni@intel.com \
--cc=przanoni@gmail.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