From: Thomas Zimmermann <tzimmermann@suse.de>
To: LiangCheng Wang <zaq14760@gmail.com>,
Devarsh Thakkar <devarsht@ti.com>,
Maarten Lankhorst <maarten.lankhorst@linux.intel.com>,
Maxime Ripard <mripard@kernel.org>,
David Airlie <airlied@gmail.com>, Simona Vetter <simona@ffwll.ch>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>, Wig Cheng <onlywig@gmail.com>
Cc: dri-devel@lists.freedesktop.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org,
Tomi Valkeinen <tomi.valkeinen@ideasonboard.com>
Subject: Re: [PATCH v3 2/2] drm/tiny: add support for PIXPAPER 4.26 monochrome e-ink panel
Date: Thu, 18 Jun 2026 09:30:35 +0200 [thread overview]
Message-ID: <68a0c8de-9a12-4dc4-84ca-ae988b76087b@suse.de> (raw)
In-Reply-To: <20260618023338.26630-1-zaq14760@gmail.com>
Hi
Am 18.06.26 um 04:33 schrieb LiangCheng Wang:
> Hi Thomas,
>
> Thanks for the review, and no worries about the timing.
>
> Before I spin a v4 for these comments, I'd like to confirm the overall
> direction, since it affects whether this should remain a standalone driver
> at all.
>
> In parallel, Devarsh Thakkar is adding a generic Solomon SSD16xx e-paper
> driver (panel-ssd16xx.c, currently v1 in review). The PIXPAPER 4.26 uses an
> SSD1677, which is part of that family; Devarsh has said he will add SSD1677
> support in the next revision (v2) of his series, after which this panel
> could be supported there as a panel entry rather than as a separate driver.
> That work isn't posted yet, but I had agreed that consolidating under
> panel-ssd16xx.c is the better long-term direction.
>
> I'd appreciate your guidance on how to proceed -- whether it is better to
> keep iterating on this standalone driver, or to hold it and add the
> PIXPAPER 4.26 panel to panel-ssd16xx.c once that driver supports SSD1677.
> I'm happy to go whichever way you prefer.
I see. It is usually preferable to have only a single driver for a
controller. If there are specific features of the Pixpaper 4.26, they
should be added to the ssd16xx driver if possible.
There are exceptions from this rule, of course. If the Pixpaper turns
out to be significantly different, we can always reconsider.
Best regards
Thomas
>
> Regards,
> LiangCheng
--
--
Thomas Zimmermann
Graphics Driver Developer
SUSE Software Solutions Germany GmbH
Frankenstr. 146, 90461 Nürnberg, Germany, www.suse.com
GF: Jochen Jaser, Andrew McDonald, Werner Knoblich, (HRB 36809, AG Nürnberg)
prev parent reply other threads:[~2026-06-18 7:30 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-29 10:31 [PATCH v3 0/2] " LiangCheng Wang
2026-05-29 10:31 ` [PATCH v3 1/2] dt-bindings: display: mayqueen,pixpaper: add pixpaper-426m LiangCheng Wang
2026-05-29 10:31 ` [PATCH v3 2/2] drm/tiny: add support for PIXPAPER 4.26 monochrome e-ink panel LiangCheng Wang
2026-06-10 2:10 ` LiangCheng Wang
2026-06-16 7:08 ` Devarsh Thakkar
2026-06-16 8:39 ` LiangCheng Wang
2026-06-16 15:08 ` Devarsh Thakkar
2026-06-17 2:09 ` LiangCheng Wang
2026-07-13 13:35 ` Devarsh Thakkar
2026-07-31 3:57 ` LiangCheng Wang
2026-09-16 8:29 ` LiangCheng Wang
2026-09-16 9:10 ` Thomas Zimmermann
2026-09-16 9:44 ` LiangCheng Wang
2026-09-16 11:40 ` Thomas Zimmermann
2026-09-17 2:56 ` LiangCheng Wang
2026-09-17 10:49 ` Javier Martinez Canillas
2026-09-17 11:34 ` Thomas Zimmermann
2026-09-17 12:15 ` Javier Martinez Canillas
2026-09-18 4:55 ` Thakkar, Devarsh
2026-09-18 6:25 ` LiangCheng Wang
2026-09-18 17:05 ` Devarsh Thakkar
2026-09-25 17:53 ` Thakkar, Devarsh
2026-06-17 15:31 ` Thomas Zimmermann
2026-06-18 2:33 ` LiangCheng Wang
2026-06-18 7:30 ` Thomas Zimmermann [this message]
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=68a0c8de-9a12-4dc4-84ca-ae988b76087b@suse.de \
--to=tzimmermann@suse.de \
--cc=airlied@gmail.com \
--cc=conor+dt@kernel.org \
--cc=devarsht@ti.com \
--cc=devicetree@vger.kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=krzk+dt@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=mripard@kernel.org \
--cc=onlywig@gmail.com \
--cc=robh@kernel.org \
--cc=simona@ffwll.ch \
--cc=tomi.valkeinen@ideasonboard.com \
--cc=zaq14760@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
all inboxes | Powered by JetHome®