From: Jani Nikula <jani.nikula@intel.com>
To: Rodrigo Vivi <rodrigo.vivi@gmail.com>
Cc: intel-gfx <intel-gfx@lists.freedesktop.org>,
Paulo Zanoni <paulo.r.zanoni@intel.com>,
Rodrigo Vivi <rodrigo.vivi@intel.com>
Subject: Re: [PATCH] drm/i915: Fix and clean BDW PCH identification
Date: Wed, 21 Jan 2015 19:22:00 +0200 [thread overview]
Message-ID: <877fwg59s7.fsf@intel.com> (raw)
In-Reply-To: <CABVU7+uiPVuPJaJWR5y_j7khVyBHSrD+=62oDrDU=XvBu_DJVg@mail.gmail.com>
On Wed, 21 Jan 2015, Rodrigo Vivi <rodrigo.vivi@gmail.com> wrote:
> On Wed, Jan 21, 2015 at 8:08 AM, Jani Nikula <jani.nikula@intel.com> wrote:
>> On Tue, 20 Jan 2015, Rodrigo Vivi <rodrigo.vivi@intel.com> wrote:
>>> It seems in the past we have BDW with PCH not been propperly identified
>>> and we force it to be LPT and we were warning !IS_HASWELL on propper identification.
>>>
>>> Now that products are out there we are receiveing logs with this incorrect WARN.
>>> And also according to local tests on all production BDW here ULT or HALO we don't
>>> need this force anymore. So let's clean this block for real.
>>>
>>> Reference: https://bugs.freedesktop.org/attachment.cgi?id=110972
>>>
>>> Cc: Jani Nikula <jani.nikula@intel.com>
>>> Cc: Paulo Zanoni <paulo.r.zanoni@intel.com>
>>> Cc: Xion Zhang <xiong.y.zhang@intel.com>
>>> Signed-off-by: Rodrigo Vivi <rodrigo.vivi@intel.com>
>>> ---
>>> drivers/gpu/drm/i915/i915_drv.c | 9 ++-------
>>> 1 file changed, 2 insertions(+), 7 deletions(-)
>>>
>>> diff --git a/drivers/gpu/drm/i915/i915_drv.c b/drivers/gpu/drm/i915/i915_drv.c
>>> index 308774f..1d14311 100644
>>> --- a/drivers/gpu/drm/i915/i915_drv.c
>>> +++ b/drivers/gpu/drm/i915/i915_drv.c
>>> @@ -462,14 +462,9 @@ void intel_detect_pch(struct drm_device *dev)
>>> } else if (id == INTEL_PCH_LPT_DEVICE_ID_TYPE) {
>>> dev_priv->pch_type = PCH_LPT;
>>> DRM_DEBUG_KMS("Found LynxPoint PCH\n");
>>> - WARN_ON(!IS_HASWELL(dev));
>>> + WARN_ON(!IS_HASWELL(dev) && !IS_BROADWELL(dev));
>>> WARN_ON(IS_HSW_ULT(dev));
>>> - } else if (IS_BROADWELL(dev)) {
>>> - dev_priv->pch_type = PCH_LPT;
>>> - dev_priv->pch_id =
>>> - INTEL_PCH_LPT_LP_DEVICE_ID_TYPE;
>>> - DRM_DEBUG_KMS("This is Broadwell, assuming "
>>> - "LynxPoint LP PCH\n");
>>> + WARN_ON(IS_BDW_ULT(dev));
>>> } else if (id == INTEL_PCH_LPT_LP_DEVICE_ID_TYPE) {
>>> dev_priv->pch_type = PCH_LPT;
>>> DRM_DEBUG_KMS("Found LynxPoint LP PCH\n");
>>
>> This will now produce a warn with the BDW ULT & LPT LP combo.
>
> No it wont. The LPT_LP identification is on the following block while
> the WARN is on LPT (non LP) block.
I meant that the LPT LP block has
WARN_ON(!IS_HASWELL(dev));
WARN_ON(!IS_HSW_ULT(dev));
which will now warn on BDW.
BR,
Jani.
>
>>
>> BR,
>> Jani.
>>
>>> --
>>> 2.1.0
>>>
>>
>> --
>> Jani Nikula, Intel Open Source Technology Center
>> _______________________________________________
>> Intel-gfx mailing list
>> Intel-gfx@lists.freedesktop.org
>> http://lists.freedesktop.org/mailman/listinfo/intel-gfx
>
>
>
> --
> Rodrigo Vivi
> Blog: http://blog.vivi.eng.br
--
Jani Nikula, Intel Open Source Technology Center
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2015-01-21 17:44 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-20 18:18 [PATCH] drm/i915: Fix and clean BDW PCH identification Rodrigo Vivi
2015-01-21 3:08 ` shuang.he
2015-01-21 16:08 ` Jani Nikula
2015-01-21 16:45 ` Rodrigo Vivi
2015-01-21 17:22 ` Jani Nikula [this message]
2015-01-21 18:33 ` Rodrigo Vivi
2015-01-21 18:40 ` Jani Nikula
2015-01-22 6:15 ` Daniel Vetter
2015-01-21 19:12 ` Jani Nikula
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=877fwg59s7.fsf@intel.com \
--to=jani.nikula@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=paulo.r.zanoni@intel.com \
--cc=rodrigo.vivi@gmail.com \
--cc=rodrigo.vivi@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