mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: LiangCheng Wang <zaq14760@gmail.com>
To: Devarsh Thakkar <devarsht@ti.com>,
	Thomas Zimmermann <tzimmermann@suse.de>,
	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: LiangCheng Wang <zaq14760@gmail.com>,
	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 16:29:24 +0800	[thread overview]
Message-ID: <20260916082924.956116-1-zaq14760@gmail.com> (raw)
In-Reply-To: <20260731035705.3198816-1-zaq14760@gmail.com>

Hi Devarsh, Thomas,

Sorry to come back to this thread after a quiet spell, and apologies in
advance if I have missed something obvious.

Devarsh, the three fixes from my July testing on the PIXPAPER 4.26m are
still available:

  https://lore.kernel.org/all/20260731-ssd16xx-pixpaper-rpi5-v1-0-18ffc0dbf59a@gmail.com/

I am happy to rebase them, reshape them into whatever form fits your
series best, or retest on a newer kernel - whatever is most convenient
for you. There is no hurry at all from my side; please just let me know
if anything would be useful, and thank you again for making room for the
panel in your work.

Thomas, may I ask your advice on how best to handle the panel support in
the meantime? The PIXPAPER 4.26m is the only SSD16xx hardware I have, so
everything I can contribute is limited to this one panel, and its support
has been on hold since June waiting for the shared driver.

I wondered whether it might be acceptable to merge the standalone
PIXPAPER driver as an interim step, on the understanding that I convert
the panel over to ssd16xx and remove the standalone driver once the
shared driver lands. I realise that is not ideal, and I may well be
missing a better option - if you would prefer to wait for the shared
driver, I am perfectly happy to do that instead. I would rather follow
your judgement than guess.

Thank you both for the review time so far.

Regards,
LiangCheng

  reply	other threads:[~2026-09-16  8:29 UTC|newest]

Thread overview: 24+ 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 [this message]
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-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=20260916082924.956116-1-zaq14760@gmail.com \
    --to=zaq14760@gmail.com \
    --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=tzimmermann@suse.de \
    /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®