From: Anusha Srivatsa <asrivats@redhat.com>
To: Neil Armstrong <neil.armstrong@linaro.org>,
Jessica Zhang <jessica.zhang@oss.qualcomm.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>
Cc: Geert Uytterhoeven <geert@linux-m68k.org>,
dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org,
Anusha Srivatsa <asrivats@redhat.com>
Subject: [PATCH 2/6] drm/panel/truly-nt35597: Use refcounted allocation in place of devm_kzalloc()
Date: Tue, 08 Jul 2025 15:35:14 -0500 [thread overview]
Message-ID: <20250708-b4-simple-panel-api-convert-july-v1-2-630902123ea1@redhat.com> (raw)
In-Reply-To: <20250708-b4-simple-panel-api-convert-july-v1-0-630902123ea1@redhat.com>
Move to using the new API devm_drm_panel_alloc() to allocate the
panel. In the call to the new API, avoid using explicit type and use
__typeof() for more type safety.
Signed-off-by: Anusha Srivatsa <asrivats@redhat.com>
---
drivers/gpu/drm/panel/panel-truly-nt35597.c | 10 +++++-----
1 file changed, 5 insertions(+), 5 deletions(-)
diff --git a/drivers/gpu/drm/panel/panel-truly-nt35597.c b/drivers/gpu/drm/panel/panel-truly-nt35597.c
index d447db912a61ec958a4718ce49454f5f706e41db..eb6c2608e4f1509c9626dcda790aee3f9b21eb8b 100644
--- a/drivers/gpu/drm/panel/panel-truly-nt35597.c
+++ b/drivers/gpu/drm/panel/panel-truly-nt35597.c
@@ -476,8 +476,6 @@ static int truly_nt35597_panel_add(struct truly_nt35597 *ctx)
/* dual port */
gpiod_set_value(ctx->mode_gpio, 0);
- drm_panel_init(&ctx->panel, dev, &truly_nt35597_drm_funcs,
- DRM_MODE_CONNECTOR_DSI);
drm_panel_add(&ctx->panel);
return 0;
@@ -523,10 +521,12 @@ static int truly_nt35597_probe(struct mipi_dsi_device *dsi)
.node = NULL,
};
- ctx = devm_kzalloc(dev, sizeof(*ctx), GFP_KERNEL);
+ ctx = devm_drm_panel_alloc(dev, __typeof(*ctx), panel,
+ &truly_nt35597_drm_funcs,
+ DRM_MODE_CONNECTOR_DSI);
- if (!ctx)
- return -ENOMEM;
+ if (IS_ERR(ctx))
+ return PTR_ERR(ctx);
/*
* This device represents itself as one with two input ports which are
--
2.48.1
next prev parent reply other threads:[~2025-07-08 20:36 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-08 20:35 [PATCH 0/6] drm/panel: Use refcounted allocation in place of devm_kzalloc() - Part4 Anusha Srivatsa
2025-07-08 20:35 ` [PATCH 1/6] drm/panel/visionox-g2647fb105: Use refcounted allocation in place of devm_kzalloc() Anusha Srivatsa
2025-07-09 13:01 ` Maxime Ripard
2025-07-08 20:35 ` Anusha Srivatsa [this message]
2025-07-09 13:01 ` [PATCH 2/6] drm/panel/truly-nt35597: " Maxime Ripard
2025-07-08 20:35 ` [PATCH 3/6] drm/panel/tdo-tl070wsh30: " Anusha Srivatsa
2025-07-09 13:03 ` Maxime Ripard
2025-07-08 20:35 ` [PATCH 4/6] drm/panel/kd070fhfid015: " Anusha Srivatsa
2025-07-09 13:04 ` Maxime Ripard
2025-07-08 20:35 ` [PATCH 5/6] drm/panel/ls043t1le01: " Anusha Srivatsa
2025-07-09 13:04 ` Maxime Ripard
2025-07-08 20:35 ` [PATCH 6/6] drm/panel/samsung-s6e63m0: " Anusha Srivatsa
2025-07-09 13:05 ` 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=20250708-b4-simple-panel-api-convert-july-v1-2-630902123ea1@redhat.com \
--to=asrivats@redhat.com \
--cc=airlied@gmail.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=geert@linux-m68k.org \
--cc=jessica.zhang@oss.qualcomm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=mripard@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
all inboxes | Powered by JetHome®