From: David Lechner <david@lechnology.com>
To: Christian Eggers <ceggers@arri.de>,
Maarten Lankhorst <maarten.lankhorst@linux.intel.com>,
Maxime Ripard <mripard@kernel.org>,
Thomas Zimmermann <tzimmermann@suse.de>,
David Airlie <airlied@gmail.com>, Daniel Vetter <daniel@ffwll.ch>
Cc: "Noralf Trønnes" <noralf@tronnes.org>,
linux-kernel@vger.kernel.org, dri-devel@lists.freedesktop.org
Subject: Re: [RFC PATCH] drm/tiny: Add support for Sitronix ST7539
Date: Wed, 3 Jul 2024 11:07:35 -0500 [thread overview]
Message-ID: <3f4e9dfa-6373-4b34-8097-48c870e69daa@lechnology.com> (raw)
In-Reply-To: <20240703140504.8518-1-ceggers@arri.de>
On 7/3/24 9:05 AM, Christian Eggers wrote:
> Based on the existing ST7586 driver. But the ST7539 ...
> - is monochrome only
> - has 8 VERTICAL pixels per byte
> - doesn't support any MIPI DCS commands
> - has (a few) 16 bit commands
> - doesn't support setting a clipping rect when writing to the RAM
> - doesn't support rotation (only mirroring of X and/or Y axis)
>
> Questions/TODO:
To start with, I would suggest reading [1]. This patch is really hard to
read because it isn't properly formatted. If you don't change the patch,
you can resend it as [RFC PATCH RESEND] using `git send-email`, or if you
do change the patch before re-sending, e.g. because you fixed checkpatch
style issues, just call it v2.
[1]: https://www.kernel.org/doc/html/latest/process/submitting-patches.html
> - should drivers for such old displays be mainlined?
If it is actually going to be used and you are willing to maintain it,
then yes.
> - shall I use mipi_dbi_ although the display doesn't implement MIPI DCS
> (and has some 16 bit commands)?
> - can the conversion to 8 vertical pixels/byte (taken from
> solomon/ssd130x.c) be avoided / simplified / made more efficient?
> - how to implement setting of the display contrast (required by my
> application)?
I see that ssd130x_update_bl() is using brightness to control
contrast. Don't know if it that is the best way though.
> - add device tree binding
>
> Signed-off-by: Christian Eggers <ceggers@arri.de>
> ---
prev parent reply other threads:[~2024-07-03 16:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-03 14:05 Christian Eggers
2024-07-03 16:07 ` David Lechner [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=3f4e9dfa-6373-4b34-8097-48c870e69daa@lechnology.com \
--to=david@lechnology.com \
--cc=airlied@gmail.com \
--cc=ceggers@arri.de \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=mripard@kernel.org \
--cc=noralf@tronnes.org \
--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®