linux-usb.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Peter Stuge <peter@stuge.se>
To: "Noralf Trønnes" <noralf@tronnes.org>
Cc: hudson@trmm.net, markus@raatikainen.cc,
	Daniel Vetter <daniel.vetter@ffwll.ch>,
	linux-usb@vger.kernel.org, dri-devel@lists.freedesktop.org,
	th020394@gmail.com, lkundrak@v3.sk, pontus.fuchs@gmail.com,
	sam@ravnborg.org
Subject: Re: [PATCH v6 3/3] drm: Add GUD USB Display driver
Date: Thu, 25 Feb 2021 21:37:29 +0000	[thread overview]
Message-ID: <20210225213729.16532.qmail@stuge.se> (raw)
In-Reply-To: <ecd868f9-5877-63ea-7d3b-504147489b61@tronnes.org>

Noralf Trønnes wrote:
> > I forgot, but I have a two-tone (black/red) e-ink display here, and I
> > also have a 3-bpp RGB TFT display.
> 
> I've been anticipating the need for more formats, but I didn't want to
> add them without having a user. Otherwise I could end up adding stuff
> that would never be used. If you can test, there's no problem adding
> support for more formats now.

That's great! I can't promise to to test the three-color (b/w/r) e-ink
but I'll prepare a test setup for the RGB-TFT on the weekend.


> Building on that I would define a 2 bpp RG format like this in the driver:
> 
> static const struct drm_format_info gud_drm_format_rg11 = {
> 	.format = GUD_DRM_FORMAT_RG11,
> 	.num_planes = 1,
> 	.char_per_block = { 1, 0, 0 },
> 	.block_w = { 4, 0, 0 }, /* 4 pixels per block/byte */
> 	.block_h = { 1, 0, 0 },
> 	.hsub = 1,
> 	.vsub = 1,
> };
> 
> And a 3 bpp RGB format like this:
> 
> static const struct drm_format_info gud_drm_format_rgb111 = {
> 	.format = GUD_DRM_FORMAT_RGB111,
> 	.num_planes = 1,
> 	.char_per_block = { 1, 0, 0 },
> 	.block_w = { 2, 0, 0 }, /* 2 pixels per block/byte */
> 	.block_h = { 1, 0, 0 },
> 	.hsub = 1,
> 	.vsub = 1,
> };

I can't really comment; I know next to nothing about the drm subsystem. :)


> The MIPI DBI standard defines 2 ways to transmit 2x 3-bpp pixels in one
> byte (X=pad bit):
> - Option 1: X  X  R1 G1 B1 R2 G2 B2
> - Option 2: X  R1 G1 B1 X  R2 G2 B2
> 
> So maybe we should have GUD_DRM_FORMAT_RGB111_OPTION1 and
> GUD_DRM_FORMAT_RGB111_OPTION2?
> Or just use option 2 and let the display fix it up if needed?

It would of course be lovely to be able to set up an automated DMA from
a USB endpoint to the panel in the device and not have to touch the data,
but that would require the DRM driver to support all the combinations,
which quickly becomes complicated.


> What format does your 3 bpp display use?

It supports three formats:

- R1 G1 B1 R2 G2 B2
- R1 G1 B1 X R2 G2 B2 X (your option 2)
- R1 R2 R3 (simulated monochrome, same data bit to all three subpixels)


> And then something like this for the conversion function:
> 
> static size_t gud_xrgb8888_to_color(u8 *dst, const struct

All right!


//Peter

  reply	other threads:[~2021-02-25 21:38 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-19 12:16 [PATCH v6 0/3] GUD USB Display driver Noralf Trønnes
2021-02-19 12:17 ` [PATCH v6 1/3] drm/uapi: Add USB connector type Noralf Trønnes
2021-02-19 12:17 ` [PATCH v6 2/3] drm/probe-helper: Check epoch counter in output_poll_execute() Noralf Trønnes
2021-02-19 12:17 ` [PATCH v6 3/3] drm: Add GUD USB Display driver Noralf Trønnes
2021-02-19 21:42   ` Peter Stuge
2021-02-20 17:27     ` Noralf Trønnes
2021-02-26 12:09       ` Noralf Trønnes
2021-02-28  1:52         ` Peter Stuge
2021-02-28 21:04           ` Noralf Trønnes
2021-02-25  9:58   ` Peter Stuge
2021-02-25 18:06     ` Noralf Trønnes
2021-02-25 21:37       ` Peter Stuge [this message]
2021-02-26 12:18         ` Noralf Trønnes
     [not found]       ` <20210225213729.GG20076@stuge.se>
2021-03-01 18:31         ` Peter Stuge
2021-03-01 21:41           ` Noralf Trønnes

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=20210225213729.16532.qmail@stuge.se \
    --to=peter@stuge.se \
    --cc=daniel.vetter@ffwll.ch \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=hudson@trmm.net \
    --cc=linux-usb@vger.kernel.org \
    --cc=lkundrak@v3.sk \
    --cc=markus@raatikainen.cc \
    --cc=noralf@tronnes.org \
    --cc=pontus.fuchs@gmail.com \
    --cc=sam@ravnborg.org \
    --cc=th020394@gmail.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;
as well as URLs for NNTP newsgroup(s).