From: Conor Dooley <conor@kernel.org>
To: LiangCheng Wang <zaq14760@gmail.com>
Cc: 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>,
dri-devel@lists.freedesktop.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] dt-bindings: display: mayqueen,pixpaper: add pixpaper-426m
Date: Wed, 6 May 2026 17:58:02 +0100 [thread overview]
Message-ID: <20260506-clique-safely-6dd507d0593f@spud> (raw)
In-Reply-To: <20260506-bar-v1-1-12195406f4ef@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2894 bytes --]
On Wed, May 06, 2026 at 02:25:37PM +0800, LiangCheng Wang wrote:
> Add the compatible string for the PIXPAPER 4.26 monochrome
> e-ink panel to the Mayqueen Pixpaper binding.
>
> The new panel uses the same SPI and GPIO control interface as
> the existing Pixpaper panel, so extend the existing binding
> instead of adding a separate schema. Document the new compatible
> string and add an example node for pixpaper-426m.
>
> Signed-off-by: LiangCheng Wang <zaq14760@gmail.com>
> ---
> .../bindings/display/mayqueen,pixpaper.yaml | 25 +++++++++++++++++-----
> 1 file changed, 20 insertions(+), 5 deletions(-)
>
> diff --git a/Documentation/devicetree/bindings/display/mayqueen,pixpaper.yaml b/Documentation/devicetree/bindings/display/mayqueen,pixpaper.yaml
> index cd27f8ba5ae1d94660818525b5fa71db98c8acb7..4b0db2b079ebea244eb149a52ee1d8dbab0f60bb 100644
> --- a/Documentation/devicetree/bindings/display/mayqueen,pixpaper.yaml
> +++ b/Documentation/devicetree/bindings/display/mayqueen,pixpaper.yaml
> @@ -4,22 +4,23 @@
> $id: http://devicetree.org/schemas/display/mayqueen,pixpaper.yaml#
> $schema: http://devicetree.org/meta-schemas/core.yaml#
>
> -title: Mayqueen Pixpaper e-ink display panel
> +title: Mayqueen Pixpaper e-ink display panels
>
> maintainers:
> - LiangCheng Wang <zaq14760@gmail.com>
>
> description:
> - The Pixpaper is an e-ink display panel controlled via an SPI interface.
> - The panel has a resolution of 122x250 pixels and requires GPIO pins for
> - reset, busy, and data/command control.
> + Mayqueen Pixpaper e-ink display panels are controlled via an SPI interface
> + and require GPIO pins for reset, busy, and data/command control.
>
> allOf:
> - $ref: /schemas/spi/spi-peripheral-props.yaml#
>
> properties:
> compatible:
> - const: mayqueen,pixpaper
> + enum:
> + - mayqueen,pixpaper
> + - mayqueen,pixpaper-426m
The commit message makes it sound like both devices could be compatible,
but the diff says they are not. What actually makes them incompatible?
>
> reg:
> maxItems: 1
> @@ -61,3 +62,17 @@ examples:
> dc-gpios = <&gpio1 19 GPIO_ACTIVE_HIGH>;
> };
> };
> + - |
> + #include <dt-bindings/gpio/gpio.h>
> + spi {
> + #address-cells = <1>;
> + #size-cells = <0>;
> + display@0 {
> + compatible = "mayqueen,pixpaper-426m";
> + reg = <0>;
> + spi-max-frequency = <1000000>;
> + reset-gpios = <&gpio1 17 GPIO_ACTIVE_HIGH>;
> + busy-gpios = <&gpio1 18 GPIO_ACTIVE_HIGH>;
> + dc-gpios = <&gpio1 19 GPIO_ACTIVE_HIGH>;
> + };
> + };
This example just duplicates the existing one, there's no value in
adding it.
pw-bot: changes-requested
Cheers,
Conor.
>
> --
> 2.34.1
>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2026-05-06 16:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-06 6:25 [PATCH 0/2] Add support for PIXPAPER 4.26 monochrome e-ink panel LiangCheng Wang
2026-05-06 6:25 ` [PATCH 1/2] dt-bindings: display: mayqueen,pixpaper: add pixpaper-426m LiangCheng Wang
2026-05-06 16:58 ` Conor Dooley [this message]
2026-05-07 2:32 ` LiangCheng Wang
2026-05-06 6:25 ` [PATCH 2/2] drm/tiny: add support for PIXPAPER 4.26 monochrome e-ink panel LiangCheng Wang
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=20260506-clique-safely-6dd507d0593f@spud \
--to=conor@kernel.org \
--cc=airlied@gmail.com \
--cc=conor+dt@kernel.org \
--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=tzimmermann@suse.de \
--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