From: Pin-yen Lin <treapking@chromium.org>
To: Xin Ji <xji@analogixsemi.com>,
Andrzej Hajda <andrzej.hajda@intel.com>,
Neil Armstrong <neil.armstrong@linaro.org>,
Robert Foss <rfoss@kernel.org>,
Laurent Pinchart <Laurent.pinchart@ideasonboard.com>,
Jonas Karlman <jonas@kwiboo.se>,
Jernej Skrabec <jernej.skrabec@gmail.com>
Cc: linux-kernel@vger.kernel.org, Sam Ravnborg <sam@ravnborg.org>,
dri-devel@lists.freedesktop.org,
Pin-yen Lin <treapking@chromium.org>,
Douglas Anderson <dianders@chromium.org>
Subject: [PATCH 0/2] Drop EDID cache for it6505/anx7625 when the bridge is powered off
Date: Tue, 24 Sep 2024 11:51:45 +0800 [thread overview]
Message-ID: <20240924035231.1163670-1-treapking@chromium.org> (raw)
This mainly fixes the use case when the user changes the external monitor
when the system is suspended. Without this series, both of the bridges
will skip the EDID read and returned the cached one after resume.
Apart from that, we also observed a DP-to-HDMI bridge expects an EDID read
after it's powered on. This patch also works around the problem by always
triggering the EDID read after the system resume.
Pin-yen Lin (2):
drm/bridge: anx7625: Drop EDID cache on bridge power off
drm/bridge: it6505: Drop EDID cache on bridge power off
drivers/gpu/drm/bridge/analogix/anx7625.c | 1 +
drivers/gpu/drm/bridge/ite-it6505.c | 2 ++
2 files changed, 3 insertions(+)
--
2.46.0.792.g87dc391469-goog
next reply other threads:[~2024-09-24 3:53 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-24 3:51 Pin-yen Lin [this message]
2024-09-24 3:51 ` [PATCH 1/2] drm/bridge: anx7625: Drop EDID cache on bridge power off Pin-yen Lin
2024-09-24 6:53 ` Dmitry Baryshkov
2024-09-24 16:42 ` Doug Anderson
2024-09-25 4:01 ` Pin-yen Lin
2024-09-24 3:51 ` [PATCH 2/2] drm/bridge: it6505: " Pin-yen Lin
2024-09-24 6:53 ` Dmitry Baryshkov
2024-09-24 17:48 ` Doug Anderson
2024-09-25 4:12 ` Pin-yen Lin
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=20240924035231.1163670-1-treapking@chromium.org \
--to=treapking@chromium.org \
--cc=Laurent.pinchart@ideasonboard.com \
--cc=andrzej.hajda@intel.com \
--cc=dianders@chromium.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=jernej.skrabec@gmail.com \
--cc=jonas@kwiboo.se \
--cc=linux-kernel@vger.kernel.org \
--cc=neil.armstrong@linaro.org \
--cc=rfoss@kernel.org \
--cc=sam@ravnborg.org \
--cc=xji@analogixsemi.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®