mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
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>,
	Neil Armstrong <neil.armstrong@linaro.org>,
	Sam Ravnborg <sam@ravnborg.org>,
	Javier Martinez Canillas <javierm@redhat.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: Wed, 16 Sep 2026 13:40:20 +0200	[thread overview]
Message-ID: <f4c6feab-b1ec-48df-81a5-888444b243a3@suse.de> (raw)
In-Reply-To: <20260916094453.1062125-1-zaq14760@gmail.com>

(cc'ing Javier for ssd130x expertise)

Hi

Am 16.09.26 um 11:44 schrieb LiangCheng Wang:
> Hi Thomas,
>
> Thank you for the quick reply.
>
>> Where exactly are these ssd16xx patches. I cannot find them in the DRM
>> trees. I presume they are not upstream yet?
> That is right, they are not upstream. Devarsh posted them on 1 May and
> the series is still at v1 on the list:
>
>    [PATCH 0/6] Add DRM driver for Solomon SSD16xx e-paper display controllers
>    https://lore.kernel.org/all/20260430183311.2978142-1-devarsht@ti.com/
>
> One thing that is easy to miss, and that I should have made clearer in my
> last mail: that v1 series covers the SSD1683 only. The SSD1677, which is
> the controller on the PIXPAPER 4.26m, is not part of it. Devarsh has
> SSD1677 support in a staged branch that he kindly shared with me in July,
> and that is what I tested on the panel:
>
>    https://github.com/devarsht/linux-next/commits/ssd16xx_7_2/
>
> Those SSD1677 patches have not been posted to the list yet, which is why
> the panel support has not had anything to build on so far.
>
>> If there's support for similar ICs, I'd strongly prefer to have the
>> ssd1677 be part of that instead of a stand-alone driver.
>>
>> Once the stand-alone driver is in place, users will rely on it. Then it
>> becomes hard to replace. We had (have?) cases where there are several
>> drivers for the same hardware.
> Understood, and thank you for explaining the reasoning - the point about
> users coming to depend on a driver that is then hard to replace makes
> sense, and I would rather not create that problem. I will drop the
> standalone driver and add the PIXPAPER 4.26m to ssd16xx instead, once the
> shared driver is in.

Oh, I now took a closer look at the ssd16xx driver.  I thought that it 
would use the panel helpers, but that's not the case. It's a 'regular' 
DRM driver.

If the ssd16xx does not make progress, we could also try to merge your 
code as ssd16xx and Devarsh would then add support for additional ICs on 
top.

There's also the ssd130x driver under solomon/ how does it related to 
the ssd16xx? Is that similar as well?

Best regards
Thomas

>
> Devarsh, thank you again for sharing the branch, and for making room for
> the panel in your work in the first place. I am glad to keep testing
> SSD1677 on real hardware whenever that is useful to you.
>
> 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, (HRB 36809, AG Nürnberg)



  reply	other threads:[~2026-09-16 11:40 UTC|newest]

Thread overview: 23+ 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 [this message]
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-06-17 15:31   ` Thomas Zimmermann
2026-06-18  2:33     ` LiangCheng Wang
2026-06-18  7:30       ` Thomas Zimmermann

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=f4c6feab-b1ec-48df-81a5-888444b243a3@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=javierm@redhat.com \
    --cc=krzk+dt@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=maarten.lankhorst@linux.intel.com \
    --cc=mripard@kernel.org \
    --cc=neil.armstrong@linaro.org \
    --cc=onlywig@gmail.com \
    --cc=robh@kernel.org \
    --cc=sam@ravnborg.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®