mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "CK Hu (胡俊光)" <ck.hu@mediatek.com>
To: "towwy321@gmail.com" <towwy321@gmail.com>,
	"chunkuang.hu@kernel.org" <chunkuang.hu@kernel.org>,
	"simona@ffwll.ch" <simona@ffwll.ch>,
	AngeloGioacchino Del Regno
	<angelogioacchino.delregno@collabora.com>,
	"airlied@gmail.com" <airlied@gmail.com>,
	"msp@baylibre.com" <msp@baylibre.com>,
	"p.zabel@pengutronix.de" <p.zabel@pengutronix.de>,
	"matthias.bgg@gmail.com" <matthias.bgg@gmail.com>,
	"granquet@baylibre.com" <granquet@baylibre.com>
Cc: "Rex-BC Chen (陳柏辰)" <Rex-BC.Chen@mediatek.com>,
	"dri-devel@lists.freedesktop.org"
	<dri-devel@lists.freedesktop.org>,
	"linux-mediatek@lists.infradead.org"
	<linux-mediatek@lists.infradead.org>,
	"linux-arm-kernel@lists.infradead.org"
	<linux-arm-kernel@lists.infradead.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v3] drm/mediatek: dp: Fix suspend/resume training failure
Date: Tue, 12 Aug 2025 00:46:26 +0000	[thread overview]
Message-ID: <c5abc7ac387a2bd51d000ca95bb90f37b097d0d0.camel@mediatek.com> (raw)
In-Reply-To: <c10ff37d3730bb1d434958d4d7f7002730fb117e.camel@mediatek.com>

On Mon, 2025-08-11 at 17:28 +0800, CK Hu wrote:
> On Sun, 2025-08-10 at 14:17 +0800, Haru Zheng wrote:
> > External email : Please do not click links or open attachments until you have verified the sender or the content.
> > 
> > 
> > When suspending and resuming DisplayPort via Type-C,
> > link training will be fail.
> > 
> > This patch backports the software IRQ handling for DP,
> > as eDP uses hardware IRQ while DP uses software IRQ.
> 
> This patch just modify the flow of DP, not eDP, so do not mention eDP here.
> For DP, I don't know why hardware IRQ would fail.
> HDMI support suspend and resume and it does not software IRQ.
> Please describe the hardware behavior when resume and point out why hardware would not trigger hardware hot plug interrupt.

In addition, resume flow is similar to boot up flow.

In boot up flow, the step is:
1. Plug in cable
2. Power on DP hardware.
3. DP HDP hardware interrupt happen.

So, in resume flow:
1. Plug in cable
2. Power on DP hardware
3. DP HDP hardware interrupt happen. (disappear?)

The flow is the same, why resume has no hardware interrupt?

Regards,
CK

> 
> > Additionally, cable_plugged_in is flipped in
> > mtk_dp_hpd_event to ensure correct hotplug detection
> > during resume.
> > 
> > These changes fix the DP training failure after suspend/resume.
> > 
> > Fixes: f70ac097a2cf ("drm/mediatek: Add MT8195 Embedded DisplayPort driver")
> > Signed-off-by: Haru Zheng <towwy321@gmail.com>
> > 
> > ---


      reply	other threads:[~2025-08-12  0:46 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-08-10  6:17 Haru Zheng
2025-08-11  9:28 ` CK Hu (胡俊光)
2025-08-12  0:46   ` CK Hu (胡俊光) [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=c5abc7ac387a2bd51d000ca95bb90f37b097d0d0.camel@mediatek.com \
    --to=ck.hu@mediatek.com \
    --cc=Rex-BC.Chen@mediatek.com \
    --cc=airlied@gmail.com \
    --cc=angelogioacchino.delregno@collabora.com \
    --cc=chunkuang.hu@kernel.org \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=granquet@baylibre.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mediatek@lists.infradead.org \
    --cc=matthias.bgg@gmail.com \
    --cc=msp@baylibre.com \
    --cc=p.zabel@pengutronix.de \
    --cc=simona@ffwll.ch \
    --cc=towwy321@gmail.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

all inboxes | Powered by JetHome®