From: Albert Esteve <aesteve@redhat.com>
To: Maxime Ripard <mripard@kernel.org>
Cc: Neil Armstrong <neil.armstrong@linaro.org>,
Jessica Zhang <jesszhan0024@gmail.com>,
Maarten Lankhorst <maarten.lankhorst@linux.intel.com>,
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>,
dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 10/10] drm/panel: Make drm_panel_init() static
Date: Thu, 7 May 2026 17:11:15 +0200 [thread overview]
Message-ID: <CADSE00+UN3wgsJnfCn3CLB3h-RnR-FLLfAOY3UhDyCOmt5HTKA@mail.gmail.com> (raw)
In-Reply-To: <20260507-premium-curious-macaw-d43cbe@houat>
On Thu, May 7, 2026 at 4:57 PM Maxime Ripard <mripard@kernel.org> wrote:
>
> Hi,
>
> On Thu, May 07, 2026 at 01:53:08PM +0200, Albert Esteve wrote:
> > 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.
> >
> > Signed-off-by: Albert Esteve <aesteve@redhat.com>
> > ---
> > drivers/gpu/drm/display/drm_dp_helper.c | 2 +-
> > drivers/gpu/drm/drm_panel.c | 8 ++++----
> > include/drm/drm_panel.h | 4 ----
> > 3 files changed, 5 insertions(+), 9 deletions(-)
> >
> > diff --git a/drivers/gpu/drm/display/drm_dp_helper.c b/drivers/gpu/drm/display/drm_dp_helper.c
> > index a697cc227e289..380ebf0fad2be 100644
> > --- a/drivers/gpu/drm/display/drm_dp_helper.c
> > +++ b/drivers/gpu/drm/display/drm_dp_helper.c
> > @@ -4626,7 +4626,7 @@ 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().
> > + * drm_panel_dp_aux_backlight() must be called after devm_drm_panel_alloc().
> > *
> > * Return: 0 on success or a negative error code on failure.
> > */
> > diff --git a/drivers/gpu/drm/drm_panel.c b/drivers/gpu/drm/drm_panel.c
> > index d1e6598ea3bc0..e3e1c5ceb8ff8 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,7 @@ 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().
> > + * drm_panel_of_backlight() must be called after devm_drm_panel_alloc().
>
> I think we can drop that sentence entirely. Now that we can only get a
> panel structure through devm_drm_panel_alloc, and that it also
> initializes it, we can't call drm_panel_of_backlight before having an
> initialized drm_panel.
Makes sense, I will remove the sentence and send a v2. It probably
follows the same reasoning, but just to ensure you did not miss it:
does that apply to drm_panel_dp_aux_backlight() above too?
>
> Maxime
next prev parent reply other threads:[~2026-05-07 15:11 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-07 11:52 [PATCH 00/10] drm/panel: Use refcounted allocation for remaining panel drivers Albert Esteve
2026-05-07 11:52 ` [PATCH 01/10] drm/panel/visionox-g2647fb105: Use refcounted allocation in place of devm_kzalloc() Albert Esteve
2026-05-07 15:34 ` Neil Armstrong
2026-05-07 11:53 ` [PATCH 02/10] drm/panel/samsung-s6e63m0: " Albert Esteve
2026-05-07 15:35 ` Neil Armstrong
2026-05-07 11:53 ` [PATCH 03/10] drm/panel/novatek-nt37700f: " Albert Esteve
2026-05-07 15:35 ` Neil Armstrong
2026-05-07 15:35 ` Neil Armstrong
2026-05-07 11:53 ` [PATCH 04/10] drm/panel/lxd-m9189a: " Albert Esteve
2026-05-07 15:35 ` Neil Armstrong
2026-05-07 11:53 ` [PATCH 05/10] drm/panel/ilitek-ili9806e: " Albert Esteve
2026-05-07 15:35 ` Neil Armstrong
2026-05-07 11:53 ` [PATCH 06/10] drm/panel/tdo-tl070wsh30: " Albert Esteve
2026-05-07 15:36 ` Neil Armstrong
2026-05-07 11:53 ` [PATCH 07/10] drm/panel/sharp-ls043t1le01: " Albert Esteve
2026-05-07 15:36 ` Neil Armstrong
2026-05-07 11:53 ` [PATCH 08/10] drm/panel/truly-nt35597: " Albert Esteve
2026-05-07 15:37 ` Neil Armstrong
2026-05-07 11:53 ` [PATCH 09/10] drm/panel/startek-kd070fhfid015: " Albert Esteve
2026-05-07 15:37 ` Neil Armstrong
2026-05-07 11:53 ` [PATCH 10/10] drm/panel: Make drm_panel_init() static Albert Esteve
2026-05-07 14:57 ` Maxime Ripard
2026-05-07 15:11 ` Albert Esteve [this message]
2026-05-07 15:29 ` Maxime Ripard
2026-05-07 14:57 ` [PATCH 00/10] drm/panel: Use refcounted allocation for remaining panel drivers 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=CADSE00+UN3wgsJnfCn3CLB3h-RnR-FLLfAOY3UhDyCOmt5HTKA@mail.gmail.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