From: Henry Zhang <henryzhang62@gmail.com>
To: henryzhang62@gmail.com, Maxime Ripard <mripard@kernel.org>,
Dave Stevenson <dave.stevenson@raspberrypi.com>
Cc: "Maíra Canal" <mcanal@igalia.com>,
"Raspberry Pi Kernel Maintenance" <kernel-list@raspberrypi.com>,
"Maarten Lankhorst" <maarten.lankhorst@linux.intel.com>,
"Thomas Zimmermann" <tzimmermann@suse.de>,
"David Airlie" <airlied@gmail.com>,
"Simona Vetter" <simona@ffwll.ch>,
dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org
Subject: [PATCH v2 0/3] drm/vc4: dsi: Make failed reads visible and recoverable
Date: Mon, 19 Oct 2026 10:49:27 -0700 [thread overview]
Message-ID: <20261019174930.7237-1-henryzhang62@gmail.com> (raw)
DSI reads on the Raspberry Pi 4 (vc4, DSI1) can fail in two ways that
the caller cannot handle:
- A peripheral that detected an error answers a read with an
Acknowledge and Error Report. vc4 copies its two bytes into the
caller's buffer and returns success, so the error bits look like
register contents (patch 1).
- After a read whose bus turnaround times out, every following DSI
transfer times out as well, until the display is switched off and on
(patch 2).
Patch 3 serializes host transfers, so that the recovery cannot reset
the block under a concurrent transfer.
These patches do not prevent the timeouts. With video running, vc4
does not keep commands within vertical blanking, so a read can still
collide with active video and time out. That is a separate issue; this
series makes such failures visible to the caller and recoverable
without a modeset.
Tested on a Raspberry Pi 4 with a 2-lane video mode panel at 120 Hz,
using a backport of this series to the Raspberry Pi 6.18 kernel and a
panel driver that retries failed reads up to 8 times: 499 of 500 reads
with video running and 1000 of 1000 with video stopped returned the
expected data, with no lock-up. Without the series, the first timeout
left DSI unusable.
Compile-tested on drm-misc-next (arm64 defconfig, DRM_VC4=m, W=1), each
patch on its own.
Changes in v2:
- Patch 2: restore the registers in the same order as pre_enable, and
call synchronize_irq() before the reset (Sashiko review)
- Patch 3: new, serialize host transfers (Sashiko review)
- Link to v1: https://lore.kernel.org/r/20261012190249.3167-1-henryzhang62@gmail.com
Henry Zhang (3):
drm/vc4: dsi: Don't return error reports as read data
drm/vc4: dsi: Recover from a timed-out transfer
drm/vc4: dsi: Serialize host transfers
drivers/gpu/drm/vc4/vc4_dsi.c | 145 ++++++++++++++++++++++++++++++++--
1 file changed, 138 insertions(+), 7 deletions(-)
base-commit: e6bb593b800813788dc16179d1305747ff974d00
--
2.47.3
next reply other threads:[~2026-10-19 17:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-19 17:49 Henry Zhang [this message]
2026-10-19 17:49 ` [PATCH v2 1/3] drm/vc4: dsi: Don't return error reports as read data Henry Zhang
2026-10-19 17:49 ` [PATCH v2 2/3] drm/vc4: dsi: Recover from a timed-out transfer Henry Zhang
2026-10-19 17:49 ` [PATCH v2 3/3] drm/vc4: dsi: Serialize host transfers Henry Zhang
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=20261019174930.7237-1-henryzhang62@gmail.com \
--to=henryzhang62@gmail.com \
--cc=airlied@gmail.com \
--cc=dave.stevenson@raspberrypi.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=kernel-list@raspberrypi.com \
--cc=linux-kernel@vger.kernel.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=mcanal@igalia.com \
--cc=mripard@kernel.org \
--cc=simona@ffwll.ch \
--cc=tzimmermann@suse.de \
/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®