From: Rodrigo Vivi <rodrigo.vivi@intel.com>
To: Jiajia Liu <liujiajia@kylinos.cn>
Cc: "Jani Nikula" <jani.nikula@linux.intel.com>,
"Joonas Lahtinen" <joonas.lahtinen@linux.intel.com>,
"Tvrtko Ursulin" <tursulin@ursulin.net>,
"David Airlie" <airlied@gmail.com>,
"Simona Vetter" <simona@ffwll.ch>,
"Nemesa Garg" <nemesa.garg@intel.com>,
"Ville Syrjälä" <ville.syrjala@linux.intel.com>,
"Nitin Gote" <nitin.r.gote@intel.com>,
"Matt Roper" <matthew.d.roper@intel.com>,
intel-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] drm/i915/pch: fix warning for coffeelake on SunrisePoint PCH
Date: Tue, 22 Apr 2025 15:38:51 -0400 [thread overview]
Message-ID: <aAfwS_iUrgcIRZcX@intel.com> (raw)
In-Reply-To: <20250418060006.807216-1-liujiajia@kylinos.cn>
On Fri, Apr 18, 2025 at 02:00:06PM +0800, Jiajia Liu wrote:
> i915/pch reports a warning on a mini PC which has a CoffeeLake-S GT2
> [UHD Graphics 630] [8086:3e92] and an ISA bridge - H110 LPC Controller
> [8086:a143].
>
> [3.490423] i915 0000:00:02.0: [drm] Found coffeelake (device ID 3e92) integrated display version 9.00 stepping N/A
> [3.507160] ------------[ cut here ]------------
> [3.523341] i915 0000:00:02.0: [drm] drm_WARN_ON(!IS_PLATFORM(dev_priv, INTEL_SKYLAKE) && !IS_PLATFORM(dev_priv, INTEL_KABYLAKE))
> [3.523356] WARNING: CPU: 5 PID: 199 at drivers/gpu/drm/i915/soc/intel_pch.c:92 intel_pch_type+0x1c3/0xe10 [i915]
> [3.709685] CPU: 5 UID: 0 PID: 199 Comm: systemd-udevd Not tainted 6.15.0-rc2-up-fc96b232f8e7 #1 PREEMPT(voluntary)
Interesting finding! o.O
Well, please rebase your patch against drm-tip branch and resend it.
https://gitlab.freedesktop.org/drm/tip/
Feel free to resend with:
Reviewed-by: Rodrigo Vivi <rodrigo.vivi@intel.com>
>
> Signed-off-by: Jiajia Liu <liujiajia@kylinos.cn>
> ---
> drivers/gpu/drm/i915/soc/intel_pch.c | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/gpu/drm/i915/soc/intel_pch.c b/drivers/gpu/drm/i915/soc/intel_pch.c
> index 82dc7fbd1a3e..011bc9757e9b 100644
> --- a/drivers/gpu/drm/i915/soc/intel_pch.c
> +++ b/drivers/gpu/drm/i915/soc/intel_pch.c
> @@ -90,7 +90,8 @@ intel_pch_type(const struct drm_i915_private *dev_priv, unsigned short id)
> case INTEL_PCH_SPT_DEVICE_ID_TYPE:
> drm_dbg_kms(&dev_priv->drm, "Found SunrisePoint PCH\n");
> drm_WARN_ON(&dev_priv->drm,
> - !IS_SKYLAKE(dev_priv) && !IS_KABYLAKE(dev_priv));
> + !IS_SKYLAKE(dev_priv) && !IS_KABYLAKE(dev_priv) &&
> + !IS_COFFEELAKE(dev_priv));
> return PCH_SPT;
> case INTEL_PCH_SPT_LP_DEVICE_ID_TYPE:
> drm_dbg_kms(&dev_priv->drm, "Found SunrisePoint LP PCH\n");
> --
> 2.25.1
>
prev parent reply other threads:[~2025-04-22 19:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-18 6:00 [PATCH] drm/i915/pch: fix warning for coffeelake on SunrisePoint PCH Jiajia Liu
2025-04-22 11:47 ` ✗ Fi.CI.BUILD: failure for " Patchwork
2025-04-22 19:38 ` Rodrigo Vivi [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=aAfwS_iUrgcIRZcX@intel.com \
--to=rodrigo.vivi@intel.com \
--cc=airlied@gmail.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jani.nikula@linux.intel.com \
--cc=joonas.lahtinen@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=liujiajia@kylinos.cn \
--cc=matthew.d.roper@intel.com \
--cc=nemesa.garg@intel.com \
--cc=nitin.r.gote@intel.com \
--cc=simona@ffwll.ch \
--cc=tursulin@ursulin.net \
--cc=ville.syrjala@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 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.