From: Jan Kiszka <jan.kiszka@siemens.com>
To: Nicusor Huhulea <nicusor.huhulea@siemens.com>,
cip-dev@lists.cip-project.org
Subject: Re: [PATCH 6.1.y-cip 0/5] drm/i915: fixes for i915 Hot Plug Detection and build/runtime issues
Date: Thu, 24 Jul 2025 22:38:23 +0200 [thread overview]
Message-ID: <871fc209-a592-4fcb-bff7-d97337bdcb5d@siemens.com> (raw)
In-Reply-To: <20250723125427.59324-1-nicusor.huhulea@siemens.com>
On 23.07.25 14:54, Nicusor Huhulea wrote:
> Hello maintainers,
>
> This series addresses a defect observed on certain hardware platforms using Linux kernel 6.1.127 with the i915 driver. The issue concerns hot plug detection (HPD) logic,
> leading to unreliable or missed detection events on affected hardware. This is happening on some specific devices.
>
> ### Background
>
> Issue:
> On Simatic IPC227E, we observed unreliable or missing hot plug detection events, while on Simatic IPC227G (otherwise similar platform), expected hot plug behavior was maintained.
> Affected kernel:
> Most of the tests were conducted on 6.1.127 (manual/standalone kernel build, CIP/Isar context). But it also happens on 6.1.145-cip44
> Root cause analysis:
> Through testing and diagnostics, it appears that the HPD finite state machine or polling logic in kernel 6.1.127 is marginal for this edge case. Device IPC227E's behavior triggers
> this kernel edge case, likely due to slight variations in signal integrity, electrical margins, or internal component timing.
> Simatic IPC227G, functions as expected, possibly due to cleaner electrical signaling or more optimal timing characteristics, thus avoiding the triggering condition.
> Summary:
> This points to a hardware-software interaction where kernel code assumes nicer signaling or margins than IPC227E is able to provide, exposing logic gaps not visible on more robust hardware.
>
> ### Patches
>
> Patches 1-4:
> - Partial backports of upstream commits; only the relevant logic or fixes are applied, with other code omitted due to downstream divergence.
> Patch 5:
> - Additional modifications to ensure the driver builds and resolves run-time issues
> - Contains cherry-picked logic plus context/compatibility amendments as needed.
> - Together these fixes greatly improve reliability of hotplug detection on both devices, with no regression detected in our setups.
What is this series targeting, regular stable 6.1 or 6.1-cip only? If
the latter, why only cip? 6.1 stable is still alive, and this introduces
itself as fix.
Jan
--
Siemens AG, Foundational Technologies
Linux Expert Center
next prev parent reply other threads:[~2025-07-24 20:38 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-23 12:54 [PATCH 6.1.y-cip 0/5] drm/i915: fixes for i915 Hot Plug Detection and build/runtime issues Nicusor Huhulea
2025-07-23 12:54 ` [PATCH 6.1.y-cip 1/5] [PARTIAL BACKPORT]drm/i915: Fix HPD polling, reenabling the output poll work as needed Nicusor Huhulea
2025-07-23 12:54 ` [PATCH 6.1.y-cip 2/5] [PARTIAL BACKPORT]drm: Add an HPD poll helper to reschedule the poll work Nicusor Huhulea
2025-07-23 13:38 ` Greg KH
2025-07-23 17:18 ` nicusor.huhulea
2025-07-23 12:54 ` [PATCH 6.1.y-cip 3/5] [PARTIAL BACKPORT]drm/probe_helper: extract two helper functions Nicusor Huhulea
2025-07-23 12:54 ` [PATCH 6.1.y-cip 4/5] [PARTIAL BACKPORT]drm/probe-helper: enable and disable HPD on connectors Nicusor Huhulea
2025-07-23 12:54 ` [PATCH 6.1.y-cip 5/5] [PARTIAL BACKPORT]fixes for i915 Hot Plug Detection and build/runtime issues Nicusor Huhulea
2025-07-24 20:38 ` Jan Kiszka [this message]
2025-07-28 16:49 ` [PATCH 6.1.y-cip 0/5] drm/i915: fixes " nicusor.huhulea
2025-07-25 0:39 ` [cip-dev] " nobuhiro1.iwamatsu
2025-07-28 16:51 ` nicusor.huhulea
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=871fc209-a592-4fcb-bff7-d97337bdcb5d@siemens.com \
--to=jan.kiszka@siemens.com \
--cc=cip-dev@lists.cip-project.org \
--cc=nicusor.huhulea@siemens.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.