From: "Dixit, Ashutosh" <ashutosh.dixit@intel.com>
To: Anusha Srivatsa <asrivats@redhat.com>
Cc: <imre.deak@intel.com>, Neil Armstrong <neil.armstrong@linaro.org>,
"Jessica Zhang" <quic_jesszhan@quicinc.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>,
Linus Walleij <linus.walleij@linaro.org>,
Joel Selvaraj <jo@jsfamily.in>,
Douglas Anderson <dianders@chromium.org>,
<dri-devel@lists.freedesktop.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 04/10] panel/auo-a030jtn01: Use refcounted allocation in place of devm_kzalloc()
Date: Mon, 07 Apr 2025 17:18:23 -0700 [thread overview]
Message-ID: <87bjt7eca8.wl-ashutosh.dixit@intel.com> (raw)
In-Reply-To: <85a58rsgjj.wl-ashutosh.dixit@intel.com>
On Mon, 07 Apr 2025 16:22:40 -0700, Dixit, Ashutosh wrote:
>
> On Mon, 07 Apr 2025 08:49:23 -0700, Imre Deak wrote:
> >
> > Hi,
> >
> > On Tue, Apr 01, 2025 at 12:03:47PM -0400, Anusha Srivatsa wrote:
> > > Move to using the new API devm_drm_panel_alloc() to allocate the
> > > panel.
> > >
> > > Signed-off-by: Anusha Srivatsa <asrivats@redhat.com>
> > > ---
> > > drivers/gpu/drm/panel/panel-auo-a030jtn01.c | 10 ++++------
> > > 1 file changed, 4 insertions(+), 6 deletions(-)
> > >
> > > diff --git a/drivers/gpu/drm/panel/panel-auo-a030jtn01.c b/drivers/gpu/drm/panel/panel-auo-a030jtn01.c
> > > index 77604d6a4e72c915c40575be0e47810c90b4ed71..83529b1c2bac2e29f41efaf4028950214b056a95 100644
> > > --- a/drivers/gpu/drm/panel/panel-auo-a030jtn01.c
> > > +++ b/drivers/gpu/drm/panel/panel-auo-a030jtn01.c
> > > @@ -200,9 +200,10 @@ static int a030jtn01_probe(struct spi_device *spi)
> > >
> > > spi->mode |= SPI_MODE_3 | SPI_3WIRE;
> > >
> > > - priv = devm_kzalloc(dev, sizeof(*priv), GFP_KERNEL);
> > > - if (!priv)
> > > - return -ENOMEM;
> > > + panel = devm_drm_panel_alloc(dev, struct a030jtn01, panel,
> > > + &a030jtn01_funcs, DRM_MODE_CONNECTOR_DPI);
> >
> > This doesn't compile and (yet) it's pushed already to drm-tip. AFAIU
> > it's supposed to be
> > priv = devm_drm_panel_alloc(...);
>
> Yes:
>
> drivers/gpu/drm/panel/panel-auo-a030jtn01.c: In function ‘a030jtn01_probe’:
> drivers/gpu/drm/panel/panel-auo-a030jtn01.c:203:9: error: ‘panel’ undeclared (first use in this function)
> 203 | panel = devm_drm_panel_alloc(dev, struct a030jtn01, panel,
> | ^~~~~
> drivers/gpu/drm/panel/panel-auo-a030jtn01.c:203:9: note: each undeclared identifier is reported only once for each function it appears in
>
> Please turn on the config options for particular module if you are making
> changes to that module.
Though probably, you can argue, that the pre-merge CI build should already
be doing this. A sort of allmodconfig for the DRM subsystem, so that these
kinds of issues don't get missed.
>
> >
> > > + if (IS_ERR(panel))
> > > + return PTR_ERR(panel);
> > >
> > > priv->spi = spi;
> > > spi_set_drvdata(spi, priv);
> > > @@ -223,9 +224,6 @@ static int a030jtn01_probe(struct spi_device *spi)
> > > if (IS_ERR(priv->reset_gpio))
> > > return dev_err_probe(dev, PTR_ERR(priv->reset_gpio), "Failed to get reset GPIO");
> > >
> > > - drm_panel_init(&priv->panel, dev, &a030jtn01_funcs,
> > > - DRM_MODE_CONNECTOR_DPI);
> > > -
> > > err = drm_panel_of_backlight(&priv->panel);
> > > if (err)
> > > return err;
> > >
> > > --
> > > 2.48.1
> > >
next prev parent reply other threads:[~2025-04-08 0:18 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-01 16:03 [PATCH 00/10] drm/panel: Use refcounted allocation in place of devm_kzalloc() Anusha Srivatsa
2025-04-01 16:03 ` [PATCH 01/10] panel/abt-y030xx067a: Use the " Anusha Srivatsa
2025-04-01 16:03 ` [PATCH 02/10] panel/arm-versatile: " Anusha Srivatsa
2025-04-15 8:01 ` Linus Walleij
2025-04-01 16:03 ` [PATCH 03/10] panel/z00t-tm5p5-n35596: Use " Anusha Srivatsa
2025-04-01 16:03 ` [PATCH 04/10] panel/auo-a030jtn01: " Anusha Srivatsa
2025-04-07 15:49 ` Imre Deak
2025-04-07 23:22 ` Dixit, Ashutosh
2025-04-08 0:18 ` Dixit, Ashutosh [this message]
2025-04-08 1:40 ` Dixit, Ashutosh
2025-04-08 4:01 ` Dixit, Ashutosh
2025-04-08 6:47 ` Borah, Chaitanya Kumar
2025-04-08 12:50 ` Maxime Ripard
2025-04-08 13:03 ` Borah, Chaitanya Kumar
2025-04-08 13:51 ` Jani Nikula
2025-04-08 14:26 ` Dmitry Baryshkov
2025-04-08 14:38 ` Lucas De Marchi
2025-04-08 12:48 ` Maxime Ripard
2025-04-01 16:03 ` [PATCH 05/10] panel/bf060y8m-aj0: " Anusha Srivatsa
2025-04-01 16:03 ` [PATCH 06/10] panel/th101mb31ig002-28a: " Anusha Srivatsa
2025-04-08 8:24 ` Thomas Zimmermann
2025-04-01 16:03 ` [PATCH 07/10] panel/boe-tv101wum-ll2: " Anusha Srivatsa
2025-04-08 8:27 ` Thomas Zimmermann
2025-04-01 16:03 ` [PATCH 08/10] panel/dsi-cm: " Anusha Srivatsa
2025-04-01 16:03 ` [PATCH 09/10] panel/ebbg-ft8719: " Anusha Srivatsa
2025-04-01 16:03 ` [PATCH 10/10] panel/panel-edp: " Anusha Srivatsa
2025-04-02 14:24 ` [PATCH 00/10] drm/panel: " Neil Armstrong
2025-04-07 8:34 ` 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=87bjt7eca8.wl-ashutosh.dixit@intel.com \
--to=ashutosh.dixit@intel.com \
--cc=airlied@gmail.com \
--cc=asrivats@redhat.com \
--cc=dianders@chromium.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=imre.deak@intel.com \
--cc=jo@jsfamily.in \
--cc=linus.walleij@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=mripard@kernel.org \
--cc=neil.armstrong@linaro.org \
--cc=quic_jesszhan@quicinc.com \
--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