linux-fbdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Thomas Zimmermann <tzimmermann@suse.de>
To: Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
	Javier Martinez Canillas <javierm@redhat.com>
Cc: linux-kernel@vger.kernel.org, linux-fbdev@vger.kernel.org,
	"Geert Uytterhoeven" <geert@linux-m68k.org>,
	"Maxime Ripard" <maxime@cerno.tech>,
	"Daniel Vetter" <daniel.vetter@ffwll.ch>,
	dri-devel@lists.freedesktop.org,
	"Sam Ravnborg" <sam@ravnborg.org>,
	"Noralf Trønnes" <noralf@tronnes.org>,
	"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 v4 2/6] drm/format-helper: Add drm_fb_xrgb8888_to_mono_reversed()
Date: Fri, 11 Feb 2022 12:59:30 +0100	[thread overview]
Message-ID: <5cffc63b-c42a-df4c-7270-488735c9e014@suse.de> (raw)
In-Reply-To: <YgZEPo0ERFRloDyA@smile.fi.intel.com>


[-- Attachment #1.1: Type: text/plain, Size: 3342 bytes --]

Hi

Am 11.02.22 um 12:10 schrieb Andy Shevchenko:
> On Fri, Feb 11, 2022 at 10:19:23AM +0100, Javier Martinez Canillas wrote:
>> Add support to convert from XR24 to reversed monochrome for drivers that
>> control monochromatic display panels, that only have 1 bit per pixel.
>>
>> The function does a line-by-line conversion doing an intermediate step
>> first from XR24 to 8-bit grayscale and then to reversed monochrome.
>>
>> The drm_fb_gray8_to_mono_reversed_line() helper was based on code from
>> drivers/gpu/drm/tiny/repaper.c driver.
> 
> ...
> 
>> +static void drm_fb_gray8_to_mono_reversed_line(u8 *dst, const u8 *src, unsigned int pixels,
>> +					       unsigned int start_offset, unsigned int end_len)
>> +{
>> +	unsigned int xb, i;
>> +
>> +	for (xb = 0; xb < pixels; xb++) {
>> +		unsigned int start = 0, end = 8;
>> +		u8 byte = 0x00;
> 
>> +		if (xb == 0 && start_offset)
>> +			start = start_offset;
> 
> This is invariant to the loop, can be moved out.
> 
>> +		if (xb == pixels - 1 && end_len)
>> +			end = end_len;
> 
> Ditto. However it may require to factor out the following loop to a helper.

Splitting the loop is much nicer, but leaves corner cases where start 
and end is in the same byte. Doing this sounds like a premature 
optimization to me.

Best regards
Thomas

> 
>> +		for (i = start; i < end; i++) {
>> +			unsigned int x = xb * 8 + i;
>> +
>> +			byte >>= 1;
>> +			if (src[x] >> 7)
>> +				byte |= BIT(7);
>> +		}
>> +		*dst++ = byte;
>> +	}
>> +}
> 
> ...
> 
>> +	/*
>> +	 * The reversed mono destination buffer contains 1 bit per pixel
>> +	 * and destination scanlines have to be in multiple of 8 pixels.
>> +	 */
>> +	if (!dst_pitch)
>> +		dst_pitch = DIV_ROUND_UP(linepixels, 8);
> 
> round_up() ?
> 
>> +	WARN_ONCE(dst_pitch % 8 != 0, "dst_pitch is not a multiple of 8\n");
> 
> 
> I would move this to the if conditional, i.e.
> 
> 	if (dst_pitch)
> 		WARN_ONCE(dst_pitch % 8 != 0, "dst_pitch is not a multiple of 8\n");
> 	else
> 		dst_pitch = round_up(linepixels, 8);
> 
>> +	/*
>> +	 * The cma memory is write-combined so reads are uncached.
> 
> CMA
> 
>> +	 * Speed up by fetching one line at a time.
>> +	 *
>> +	 * Also, format conversion from XR24 to reversed monochrome
>> +	 * are done line-by-line but are converted to 8-bit grayscale
>> +	 * as an intermediate step.
>> +	 *
>> +	 * Allocate a buffer to be used for both copying from the cma
>> +	 * memory and to store the intermediate grayscale line pixels.
>> +	 */
>> +	src32 = kmalloc(len_src32 + linepixels, GFP_KERNEL);
> 
> size_add() ?
> 
>> +	if (!src32)
>> +		return;
> 
> ...
> 
>> +	/*
>> +	 * For damage handling, it is possible that only parts of the source
>> +	 * buffer is copied and this could lead to start and end pixels that
>> +	 * are not aligned to multiple of 8.
>> +	 *
>> +	 * Calculate if the start and end pixels are not aligned and set the
>> +	 * offsets for the reversed mono line conversion function to adjust.
>> +	 */
>> +	start_offset = clip->x1 % 8;
>> +	end_len = clip->x2 % 8;
> 
> ALIGN() ?
> 

-- 
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 --]

  parent reply	other threads:[~2022-02-11 12:03 UTC|newest]

