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 RESEND] drm/i915/pch: fix warning for coffeelake on SunrisePoint PCH
Date: Tue, 29 Apr 2025 17:19:44 -0400 [thread overview]
Message-ID: <aBFCcH5T56ZenY-K@intel.com> (raw)
In-Reply-To: <20250423073730.585181-1-liujiajia@kylinos.cn>
On Wed, Apr 23, 2025 at 03:37:30PM +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].
>
> [5.608723] i915 0000:00:02.0: [drm] Found coffeelake (device ID 3e92) integrated display version 9.00 stepping N/A
> [5.608969] ------------[ cut here ]------------
> [5.608972] i915 0000:00:02.0: [drm] drm_WARN_ON(!display->platform.skylake && !display->platform.kabylake)
> [5.608995] WARNING: CPU: 3 PID: 440 at drivers/gpu/drm/i915/display/intel_pch.c:126 intel_pch_type+0x1af/0xae0 [i915]
> [5.609317] CPU: 3 UID: 0 PID: 440 Comm: (udev-worker) Not tainted 6.15.0-rc3-drm-tip-2fa6469c618d #3 PREEMPT(voluntary)
>
> Signed-off-by: Jiajia Liu <liujiajia@kylinos.cn>
> Reviewed-by: Rodrigo Vivi <rodrigo.vivi@intel.com>
pushed to drm-intel-next. Thanks for the finding and the patch
> ---
> drivers/gpu/drm/i915/display/intel_pch.c | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/gpu/drm/i915/display/intel_pch.c b/drivers/gpu/drm/i915/display/intel_pch.c
> index 5035b63a4889..469e8a3cfb49 100644
> --- a/drivers/gpu/drm/i915/display/intel_pch.c
> +++ b/drivers/gpu/drm/i915/display/intel_pch.c
> @@ -125,7 +125,8 @@ intel_pch_type(const struct intel_display *display, unsigned short id)
> drm_dbg_kms(display->drm, "Found SunrisePoint PCH\n");
> drm_WARN_ON(display->drm,
> !display->platform.skylake &&
> - !display->platform.kabylake);
> + !display->platform.kabylake &&
> + !display->platform.coffeelake);
> return PCH_SPT;
> case INTEL_PCH_SPT_LP_DEVICE_ID_TYPE:
> drm_dbg_kms(display->drm, "Found SunrisePoint LP PCH\n");
> --
> 2.25.1
>
prev parent reply other threads:[~2025-04-29 21:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-23 7:37 [PATCH RESEND] drm/i915/pch: fix warning for coffeelake on SunrisePoint PCH Jiajia Liu
2025-04-25 21:53 ` ✓ i915.CI.BAT: success for drm/i915/pch: fix warning for coffeelake on SunrisePoint PCH (rev2) Patchwork
2025-04-26 7:41 ` ✗ i915.CI.Full: failure " Patchwork
2025-04-29 21:19 ` 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=aBFCcH5T56ZenY-K@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.