From: LiangCheng Wang <zaq14760@gmail.com>
To: Devarsh Thakkar <devarsht@ti.com>,
Maarten Lankhorst <maarten.lankhorst@linux.intel.com>,
Maxime Ripard <mripard@kernel.org>,
Thomas Zimmermann <tzimmermann@suse.de>,
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>,
LiangCheng Wang <zaq14760@gmail.com>
Subject: Re: [PATCH v3 2/2] drm/tiny: add support for PIXPAPER 4.26 monochrome e-ink panel
Date: Wed, 17 Jun 2026 10:09:26 +0800 [thread overview]
Message-ID: <20260617020926.114947-1-zaq14760@gmail.com> (raw)
In-Reply-To: <423c3dca-9589-488d-8462-c3d51f05ee4a@ti.com>
Hi Devarsh,
Thanks, that sounds great -- let's converge on panel-ssd16xx.c.
> Yes, I will be adding SSD1677 controller support in V2 of my series,
> hopefully that should help and after that it's just a matter of adding
> panel entry for your pixpaper panel. I can share you my branch with
> ssd1677 support once I have it ready.
That would be very helpful, please do share the branch once it's ready. I
have the PIXPAPER 4.26 hardware here, so I can validate the SSD1677 support
and the panel on real hardware and report back any quirks.
> additionally I can quickly add boilerplate pixpaper 4.26 panel entries on
> top of my V2 series referring from your patch so that it switches to using
> standard ssd16xx commands and ssd1677 quirks wherever necessary and you can
> then validate and modify.
Thanks for offering. If it's alright with you, I'd like to take the
pixpaper-426m panel entry through review myself on top of your series, using
your boilerplate as a starting point, since I can carry the validation on
real hardware. I'll credit your help with Co-developed-by/Suggested-by as
appropriate. Happy to arrange it whichever way is easiest for you.
I'll also follow up with the 0xF7/0xFF test result so we can capture the
correct SSD1677 update-sequence quirk.
Regards,
LiangCheng
prev parent reply other threads:[~2026-06-17 2:09 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-29 10:31 [PATCH v3 0/2] drm/tiny: add support for PIXPAPER 4.26 monochrome e-ink panel 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-05-29 10:54 ` sashiko-bot
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 [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=20260617020926.114947-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