From: Jens Glathe <jens.glathe@oldschoolsolutions.biz>
To: Jani Nikula <jani.nikula@linux.intel.com>,
Jens Glathe via B4 Relay
<devnull+jens.glathe.oldschoolsolutions.biz@kernel.org>,
Rob Clark <robin.clark@oss.qualcomm.com>,
Dmitry Baryshkov <lumag@kernel.org>,
Abhinav Kumar <abhinav.kumar@linux.dev>,
Jessica Zhang <jesszhan0024@gmail.com>,
Sean Paul <sean@poorly.run>,
Marijn Suijten <marijn.suijten@somainline.org>,
David Airlie <airlied@gmail.com>, Simona Vetter <simona@ffwll.ch>
Cc: linux-arm-msm@vger.kernel.org, dri-devel@lists.freedesktop.org,
freedreno@lists.freedesktop.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] drm/msm/dp: add EDID re-read retry in msm_dp_panel_get_modes()
Date: Tue, 2 Jun 2026 20:26:32 +0200 [thread overview]
Message-ID: <240b394b-46c5-4d9b-85fa-981e2c3b9457@oldschoolsolutions.biz> (raw)
In-Reply-To: <d50293fab9e6292220b1817a8e85bbd89743b708@intel.com>
On 01.06.26 12:57, Jani Nikula wrote:
> Did you actually bisect to this commit? It's a bit of a surprise.
Hi Jani,
haha yes, sort of. I did a few weeks of bisecting for a different issue
[1] and this error message came up increasingly, so after resolving (or
so) the first one I took a shot at it. The commit was the result of git
blame for the line that the retry was programmed around. And as v2
shows, it was the right intuition.
[1]:
https://lore.kernel.org/all/20260530-typc-mux-modeset-v1-1-64b0281e2cd6@oldschoolsolutions.biz/
with best regards
Jens
next prev parent reply other threads:[~2026-06-02 18:41 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-31 21:16 [PATCH] drm/msm/dp: add EDID re-read retry in msm_dp_panel_get_modes() Jens Glathe via B4 Relay
2026-06-01 10:54 ` Jani Nikula
2026-06-01 10:57 ` Jani Nikula
2026-06-02 18:26 ` Jens Glathe [this message]
2026-06-01 11:20 ` Dmitry Baryshkov
2026-06-04 4:42 ` Claude review: " Claude Code Review Bot
2026-06-04 4:42 ` Claude Code Review Bot
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=240b394b-46c5-4d9b-85fa-981e2c3b9457@oldschoolsolutions.biz \
--to=jens.glathe@oldschoolsolutions.biz \
--cc=abhinav.kumar@linux.dev \
--cc=airlied@gmail.com \
--cc=devnull+jens.glathe.oldschoolsolutions.biz@kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=freedreno@lists.freedesktop.org \
--cc=jani.nikula@linux.intel.com \
--cc=jesszhan0024@gmail.com \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lumag@kernel.org \
--cc=marijn.suijten@somainline.org \
--cc=robin.clark@oss.qualcomm.com \
--cc=sean@poorly.run \
--cc=simona@ffwll.ch \
/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