From: Jani Nikula <jani.nikula@intel.com>
To: "Vivi, Rodrigo" <rodrigo.vivi@intel.com>
Cc: "intel-gfx@lists.freedesktop.org"
<intel-gfx@lists.freedesktop.org>,
Rainer Koenig <Rainer.Koenig@ts.fujitsu.com>,
"stable@vger.kernel.org" <stable@vger.kernel.org>
Subject: Re: [PATCH] drm/i915: don't warn about Skylake CPU - KabyPoint PCH combo
Date: Thu, 02 Feb 2017 16:27:48 +0200 [thread overview]
Message-ID: <877f58zmzf.fsf@intel.com> (raw)
In-Reply-To: <DFF9509B-2A0E-4340-9BF5-795662CA0588@intel.com>
On Wed, 01 Feb 2017, "Vivi, Rodrigo" <rodrigo.vivi@intel.com> wrote:
> Reviewed-by: Rodrigo Vivi <rodrigo.vivi@intel.com>
Pushed to drm-intel-next-queued, thanks for the review.
BR,
Jani.
>
>> On Feb 1, 2017, at 5:46 AM, Nikula, Jani <jani.nikula@intel.com> wrote:
>>
>> Apparently there are machines out there with Skylake CPU and KabyPoint
>> PCH. Judging from our driver code, there doesn't seem to be any code
>> paths that would do anything different between SunrisePoint and
>> KabyPoint PCHs, so it would seem okay to accept the combo without
>> warnings.
>>
>> Fixes: 22dea0be50b2 ("drm/i915: Introduce Kabypoint PCH for Kabylake H/DT.")
>> References: https://lists.freedesktop.org/archives/intel-gfx/2017-February/118611.html
>> Reported-by: Rainer Koenig <Rainer.Koenig@ts.fujitsu.com>
>> Cc: Rainer Koenig <Rainer.Koenig@ts.fujitsu.com>
>> Cc: Rodrigo Vivi <rodrigo.vivi@intel.com>
>> Cc: <stable@vger.kernel.org> # v4.8+
>> Signed-off-by: Jani Nikula <jani.nikula@intel.com>
>> ---
>> drivers/gpu/drm/i915/i915_drv.c | 3 ++-
>> 1 file changed, 2 insertions(+), 1 deletion(-)
>>
>> diff --git a/drivers/gpu/drm/i915/i915_drv.c b/drivers/gpu/drm/i915/i915_drv.c
>> index 267d5f8c49e1..6a430648fa71 100644
>> --- a/drivers/gpu/drm/i915/i915_drv.c
>> +++ b/drivers/gpu/drm/i915/i915_drv.c
>> @@ -213,7 +213,8 @@ static void intel_detect_pch(struct drm_i915_private *dev_priv)
>> } else if (id == INTEL_PCH_KBP_DEVICE_ID_TYPE) {
>> dev_priv->pch_type = PCH_KBP;
>> DRM_DEBUG_KMS("Found KabyPoint PCH\n");
>> - WARN_ON(!IS_KABYLAKE(dev_priv));
>> + WARN_ON(!IS_SKYLAKE(dev_priv) &&
>> + !IS_KABYLAKE(dev_priv));
>> } else if ((id == INTEL_PCH_P2X_DEVICE_ID_TYPE) ||
>> (id == INTEL_PCH_P3X_DEVICE_ID_TYPE) ||
>> ((id == INTEL_PCH_QEMU_DEVICE_ID_TYPE) &&
>> --
>> 2.1.4
>>
--
Jani Nikula, Intel Open Source Technology Center
WARNING: multiple messages have this Message-ID (diff)
From: Jani Nikula <jani.nikula@intel.com>
To: "Vivi\, Rodrigo" <rodrigo.vivi@intel.com>
Cc: "intel-gfx\@lists.freedesktop.org"
<intel-gfx@lists.freedesktop.org>,
Rainer Koenig <Rainer.Koenig@ts.fujitsu.com>,
"stable\@vger.kernel.org" <stable@vger.kernel.org>
Subject: Re: [PATCH] drm/i915: don't warn about Skylake CPU - KabyPoint PCH combo
Date: Thu, 02 Feb 2017 16:27:48 +0200 [thread overview]
Message-ID: <877f58zmzf.fsf@intel.com> (raw)
In-Reply-To: <DFF9509B-2A0E-4340-9BF5-795662CA0588@intel.com>
On Wed, 01 Feb 2017, "Vivi, Rodrigo" <rodrigo.vivi@intel.com> wrote:
> Reviewed-by: Rodrigo Vivi <rodrigo.vivi@intel.com>
Pushed to drm-intel-next-queued, thanks for the review.
BR,
Jani.
>
>> On Feb 1, 2017, at 5:46 AM, Nikula, Jani <jani.nikula@intel.com> wrote:
>>
>> Apparently there are machines out there with Skylake CPU and KabyPoint
>> PCH. Judging from our driver code, there doesn't seem to be any code
>> paths that would do anything different between SunrisePoint and
>> KabyPoint PCHs, so it would seem okay to accept the combo without
>> warnings.
>>
>> Fixes: 22dea0be50b2 ("drm/i915: Introduce Kabypoint PCH for Kabylake H/DT.")
>> References: https://lists.freedesktop.org/archives/intel-gfx/2017-February/118611.html
>> Reported-by: Rainer Koenig <Rainer.Koenig@ts.fujitsu.com>
>> Cc: Rainer Koenig <Rainer.Koenig@ts.fujitsu.com>
>> Cc: Rodrigo Vivi <rodrigo.vivi@intel.com>
>> Cc: <stable@vger.kernel.org> # v4.8+
>> Signed-off-by: Jani Nikula <jani.nikula@intel.com>
>> ---
>> drivers/gpu/drm/i915/i915_drv.c | 3 ++-
>> 1 file changed, 2 insertions(+), 1 deletion(-)
>>
>> diff --git a/drivers/gpu/drm/i915/i915_drv.c b/drivers/gpu/drm/i915/i915_drv.c
>> index 267d5f8c49e1..6a430648fa71 100644
>> --- a/drivers/gpu/drm/i915/i915_drv.c
>> +++ b/drivers/gpu/drm/i915/i915_drv.c
>> @@ -213,7 +213,8 @@ static void intel_detect_pch(struct drm_i915_private *dev_priv)
>> } else if (id == INTEL_PCH_KBP_DEVICE_ID_TYPE) {
>> dev_priv->pch_type = PCH_KBP;
>> DRM_DEBUG_KMS("Found KabyPoint PCH\n");
>> - WARN_ON(!IS_KABYLAKE(dev_priv));
>> + WARN_ON(!IS_SKYLAKE(dev_priv) &&
>> + !IS_KABYLAKE(dev_priv));
>> } else if ((id == INTEL_PCH_P2X_DEVICE_ID_TYPE) ||
>> (id == INTEL_PCH_P3X_DEVICE_ID_TYPE) ||
>> ((id == INTEL_PCH_QEMU_DEVICE_ID_TYPE) &&
>> --
>> 2.1.4
>>
--
Jani Nikula, Intel Open Source Technology Center
next prev parent reply other threads:[~2017-02-02 14:27 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-01 13:46 [PATCH] drm/i915: don't warn about Skylake CPU - KabyPoint PCH combo Jani Nikula
2017-02-01 13:46 ` Jani Nikula
2017-02-01 14:57 ` Vivi, Rodrigo
2017-02-02 14:27 ` Jani Nikula [this message]
2017-02-02 14:27 ` Jani Nikula
2017-02-01 16:24 ` ✓ Fi.CI.BAT: success for " Patchwork
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=877f58zmzf.fsf@intel.com \
--to=jani.nikula@intel.com \
--cc=Rainer.Koenig@ts.fujitsu.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=rodrigo.vivi@intel.com \
--cc=stable@vger.kernel.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.