diff options
author | Javier Martinez Canillas <javierm@redhat.com> | 2023-07-13 11:58:07 +0300 |
---|---|---|
committer | Javier Martinez Canillas <javierm@redhat.com> | 2023-07-13 15:01:49 +0300 |
commit | 7dae503584a1f9fb761fbdfa2efcb6f8a029a0ea (patch) | |
tree | 1d991b9b80f5bd6621539cd2e9c40dd6348fc33f /tools/perf/scripts/python/export-to-postgresql.py | |
parent | 36672dda2eb715af99e9abbcdc400d46598b691c (diff) | |
download | linux-7dae503584a1f9fb761fbdfa2efcb6f8a029a0ea.tar.xz |
drm/ssd130x: Change pixel format used to compute the buffer size
The commit e254b584dbc0 ("drm/ssd130x: Remove hardcoded bits-per-pixel in
ssd130x_buf_alloc()") used a pixel format info rather than a hardcoded bpp
to calculate the size of the buffer allocated to store the native pixels.
But it wrongly used the DRM_FORMAT_C1 fourcc pixel format. That is for
color-indexed frame buffer formats, while the ssd103x controllers don't
support different single-channel colors nor a Color Lookup Table (CLUT).
So the correct pixel format to use in this case is DRM_FORMAT_R1 instead.
Since both formats use a eight pixels/byte, there is no functional change
in practice by this patch. Still, the correct pixel format should be used.
Suggested-by: Geert Uytterhoeven <geert@linux-m68k.org>
Signed-off-by: Javier Martinez Canillas <javierm@redhat.com>
Reviewed-by: Geert Uytterhoeven <geert@linux-m68k.org>
Reviewed-by: Thomas Zimmermann <tzimmermann@suse.de>
Link: https://patchwork.freedesktop.org/patch/msgid/20230713085859.907127-1-javierm@redhat.com
Diffstat (limited to 'tools/perf/scripts/python/export-to-postgresql.py')
0 files changed, 0 insertions, 0 deletions