From: Thomas Zimmermann <tzimmermann@suse.de>
To: Javier Martinez Canillas <javierm@redhat.com>,
linux-kernel@vger.kernel.org
Cc: "Andy Shevchenko" <andriy.shevchenko@linux.intel.com>,
"Daniel Vetter" <daniel.vetter@ffwll.ch>,
"Geert Uytterhoeven" <geert@linux-m68k.org>,
linux-fbdev@vger.kernel.org, "Sam Ravnborg" <sam@ravnborg.org>,
dri-devel@lists.freedesktop.org,
"Noralf Trønnes" <noralf@tronnes.org>,
"Maxime Ripard" <maxime@cerno.tech>,
"Daniel Vetter" <daniel@ffwll.ch>,
"David Airlie" <airlied@linux.ie>,
"Maarten Lankhorst" <maarten.lankhorst@linux.intel.com>,
"Maxime Ripard" <mripard@kernel.org>
Subject: Re: [PATCH v2 1/4] drm/format-helper: Add drm_fb_{xrgb8888,gray8}_to_mono_reversed()
Date: Fri, 4 Feb 2022 21:35:05 +0100 [thread overview]
Message-ID: <de99712a-55d1-8910-e8a6-6a6254f58724@suse.de> (raw)
In-Reply-To: <b388f295-920a-b4fc-41ef-d090bdcd69e2@redhat.com>
[-- Attachment #1.1: Type: text/plain, Size: 4160 bytes --]
Hi
Am 04.02.22 um 20:31 schrieb Javier Martinez Canillas:
> Hello Thomas,
>
> Thanks a lot for your feedback.
>
> On 2/4/22 16:52, Thomas Zimmermann wrote:
>
> [snip]
>
>>> +static void drm_fb_gray8_to_mono_reversed_line(u8 *dst, const u8 *src, size_t pixels)
>>> +{
>>> + unsigned int xb, i;
>>> +
>>> + for (xb = 0; xb < pixels / 8; xb++) {
>>
>> In practice, all mode widths are multiples of 8 because VGA mandated it.
>> So it's ok-ish to assume this here. You should probably at least print a
>> warning somewhere if (pixels % 8 != 0)
>>
>
> Agreed.
After sending the mail, I realized that some code copies only parts of
the source around; specifically for damage handling. None of this is
aligned to multiple of 8. So the copying could start and end in the
middle of bytes. You'd need a pixel-offset value of some sort.
If you don't want to handle this now, maybe at least detect this case
and put a warning somewhere.
>
> [snip]
>
>>> + * DRM doesn't have native monochrome or grayscale support.
>>> + * Such drivers can announce the commonly supported XR24 format to userspace
>>> + * and use drm_fb_xrgb8888_to_gray8() to convert to grayscale and then this
>>> + * helper function to convert to the native format.
>>> + */
>>> +void drm_fb_gray8_to_mono_reversed(void *dst, unsigned int dst_pitch, const void *src,
>>> + const struct drm_rect *clip)
>>
>> There's a bug here. You want to pass in a drm_framebuffer as fourth
>> argument.
>>
>>> +{
>>> +
>>> + size_t height = drm_rect_height(clip);
>>> + size_t width = drm_rect_width(clip);
>>> + unsigned int y;
>>> + const u8 *gray8 = src;
>>> + u8 *mono = dst;
>>> +
>>> + if (!dst_pitch)
>>> + dst_pitch = width;
>>
>> The dst_pitch is given in bytes. You have to device by 8. Here would be
>> a good place to warn if (width % 8 != 0).
>>
>
> Ok.
>
>>> +
>>> + for (y = 0; y < height; y++) {
>>> + drm_fb_gray8_to_mono_reversed_line(mono, gray8, dst_pitch);
>>> + mono += (dst_pitch / 8);
>>
>> The dst_pitch is already given in bytes.
>>
>
> Yes, I know but for reversed mono we want only 1/8 of the width since we
> are converting from 8 bits per pixel greyscale to 1 bit per pixel mono.
>
> Or am I misunderstanding what you meant ?
I mean that if there are 80 pixel on a scanline, the value of dst_pitch
is already 10. These pitch values are always given in bytes.
Best regards
Thomas
>
>>> + gray8 += dst_pitch;
>>
>> 'gray8 += fb->pitches[0]' would be correct.
>>
>
> Ok.
>
> [snip]
>
>>> + */
>>> +void drm_fb_xrgb8888_to_mono_reversed(void *dst, unsigned int dst_pitch, const void *src,
>>> + const struct drm_framebuffer *fb,
>>> + const struct drm_rect *clip)
>>> +{
>>> + if (WARN_ON(fb->format->format != DRM_FORMAT_XRGB8888))
>>> + return;
>>> +
>>> + if (!dst_pitch)
>>> + dst_pitch = drm_rect_width(clip);
>>> +
>>> + drm_fb_xrgb8888_to_gray8(dst, dst_pitch, src, fb, clip);
>>> + drm_fb_gray8_to_mono_reversed(dst, dst_pitch, dst, fb, clip);
>>
>> Converting from dst into dst can give incorrect results. At some point
>> we probably want to add restrict qualifiers to these pointers, to help
>> the compiler with optimizing.
>>
>> A better approach here is to pull the per-line conversion from
>> drm_fb_xrgb8888_to_gray8() into a separate helper and implement a
>> line-by-line conversion here. something like this:
>>
>> drm_fb_xrgb8888_to_mono_reversed()
>> {
>> char *tmp = kmalloc(size of a single line of gray8)
>>
>> for (heigth) {
>> drm_fb_xrgb8888_to_gray8_line(tmp, ..., src, ...);
>> drm_fb_gray8_to_mono_reversed(dst, ..., tmp, ...);
>>
>> src += fb->pitches[0]
>> dst += dst_pitch;
>> }
>>
>> kfree(tmp);
>> }
>>
>
> I see. Yes, that sounds a much better approach. I'll change it in v3.
>
> Best regards,
--
Thomas Zimmermann
Graphics Driver Developer
SUSE Software Solutions Germany GmbH
Maxfeldstr. 5, 90409 Nürnberg, Germany
(HRB 36809, AG Nürnberg)
Geschäftsführer: Ivo Totev
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 840 bytes --]
next prev parent reply other threads:[~2022-02-04 20:35 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-04 13:43 [PATCH v2 0/4] drm/tiny: Add driver for Solomon SSD1307 OLED displays Javier Martinez Canillas
2022-02-04 13:43 ` [PATCH v2 1/4] drm/format-helper: Add drm_fb_{xrgb8888,gray8}_to_mono_reversed() Javier Martinez Canillas
2022-02-04 15:52 ` Thomas Zimmermann
2022-02-04 16:00 ` Thomas Zimmermann
2022-02-04 19:31 ` Javier Martinez Canillas
2022-02-04 20:35 ` Thomas Zimmermann [this message]
2022-02-04 21:02 ` Ilia Mirkin
2022-02-07 12:44 ` [PATCH v2 1/4] drm/format-helper: Add drm_fb_{xrgb8888, gray8}_to_mono_reversed() Thomas Zimmermann
2022-02-04 13:43 ` [PATCH v2 2/4] drm/tiny: Add driver for Solomon SSD130X OLED displays Javier Martinez Canillas
2022-02-04 14:26 ` Andy Shevchenko
2022-02-04 19:19 ` Javier Martinez Canillas
2022-02-05 13:04 ` Andy Shevchenko
2022-02-05 17:40 ` Javier Martinez Canillas
2022-02-04 13:43 ` [PATCH v2 3/4] MAINTAINERS: Add entry for Solomon SSD130X OLED displays DRM driver Javier Martinez Canillas
2022-02-04 13:57 ` Andy Shevchenko
2022-02-04 14:12 ` Javier Martinez Canillas
2022-02-04 14:28 ` Andy Shevchenko
2022-02-04 14:33 ` Javier Martinez Canillas
2022-02-04 13:43 ` [PATCH v2 4/4] dt-bindings: display: ssd1307fb: Add myself as binding co-maintainer Javier Martinez Canillas
2022-02-09 22:14 ` Rob Herring
2022-02-04 14:31 ` [PATCH v2 0/4] drm/tiny: Add driver for Solomon SSD1307 OLED displays Geert Uytterhoeven
2022-02-04 14:37 ` Javier Martinez Canillas
2022-02-08 14:19 ` Geert Uytterhoeven
2022-02-08 15:10 ` Javier Martinez Canillas
2022-02-08 15:18 ` Mark Brown
2022-02-08 15:32 ` Javier Martinez Canillas
2022-02-08 15:23 ` Geert Uytterhoeven
2022-02-08 15:40 ` Javier Martinez Canillas
2022-02-08 17:19 ` Javier Martinez Canillas
2022-02-09 13:47 ` Andy Shevchenko
2022-02-09 14:27 ` Geert Uytterhoeven
2022-02-09 14:42 ` Javier Martinez Canillas
2022-02-09 15:32 ` Andy Shevchenko
2022-02-10 8:32 ` Maxime Ripard
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=de99712a-55d1-8910-e8a6-6a6254f58724@suse.de \
--to=tzimmermann@suse.de \
--cc=airlied@linux.ie \
--cc=andriy.shevchenko@linux.intel.com \
--cc=daniel.vetter@ffwll.ch \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=geert@linux-m68k.org \
--cc=javierm@redhat.com \
--cc=linux-fbdev@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=maxime@cerno.tech \
--cc=mripard@kernel.org \
--cc=noralf@tronnes.org \
--cc=sam@ravnborg.org \
/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).