From: Richard Acayan <mailingradian@gmail.com>
To: 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>,
Thierry Reding <thierry.reding@gmail.com>,
Sam Ravnborg <sam@ravnborg.org>,
Emil Velikov <emil.l.velikov@gmail.com>,
Vinay Simha BN <simhavcs@gmail.com>,
dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org
Cc: Daniel Mentz <danielmentz@google.com>,
Caleb Connolly <caleb@connolly.tech>,
Richard Acayan <mailingradian@gmail.com>
Subject: [RFC PATCH v2 0/2] drm/dsi-mipi: 16-bit Brightness Endianness Fix
Date: Fri, 13 Jan 2023 20:00:04 -0500 [thread overview]
Message-ID: <20230114010006.50471-1-mailingradian@gmail.com> (raw)
Changes since v1:
- move 16-bit brightness handling to new functions and revert API
change (1/2)
- remove Change-Id in compliance with checkpatch.pl (1/2)
- separate panel driver changes (2/2)
This series adds proper support for 16-bit MIPI DSI brightness and
cleans up existing panel drivers.
I cannot test the SOFEF00 change, although I tested an equivalent change
to an external S6E3FA7 driver generated with the same generator. Both
setting and getting works on S6E3FA7.
Daniel Mentz (1):
drm/dsi-mipi: Fix byte order of DCS set/get brightness
Richard Acayan (1):
drm/panel: sofef00: Use 16-bit panel brightness
drivers/gpu/drm/drm_mipi_dsi.c | 52 +++++++++++++++++++
drivers/gpu/drm/panel/panel-samsung-sofef00.c | 9 +---
include/drm/drm_mipi_dsi.h | 4 ++
3 files changed, 58 insertions(+), 7 deletions(-)
--
2.39.0
next reply other threads:[~2023-01-14 1:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-14 1:00 Richard Acayan [this message]
2023-01-14 1:00 ` [RFC PATCH v2 1/2] drm/dsi-mipi: Fix byte order of DCS set/get brightness Richard Acayan
2023-01-14 1:36 ` Richard Acayan
2023-01-14 1:00 ` [RFC PATCH v2 2/2] drm/panel: sofef00: Use 16-bit panel brightness Richard Acayan
2023-01-14 1:30 ` Caleb Connolly
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=20230114010006.50471-1-mailingradian@gmail.com \
--to=mailingradian@gmail.com \
--cc=airlied@gmail.com \
--cc=caleb@connolly.tech \
--cc=daniel@ffwll.ch \
--cc=danielmentz@google.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=emil.l.velikov@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=mripard@kernel.org \
--cc=sam@ravnborg.org \
--cc=simhavcs@gmail.com \
--cc=thierry.reding@gmail.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®