From: Tobias Johansson <tobias.johansson@axis.com>
To: Alex Lanzano <lanzano.alex@gmail.com>,
Maarten Lankhorst <maarten.lankhorst@linux.intel.com>,
Maxime Ripard <mripard@kernel.org>,
Thomas Zimmermann <tzimmermann@suse.de>,
David Airlie <airlied@gmail.com>, Simona Vetter <simona@ffwll.ch>,
Dmitry Baryshkov <lumag@kernel.org>,
"Mehdi Djait" <mehdi.djait@bootlin.com>,
Uwe Kleine-König <u.kleine-koenig@baylibre.com>
Cc: <dri-devel@lists.freedesktop.org>, <linux-kernel@vger.kernel.org>,
"Tobias Johansson" <tobias.johansson@axis.com>, <kernel@axis.com>
Subject: [PATCH 2/2] drm/tiny: sharp-memory: avoid transmitting stale TX buffer data
Date: Mon, 30 Mar 2026 09:20:17 +0200 [thread overview]
Message-ID: <20260330-flickering-v1-2-5a192bf4b93d@axis.com> (raw)
In-Reply-To: <20260330-flickering-v1-0-5a192bf4b93d@axis.com>
When only a subset of lines is dirty, the TX buffer sent to the
panel contains stale line data from previous updates, resulting
in visible flickering on the display.
sharp_memory_update_display() transmits the entire TX buffer
regardless of how many lines were updated. Entries written by a
previous larger update linger in the buffer and
are retransmitted on every subsequent smaller update, overwriting
the newly written data with stale content.
Fix sharp_memory_update_display() to transmit only the buffer
entries populated by the current update.
Fixes: b8f9f21716fec ("drm/tiny: Add driver for Sharp Memory LCD")
Signed-off-by: Tobias Johansson <tobias.johansson@axis.com>
---
drivers/gpu/drm/tiny/sharp-memory.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/gpu/drm/tiny/sharp-memory.c b/drivers/gpu/drm/tiny/sharp-memory.c
index 595926ed660e..e7521fc6a010 100644
--- a/drivers/gpu/drm/tiny/sharp-memory.c
+++ b/drivers/gpu/drm/tiny/sharp-memory.c
@@ -155,7 +155,7 @@ static int sharp_memory_update_display(struct sharp_memory_device *smd,
u32 pitch = smd->pitch;
u8 vcom = smd->vcom;
u8 *tx_buffer = smd->tx_buffer;
- u32 tx_buffer_size = smd->tx_buffer_size;
+ u32 tx_len = 1 + (drm_rect_height(&clip) * pitch);
mutex_lock(&smd->tx_mutex);
@@ -165,7 +165,7 @@ static int sharp_memory_update_display(struct sharp_memory_device *smd,
sharp_memory_set_tx_buffer_addresses(&tx_buffer[1], clip, pitch);
sharp_memory_set_tx_buffer_data(&tx_buffer[2], fb, vmap, clip, pitch, fmtcnv_state);
- ret = sharp_memory_spi_write(smd->spi, tx_buffer, tx_buffer_size);
+ ret = sharp_memory_spi_write(smd->spi, tx_buffer, tx_len);
mutex_unlock(&smd->tx_mutex);
--
2.43.0
next prev parent reply other threads:[~2026-03-30 9:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-30 7:20 [PATCH 0/2] drm/tiny: sharp-memory: fix TX buffer corruption on partial update Tobias Johansson
2026-03-30 7:20 ` [PATCH 1/2] drm/tiny: sharp-memory: fix line address assignment " Tobias Johansson
2026-03-31 7:34 ` Claude review: " Claude Code Review Bot
2026-03-30 7:20 ` Tobias Johansson [this message]
2026-03-31 7:34 ` Claude review: drm/tiny: sharp-memory: avoid transmitting stale TX buffer data Claude Code Review Bot
2026-03-31 7:34 ` Claude review: drm/tiny: sharp-memory: fix TX buffer corruption on partial update 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=20260330-flickering-v1-2-5a192bf4b93d@axis.com \
--to=tobias.johansson@axis.com \
--cc=airlied@gmail.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=kernel@axis.com \
--cc=lanzano.alex@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lumag@kernel.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=mehdi.djait@bootlin.com \
--cc=mripard@kernel.org \
--cc=simona@ffwll.ch \
--cc=tzimmermann@suse.de \
--cc=u.kleine-koenig@baylibre.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