From: Albert Esteve <aesteve@redhat.com>
To: Neil Armstrong <neil.armstrong@linaro.org>,
Jessica Zhang <jesszhan0024@gmail.com>,
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>,
Michael Tretter <m.tretter@pengutronix.de>,
Michael Walle <mwalle@kernel.org>,
Dario Binacchi <dario.binacchi@amarulasolutions.com>
Cc: dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org,
Albert Esteve <aesteve@redhat.com>
Subject: [PATCH v2 10/10] drm/panel: Make drm_panel_init() static
Date: Fri, 08 May 2026 09:04:50 +0200 [thread overview]
Message-ID: <20260508-drm_panel_init_rm-v2-10-0bd4ac429971@redhat.com> (raw)
In-Reply-To: <20260508-drm_panel_init_rm-v2-0-0bd4ac429971@redhat.com>
Now that all panel drivers use devm_drm_panel_alloc(),
there are no external callers of drm_panel_init().
Make it static to prevent new users from bypassing the
refcounted allocation path.
Remove stale references to drm_panel_init() in kdocs.
Reviewed-by: Maxime Ripard <mripard@kernel.org>
Signed-off-by: Albert Esteve <aesteve@redhat.com>
---
drivers/gpu/drm/display/drm_dp_helper.c | 2 --
drivers/gpu/drm/drm_panel.c | 7 +++----
include/drm/drm_panel.h | 4 ----
3 files changed, 3 insertions(+), 10 deletions(-)
diff --git a/drivers/gpu/drm/display/drm_dp_helper.c b/drivers/gpu/drm/display/drm_dp_helper.c
index a697cc227e289..6d5556e3c134c 100644
--- a/drivers/gpu/drm/display/drm_dp_helper.c
+++ b/drivers/gpu/drm/display/drm_dp_helper.c
@@ -4626,8 +4626,6 @@ static const struct backlight_ops dp_aux_bl_ops = {
* Backlight will then be handled transparently without requiring
* any intervention from the driver.
*
- * drm_panel_dp_aux_backlight() must be called after the call to drm_panel_init().
- *
* Return: 0 on success or a negative error code on failure.
*/
int drm_panel_dp_aux_backlight(struct drm_panel *panel, struct drm_dp_aux *aux)
diff --git a/drivers/gpu/drm/drm_panel.c b/drivers/gpu/drm/drm_panel.c
index d1e6598ea3bc0..9c3cbc7aea2c3 100644
--- a/drivers/gpu/drm/drm_panel.c
+++ b/drivers/gpu/drm/drm_panel.c
@@ -56,8 +56,9 @@ static LIST_HEAD(panel_list);
* Initialize the panel structure for subsequent registration with
* drm_panel_add().
*/
-void drm_panel_init(struct drm_panel *panel, struct device *dev,
- const struct drm_panel_funcs *funcs, int connector_type)
+static void drm_panel_init(struct drm_panel *panel, struct device *dev,
+ const struct drm_panel_funcs *funcs,
+ int connector_type)
{
if (connector_type == DRM_MODE_CONNECTOR_Unknown)
DRM_WARN("%s: %s: a valid connector type is required!\n", __func__, dev_name(dev));
@@ -69,7 +70,6 @@ void drm_panel_init(struct drm_panel *panel, struct device *dev,
panel->funcs = funcs;
panel->connector_type = connector_type;
}
-EXPORT_SYMBOL(drm_panel_init);
/**
* drm_panel_add - add a panel to the global registry
@@ -708,7 +708,6 @@ EXPORT_SYMBOL(devm_drm_panel_add_follower);
* A typical implementation for a panel driver supporting device tree
* will call this function at probe time. Backlight will then be handled
* transparently without requiring any intervention from the driver.
- * drm_panel_of_backlight() must be called after the call to drm_panel_init().
*
* Return: 0 on success or a negative error code on failure.
*/
diff --git a/include/drm/drm_panel.h b/include/drm/drm_panel.h
index 2407bfa60236f..55cbc51512240 100644
--- a/include/drm/drm_panel.h
+++ b/include/drm/drm_panel.h
@@ -320,10 +320,6 @@ void *__devm_drm_panel_alloc(struct device *dev, size_t size, size_t offset,
offsetof(type, member), funcs, \
connector_type))
-void drm_panel_init(struct drm_panel *panel, struct device *dev,
- const struct drm_panel_funcs *funcs,
- int connector_type);
-
struct drm_panel *drm_panel_get(struct drm_panel *panel);
void drm_panel_put(struct drm_panel *panel);
--
2.53.0
next prev parent reply other threads:[~2026-05-08 7:05 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-08 7:04 [PATCH v2 00/10] drm/panel: Use refcounted allocation for remaining panel drivers Albert Esteve
2026-05-08 7:04 ` [PATCH v2 01/10] drm/panel/visionox-g2647fb105: Use refcounted allocation in place of devm_kzalloc() Albert Esteve
2026-05-08 7:04 ` [PATCH v2 02/10] drm/panel/samsung-s6e63m0: " Albert Esteve
2026-05-08 7:04 ` [PATCH v2 03/10] drm/panel/novatek-nt37700f: " Albert Esteve
2026-05-08 7:04 ` [PATCH v2 04/10] drm/panel/lxd-m9189a: " Albert Esteve
2026-05-08 7:04 ` [PATCH v2 05/10] drm/panel/ilitek-ili9806e: " Albert Esteve
2026-05-08 7:04 ` [PATCH v2 06/10] drm/panel/tdo-tl070wsh30: " Albert Esteve
2026-05-08 7:04 ` [PATCH v2 07/10] drm/panel/sharp-ls043t1le01: " Albert Esteve
2026-05-08 7:04 ` [PATCH v2 08/10] drm/panel/truly-nt35597: " Albert Esteve
2026-05-08 7:04 ` [PATCH v2 09/10] drm/panel/startek-kd070fhfid015: " Albert Esteve
2026-05-08 7:04 ` Albert Esteve [this message]
2026-05-08 7:29 ` [PATCH v2 00/10] drm/panel: Use refcounted allocation for remaining panel drivers Thomas Zimmermann
2026-05-08 11:28 ` Dmitry Baryshkov
2026-05-11 7:16 ` Maxime Ripard
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=20260508-drm_panel_init_rm-v2-10-0bd4ac429971@redhat.com \
--to=aesteve@redhat.com \
--cc=airlied@gmail.com \
--cc=dario.binacchi@amarulasolutions.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=jesszhan0024@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=m.tretter@pengutronix.de \
--cc=maarten.lankhorst@linux.intel.com \
--cc=mripard@kernel.org \
--cc=mwalle@kernel.org \
--cc=neil.armstrong@linaro.org \
--cc=simona@ffwll.ch \
--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