From: David Lechner <dlechner@baylibre.com>
To: "Javier Martinez Canillas" <javierm@redhat.com>,
"David Lechner" <david@lechnology.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>,
"Noralf Trønnes" <noralf@tronnes.org>,
"Dmitry Baryshkov" <lumag@kernel.org>
Cc: dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] drm/sitronix/st7586: fix bad pixel data due to byte swap
Date: Sat, 7 Mar 2026 17:27:36 -0600 [thread overview]
Message-ID: <ca862f40-1dbd-4056-9f70-8ec3d6789604@baylibre.com> (raw)
In-Reply-To: <87cy1iv9zb.fsf@ocarina.mail-host-address-is-not-set>
On 3/5/26 4:36 AM, Javier Martinez Canillas wrote:
> David Lechner <dlechner@baylibre.com> writes:
>
>> Correctly set dbi->write_memory_bpw for the ST7586 driver. This driver
>> is for a monochrome display that has an unusual data format, so the
>> default value set in mipi_dbi_spi_init() is not correct simply because
>> this controller is non-standard.
>>
>> Previously, we were using dbi->swap_bytes to make the same sort of
>> workaround, but it was removed in the same commit that added
>> dbi->write_memory_bpw, so we need to use the latter now to have the
>> correct behavior.
>>
>> This fixes every 3 columns of pixels being swapped on the display. There
>> are 3 pixels per byte, so the byte swap caused this effect.
>>
>> Fixes: df3fb27a74a4 ("drm/mipi-dbi: Make bits per word configurable for pixel transfers")
>> Signed-off-by: David Lechner <dlechner@baylibre.com>
>> ---
>
> The patch looks good to me.
>
> Reviewed-by: Javier Martinez Canillas <javierm@redhat.com>
>
I pushed this out with: dim push-branch drm-misc-fixes
(It's been 5 years since I've done that, so hopefully I did it right - I followed
the docs and it all seemed OK to me).
next prev parent reply other threads:[~2026-03-07 23:27 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-01 4:30 David Lechner
2026-03-02 7:46 ` Thomas Zimmermann
2026-03-03 9:36 ` Thomas Zimmermann
2026-03-05 10:36 ` Javier Martinez Canillas
2026-03-07 23:27 ` David Lechner [this message]
2026-03-09 9:25 ` Javier Martinez Canillas
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=ca862f40-1dbd-4056-9f70-8ec3d6789604@baylibre.com \
--to=dlechner@baylibre.com \
--cc=airlied@gmail.com \
--cc=david@lechnology.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=javierm@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lumag@kernel.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=mripard@kernel.org \
--cc=noralf@tronnes.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®