From: Marcus Folkesson <marcus.folkesson@gmail.com>
To: Thomas Zimmermann <tzimmermann@suse.de>
Cc: Javier Martinez Canillas <javierm@redhat.com>,
David Airlie <airlied@gmail.com>, Simona Vetter <simona@ffwll.ch>,
Maarten Lankhorst <maarten.lankhorst@linux.intel.com>,
Maxime Ripard <mripard@kernel.org>, Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
dri-devel@lists.freedesktop.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org,
Thomas Zimmermann <tzimmrmann@suse.de>
Subject: Re: [PATCH v3 2/3] drm/st7571-i2c: add support for Sitronix ST7571 LCD controller
Date: Tue, 8 Apr 2025 16:58:00 +0200 [thread overview]
Message-ID: <Z_U5eGy3vLgHZmz1@gmail.com> (raw)
In-Reply-To: <05fa4ac7-db09-401d-8680-0d71112d2239@suse.de>
[-- Attachment #1: Type: text/plain, Size: 1855 bytes --]
Hi,
On Tue, Apr 08, 2025 at 03:57:22PM +0200, Thomas Zimmermann wrote:
> Hi
>
> Am 08.04.25 um 15:20 schrieb Marcus Folkesson:
> [...]
> > >
> > > > +static int st7571_set_pixel_format(struct st7571_device *st7571,
> > > > + u32 pixel_format)
> > > > +{
> > > > + switch (pixel_format) {
> > > > + case DRM_FORMAT_C1:
> > > > + return st7571_set_color_mode(st7571, ST7571_COLOR_MODE_BLACKWHITE);
> > > > + case DRM_FORMAT_C2:
> > > > + return st7571_set_color_mode(st7571, ST7571_COLOR_MODE_GRAY);
> > > > + default:
> > > > + return -EINVAL;
> > > > + }
> > > These should be DRM_FORMAT_R1 and DRM_FORMAT_R2 and not C{1,2}. The former
> > > is for displays have a single color (i.e: grey) while the latter is when a
> > > pixel can have different color, whose values are defined by a CLUT table.
> > >
> > I see.
> > Does fbdev only works with CLUT formats? I get this error when I switch
> > to DRM_FORMAT_R{1,2}:
> >
> > [drm] Initialized st7571 1.0.0 for 0-003f on minor 0
> > st7571 0-003f: [drm] format C1 little-endian (0x20203143) not supported
> > st7571 0-003f: [drm] No compatible format found
> > st7571 0-003f: [drm] *ERROR* fbdev: Failed to setup emulation (ret=-22)
>
> For testing purposes, you can add the _R formats to the switch case at
>
> https://elixir.bootlin.com/linux/v6.13.7/source/drivers/gpu/drm/drm_fb_helper.c#L1246
>
> and see how it goes.
Still no penguin (same error as above).
The problem is that drm_mode_legacy_fb_format(), which is called from
drm_fbdev_shmem_driver_fbdev_probe -> drm_driver_legacy_fb_format -> drm_mode_legacy_fb_format
Sets the pixel format DRM_FORMAT_C{1,2} when bpp is 1 or 2.
So I don't think it is possible to use the _R formats with fbdev.
But I'm not sure?
>
> Best regards
> Thomas
Best regards,
Marcus Folkesson
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2025-04-08 14:58 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-08 7:04 [PATCH v3 0/3] Add support for Sitronix ST7571 LCD controller Marcus Folkesson
2025-04-08 7:04 ` [PATCH v3 1/3] dt-bindings: display: Add Sitronix ST7571 LCD Controller Marcus Folkesson
2025-04-08 16:16 ` Conor Dooley
2025-04-08 7:04 ` [PATCH v3 2/3] drm/st7571-i2c: add support for Sitronix ST7571 LCD controller Marcus Folkesson
2025-04-08 10:44 ` Javier Martinez Canillas
2025-04-08 11:01 ` Thomas Zimmermann
2025-04-08 11:34 ` Javier Martinez Canillas
2025-04-08 13:20 ` Marcus Folkesson
2025-04-08 13:57 ` Thomas Zimmermann
2025-04-08 14:58 ` Marcus Folkesson [this message]
2025-04-09 7:22 ` Thomas Zimmermann
2025-04-09 6:11 ` Javier Martinez Canillas
2025-04-09 6:41 ` Marcus Folkesson
2025-04-09 9:43 ` Javier Martinez Canillas
2025-04-09 13:25 ` Marcus Folkesson
2025-04-09 14:15 ` Javier Martinez Canillas
2025-04-11 6:47 ` Geert Uytterhoeven
2025-04-11 6:03 ` Marcus Folkesson
2025-04-11 8:26 ` Javier Martinez Canillas
2025-04-12 6:56 ` Marcus Folkesson
2025-04-14 7:55 ` Javier Martinez Canillas
2025-04-24 6:36 ` Marcus Folkesson
2025-04-24 6:45 ` Javier Martinez Canillas
2025-04-08 7:04 ` [PATCH v3 3/3] MAINTAINERS: add entry for Sitronix ST7571 LCD Controller Marcus Folkesson
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=Z_U5eGy3vLgHZmz1@gmail.com \
--to=marcus.folkesson@gmail.com \
--cc=airlied@gmail.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=javierm@redhat.com \
--cc=krzk+dt@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=mripard@kernel.org \
--cc=robh@kernel.org \
--cc=simona@ffwll.ch \
--cc=tzimmermann@suse.de \
--cc=tzimmrmann@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;
as well as URLs for NNTP newsgroup(s).