From: Javier Martinez Canillas <javierm@redhat.com>
To: linux-kernel@vger.kernel.org
Cc: "Javier Martinez Canillas" <javierm@redhat.com>,
"Daniel Vetter" <daniel@ffwll.ch>,
"David Airlie" <airlied@gmail.com>,
"Guido Günther" <agx@sigxcpu.org>,
"Maarten Lankhorst" <maarten.lankhorst@linux.intel.com>,
"Maxime Ripard" <mripard@kernel.org>,
"Ondrej Jirman" <megous@megous.com>,
"Purism Kernel Team" <kernel@puri.sm>,
"Sam Ravnborg" <sam@ravnborg.org>,
"Thierry Reding" <thierry.reding@gmail.com>,
"Thomas Zimmermann" <tzimmermann@suse.de>,
dri-devel@lists.freedesktop.org
Subject: [PATCH 00/14] drm/panel: Make panel drivers use existing DSI write macros
Date: Wed, 28 Dec 2022 02:47:43 +0100 [thread overview]
Message-ID: <20221228014757.3170486-1-javierm@redhat.com> (raw)
Hello,
This series contains cleanups for DRM panel drivers that define their own
DSI write macros instead of using what's already in <drm/drm_mipi_dsi.h>.
The changes are quite trivial but I've only tested this with allmodconfig
and `make M=drivers/gpu/drm/panel/` so please review and testing would be
highly appreciated.
Best regards,
Javier
Javier Martinez Canillas (14):
drm/mipi-dsi: Add a mipi_dsi_dcs_write_seq() macro
drm/panel-asus-z00t-tm5p5-n35596: Drop custom DSI write macros
drm/panel-sitronix-st7703: Drop custom DSI write macros
drm/panel-leadtek-ltk050h3146w: Drop custom DSI write macro
drm/panel-elida-kd35t133: Drop custom DSI write macro
drm/panel-boe-bf060y8m-aj0: Drop custom DSI write macro
drm/panel-novatek-nt35950: Drop custom DSI write macro
drm/panel-jdi-fhd-r63452: Drop custom DSI write macros
drm/panel-samsung-s6e88a0-ams452ef01: Drop custom DSI write macro
drm/panel-samsung-sofef00: Drop custom DSI write macro
drm/panel-sharp-ls060t1sx01: Drop custom DSI write macro
drm/panel-mantix-mlaf057we51: Drop custom DSI write macro
drm/panel-sony-tulip-truly-nt35521: Drop custom DSI write macro
drm/panel-xinpeng-xpp055c272: Drop custom DSI write macro
.../drm/panel/panel-asus-z00t-tm5p5-n35596.c | 96 ++---
.../gpu/drm/panel/panel-boe-bf060y8m-aj0.c | 28 +-
drivers/gpu/drm/panel/panel-elida-kd35t133.c | 34 +-
drivers/gpu/drm/panel/panel-jdi-fhd-r63452.c | 50 +--
.../drm/panel/panel-leadtek-ltk050h3146w.c | 64 ++--
.../gpu/drm/panel/panel-mantix-mlaf057we51.c | 24 +-
drivers/gpu/drm/panel/panel-novatek-nt35950.c | 14 +-
.../panel/panel-samsung-s6e88a0-ams452ef01.c | 24 +-
drivers/gpu/drm/panel/panel-samsung-sofef00.c | 24 +-
.../gpu/drm/panel/panel-sharp-ls060t1sx01.c | 19 +-
drivers/gpu/drm/panel/panel-sitronix-st7703.c | 83 ++---
.../panel/panel-sony-tulip-truly-nt35521.c | 348 +++++++++---------
.../gpu/drm/panel/panel-xinpeng-xpp055c272.c | 44 +--
include/drm/drm_mipi_dsi.h | 16 +
14 files changed, 374 insertions(+), 494 deletions(-)
--
2.38.1
next reply other threads:[~2022-12-28 1:48 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-28 1:47 Javier Martinez Canillas [this message]
2022-12-28 1:47 ` [PATCH 01/14] drm/mipi-dsi: Add a mipi_dsi_dcs_write_seq() macro Javier Martinez Canillas
2022-12-29 15:36 ` kernel test robot
2023-01-02 18:39 ` Sam Ravnborg
2023-01-02 18:59 ` Javier Martinez Canillas
2023-01-02 19:02 ` Sam Ravnborg
2022-12-28 1:47 ` [PATCH 02/14] drm/panel-asus-z00t-tm5p5-n35596: Drop custom DSI write macros Javier Martinez Canillas
2022-12-28 1:47 ` [PATCH 03/14] drm/panel-sitronix-st7703: " Javier Martinez Canillas
2022-12-28 12:01 ` Guido Günther
2022-12-29 14:30 ` Javier Martinez Canillas
2023-01-02 18:42 ` Sam Ravnborg
2022-12-28 1:47 ` [PATCH 04/14] drm/panel-leadtek-ltk050h3146w: Drop custom DSI write macro Javier Martinez Canillas
2023-01-02 18:43 ` Sam Ravnborg
2022-12-28 1:47 ` [PATCH 05/14] drm/panel-elida-kd35t133: " Javier Martinez Canillas
2023-01-02 18:44 ` Sam Ravnborg
2022-12-28 1:47 ` [PATCH 06/14] drm/panel-boe-bf060y8m-aj0: " Javier Martinez Canillas
2023-01-02 18:45 ` Sam Ravnborg
2022-12-28 1:47 ` [PATCH 07/14] drm/panel-novatek-nt35950: " Javier Martinez Canillas
2023-01-02 18:55 ` Sam Ravnborg
2022-12-28 1:47 ` [PATCH 08/14] drm/panel-jdi-fhd-r63452: Drop custom DSI write macros Javier Martinez Canillas
2023-01-02 18:46 ` Sam Ravnborg
2022-12-28 1:47 ` [PATCH 09/14] drm/panel-samsung-s6e88a0-ams452ef01: Drop custom DSI write macro Javier Martinez Canillas
2023-01-02 18:48 ` Sam Ravnborg
2022-12-28 1:47 ` [PATCH 10/14] drm/panel-samsung-sofef00: " Javier Martinez Canillas
2023-01-02 18:56 ` Sam Ravnborg
2022-12-28 1:47 ` [PATCH 11/14] drm/panel-sharp-ls060t1sx01: " Javier Martinez Canillas
2023-01-02 18:50 ` Sam Ravnborg
2022-12-28 1:47 ` [PATCH 12/14] drm/panel-mantix-mlaf057we51: " Javier Martinez Canillas
2023-01-02 18:56 ` Sam Ravnborg
2022-12-28 1:47 ` [PATCH 13/14] drm/panel-sony-tulip-truly-nt35521: " Javier Martinez Canillas
2023-01-02 18:51 ` Sam Ravnborg
2022-12-28 1:47 ` [PATCH 14/14] drm/panel-xinpeng-xpp055c272: " Javier Martinez Canillas
2023-01-02 18:53 ` Sam Ravnborg
2023-01-02 19:08 ` Javier Martinez Canillas
2023-01-02 19:00 ` [PATCH 00/14] drm/panel: Make panel drivers use existing DSI write macros Sam Ravnborg
2023-01-02 19:13 ` Javier Martinez Canillas
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=20221228014757.3170486-1-javierm@redhat.com \
--to=javierm@redhat.com \
--cc=agx@sigxcpu.org \
--cc=airlied@gmail.com \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=kernel@puri.sm \
--cc=linux-kernel@vger.kernel.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=megous@megous.com \
--cc=mripard@kernel.org \
--cc=sam@ravnborg.org \
--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;
as well as URLs for NNTP newsgroup(s).