Devicetree
 help / color / mirror / Atom feed
From: Javier Martinez Canillas <javierm@redhat.com>
To: Marcus Folkesson <marcus.folkesson@gmail.com>
Cc: David Airlie <airlied@gmail.com>, Simona Vetter <simona@ffwll.ch>,
	Maarten Lankhorst <maarten.lankhorst@linux.intel.com>,
	Maxime Ripard <mripard@kernel.org>,
	Thomas Zimmermann <tzimmermann@suse.de>,
	Rob Herring <robh@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>,
	dri-devel@lists.freedesktop.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org,
	Thomas Zimmermann <tzimmrmann@suse.de>
Subject: Re: [PATCH v3 2/3] drm/st7571-i2c: add support for Sitronix ST7571 LCD controller
Date: Fri, 11 Apr 2025 10:26:47 +0200	[thread overview]
Message-ID: <875xjb2jeg.fsf@minerva.mail-host-address-is-not-set> (raw)
In-Reply-To: <Z_iwspuiYAhARS6Y@gmail.com>

Marcus Folkesson <marcus.folkesson@gmail.com> writes:

Hello Marcus,

[...]

>> static const struct of_device_id st7571_of_match[] = {
>> 	/* monochrome displays */
>> 	{
>> 		.compatible = "sinocrystal,sc128128012-v01",
>> 		.data = monochrome_formats,
>> 	},
>> ...
>>         /* grayscale displays */
>> 	{
>> 		.compatible = "foo,bar",
>> 		.data = grayscale_formats,
>> 	},
>> };
>
> A comment for v4:
>
> I think I will go for a property in the device tree. I've implemented
> board entries as above, but I'm not satisfied for two reasons:
>
> 1. All other properties like display size and resolution are already
>    specified in the device tree. If I add entries for specific boards,
>    these properties will be somehow redundant and not as generic.
>
> 2. I could not find a ST7571 with a grayscale display as a off-the-shelf
>    product.

Sure, that makes sense to me.

Can I ask if you could still add reasonable default values that could be set
in the device ID .data fields ?

As mentioned, I've a ST7567 based LCD and a WIP driver for it. But I could
just drop that and use your driver, since AFAICT the expected display data
RAM format is exactly the same than when using monochrome for the ST7571.

But due the ST7567 only supporting R1, it would be silly to always have to
define a property in the DT node given that does not support other format.

-- 
Best regards,

Javier Martinez Canillas
Core Platforms
Red Hat


  reply	other threads:[~2025-04-11  8:26 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-08  7:04 [PATCH v3 0/3] Add support for Sitronix ST7571 LCD controller Marcus Folkesson
2025-04-08  7:04 ` [PATCH v3 1/3] dt-bindings: display: Add Sitronix ST7571 LCD Controller Marcus Folkesson
2025-04-08 16:16   ` Conor Dooley
2025-04-08  7:04 ` [PATCH v3 2/3] drm/st7571-i2c: add support for Sitronix ST7571 LCD controller Marcus Folkesson
2025-04-08 10:44   ` Javier Martinez Canillas
2025-04-08 11:01     ` Thomas Zimmermann
2025-04-08 11:34       ` Javier Martinez Canillas
2025-04-08 13:20     ` Marcus Folkesson
2025-04-08 13:57       ` Thomas Zimmermann
2025-04-08 14:58         ` Marcus Folkesson
2025-04-09  7:22           ` Thomas Zimmermann
2025-04-09  6:11       ` Javier Martinez Canillas
2025-04-09  6:41         ` Marcus Folkesson
2025-04-09  9:43           ` Javier Martinez Canillas
2025-04-09 13:25             ` Marcus Folkesson
2025-04-09 14:15               ` Javier Martinez Canillas
2025-04-11  6:47                 ` Geert Uytterhoeven
2025-04-11  6:03             ` Marcus Folkesson
2025-04-11  8:26               ` Javier Martinez Canillas [this message]
2025-04-12  6:56                 ` Marcus Folkesson
2025-04-14  7:55                   ` Javier Martinez Canillas
2025-04-24  6:36     ` Marcus Folkesson
2025-04-24  6:45       ` Javier Martinez Canillas
2025-04-08  7:04 ` [PATCH v3 3/3] MAINTAINERS: add entry for Sitronix ST7571 LCD Controller Marcus Folkesson

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=875xjb2jeg.fsf@minerva.mail-host-address-is-not-set \
    --to=javierm@redhat.com \
    --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=marcus.folkesson@gmail.com \
    --cc=mripard@kernel.org \
    --cc=robh@kernel.org \
    --cc=simona@ffwll.ch \
    --cc=tzimmermann@suse.de \
    --cc=tzimmrmann@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