Thread overview: 43+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-11  9:19 [PATCH v4 0/6] drm: Add driver for Solomon SSD130x OLED displays Javier Martinez Canillas
2022-02-11  9:19 ` [PATCH v4 1/6] drm/format-helper: Add drm_fb_xrgb8888_to_gray8_line() Javier Martinez Canillas
2022-02-11  9:29   ` Thomas Zimmermann
2022-02-11 10:28   ` Andy Shevchenko
2022-02-11 10:40     ` Javier Martinez Canillas
2022-02-11 11:12       ` Andy Shevchenko
2022-02-11 11:54         ` Thomas Zimmermann
2022-02-11 12:05           ` Jani Nikula
2022-02-11 12:11             ` Javier Martinez Canillas
2022-02-11 12:27             ` Geert Uytterhoeven
2022-02-11 15:41             ` Andy Shevchenko
2022-02-11 16:25               ` Jani Nikula
2022-02-11 17:27                 ` Andy Shevchenko
2022-02-14  9:17                   ` Pekka Paalanen
2022-02-14 10:26                     ` Andy Shevchenko
2022-02-14  9:03               ` Thomas Zimmermann
2022-02-14 10:38                 ` Andy Shevchenko
2022-02-14 10:52                   ` Simon Ser
2022-02-14 10:57                   ` Geert Uytterhoeven
2022-02-14 12:12                   ` Thomas Zimmermann
2022-02-14 12:47                     ` Ville Syrjälä
2022-02-14 12:54                       ` Thomas Zimmermann
2022-02-14 13:07                         ` Ville Syrjälä
2022-02-14 13:59                     ` Andy Shevchenko
2022-02-11  9:19 ` [PATCH v4 2/6] drm/format-helper: Add drm_fb_xrgb8888_to_mono_reversed() Javier Martinez Canillas
2022-02-11 11:10   ` Andy Shevchenko
2022-02-11 11:50     ` Javier Martinez Canillas
2022-02-11 15:55       ` Andy Shevchenko
2022-02-11 11:59     ` Thomas Zimmermann [this message]
2022-02-11 12:46   ` Thomas Zimmermann
2022-02-11  9:19 ` [PATCH v4 3/6] drm: Add driver for Solomon SSD130x OLED displays Javier Martinez Canillas
2022-02-11 11:33   ` Andy Shevchenko
2022-02-11 12:05     ` Javier Martinez Canillas
2022-02-11 12:23       ` Geert Uytterhoeven
2022-02-11 12:27         ` Javier Martinez Canillas
2022-02-11 15:49       ` Andy Shevchenko
2022-02-11 12:44   ` Thomas Zimmermann
2022-02-11  9:19 ` [PATCH v4 4/6] drm/solomon: Add SSD130x OLED displays I2C support Javier Martinez Canillas
2022-02-11 11:16   ` Andy Shevchenko
2022-02-11  9:21 ` [PATCH v4 5/6] MAINTAINERS: Add entry for Solomon SSD130x OLED displays DRM driver Javier Martinez Canillas
2022-02-11 11:34   ` Andy Shevchenko
2022-02-11  9:22 ` [PATCH v4 6/6] dt-bindings: display: ssd1307fb: Add myself as binding co-maintainer Javier Martinez Canillas
2022-02-11 11:35   ` Andy Shevchenko

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=5cffc63b-c42a-df4c-7270-488735c9e014@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).