From: Thomas Zimmermann <tzimmermann@suse.de>
To: Javier Martinez Canillas <javierm@redhat.com>,
linux-kernel@vger.kernel.org
Cc: Geert Uytterhoeven <geert@linux-m68k.org>,
Maxime Ripard <mripard@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Daniel Vetter <daniel@ffwll.ch>, David Airlie <airlied@gmail.com>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Rob Herring <robh+dt@kernel.org>,
devicetree@vger.kernel.org, dri-devel@lists.freedesktop.org
Subject: Re: [PATCH 0/5] drm/ssd130x: A few enhancements and cleanups
Date: Tue, 6 Jun 2023 10:01:36 +0200 [thread overview]
Message-ID: <6b0a12bf-a8d4-43df-860c-3aa271cfc624@suse.de> (raw)
In-Reply-To: <20230605074753.562332-1-javierm@redhat.com>
[-- Attachment #1.1: Type: text/plain, Size: 1760 bytes --]
Hi Javierm,
I've read through the patches and they look correct to me.
Reviewed-by: Thomas Zimmermann <tzimmermann@suse.de>
But I had one question about the page size. You round up to multiples of
page_size in several places. That could lead to an out-of-bounds access.
Do you need to allocate GEM buffers to be multiples of page_size as well?
Best regards
Thomas
Am 05.06.23 um 09:47 schrieb Javier Martinez Canillas:
> Hello,
>
> While working on adding support for the SSD132X family of 4-bit grayscale
> Solomon OLED panel controllers, I noticed a few things in the driver that
> can be improved and make extending to support other chip families easier.
>
> I've split the preparatory patches in this series and will post the actual
> SSD132X support as a separate patch-set once this one is merged.
>
> Best regards,
> Javier
>
>
> Javier Martinez Canillas (5):
> drm/ssd130x: Make default width and height to be controller dependent
> dt-bindings: display: ssd1307fb: Remove default width and height
> values
> drm/ssd130x: Set the page height value in the device info data
> drm/ssd130x: Don't allocate buffers on each plane update
> drm/ssd130x: Remove hardcoded bits-per-pixel in ssd130x_buf_alloc()
>
> .../bindings/display/solomon,ssd1307fb.yaml | 8 +-
> drivers/gpu/drm/solomon/ssd130x.c | 124 ++++++++++++------
> drivers/gpu/drm/solomon/ssd130x.h | 6 +
> 3 files changed, 93 insertions(+), 45 deletions(-)
>
--
Thomas Zimmermann
Graphics Driver Developer
SUSE Software Solutions Germany GmbH
Frankenstrasse 146, 90461 Nuernberg, Germany
GF: Ivo Totev, Andrew Myers, Andrew McDonald, Boudien Moerman
HRB 36809 (AG Nuernberg)
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 840 bytes --]
next prev parent reply other threads:[~2023-06-06 8:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-05 7:47 [PATCH 0/5] drm/ssd130x: A few enhancements and cleanups Javier Martinez Canillas
2023-06-05 7:47 ` [PATCH 2/5] dt-bindings: display: ssd1307fb: Remove default width and height values Javier Martinez Canillas
2023-06-05 9:25 ` Maxime Ripard
2023-06-05 10:15 ` Javier Martinez Canillas
2023-06-06 8:01 ` Thomas Zimmermann [this message]
2023-06-07 7:17 ` [PATCH 0/5] drm/ssd130x: A few enhancements and cleanups Javier Martinez Canillas
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=6b0a12bf-a8d4-43df-860c-3aa271cfc624@suse.de \
--to=tzimmermann@suse.de \
--cc=airlied@gmail.com \
--cc=conor+dt@kernel.org \
--cc=daniel@ffwll.ch \
--cc=devicetree@vger.kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=geert@linux-m68k.org \
--cc=javierm@redhat.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mripard@kernel.org \
--cc=robh+dt@kernel.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).