From: Cristian Ciocaltea <cristian.ciocaltea@collabora.com>
To: "Sandy Huang" <hjc@rock-chips.com>,
"Heiko Stübner" <heiko@sntech.de>,
"Andy Yan" <andy.yan@rock-chips.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>,
"Andrzej Hajda" <andrzej.hajda@intel.com>,
"Neil Armstrong" <neil.armstrong@linaro.org>,
"Robert Foss" <rfoss@kernel.org>,
"Laurent Pinchart" <Laurent.pinchart@ideasonboard.com>,
"Jonas Karlman" <jonas@kwiboo.se>,
"Jernej Skrabec" <jernej.skrabec@gmail.com>,
"Luca Ceresoli" <luca.ceresoli@bootlin.com>
Cc: kernel@collabora.com, dri-devel@lists.freedesktop.org,
linux-rockchip@lists.infradead.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: [PATCH 0/2] drm: devm_drm_bridge_alloc() conversion and cleanup
Date: Thu, 01 Oct 2026 11:25:10 +0300 [thread overview]
Message-ID: <20261001-bridge-alloc-conv-v1-0-f0a1fe040a86@collabora.com> (raw)
Bridge drivers are expected to allocate their private data via
devm_drm_bridge_alloc(), which also initializes the embedded struct
drm_bridge, including its funcs pointer. Most drivers were converted by
commit 9c399719cfb9 ("drm: convert many bridge drivers from
devm_kzalloc() to devm_drm_bridge_alloc() API"), but a couple of
leftovers remain.
The first patch converts the rk3066_hdmi driver, which still uses
devm_kzalloc(). The second one removes a redundant manual assignment of
the bridge funcs pointer in the lontium-lt8713sx driver, which already
uses devm_drm_bridge_alloc().
Both changes are trivial and have no functional impact. The series is
based on the latest drm-misc-next.
Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@collabora.com>
---
Cristian Ciocaltea (2):
drm/rockchip: rk3066_hdmi: Convert to devm_drm_bridge_alloc() API
drm/bridge: lontium-lt8713sx: Drop redundant bridge funcs assignment
drivers/gpu/drm/bridge/lontium-lt8713sx.c | 1 -
drivers/gpu/drm/rockchip/rk3066_hdmi.c | 8 ++++----
2 files changed, 4 insertions(+), 5 deletions(-)
---
base-commit: 37b346eab23aead52d17a8fa687056bfc651a416
change-id: 20261001-bridge-alloc-conv-f517f9b2521f
next reply other threads:[~2026-10-01 8:25 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-01 8:25 Cristian Ciocaltea [this message]
2026-10-01 8:25 ` [PATCH 1/2] drm/rockchip: rk3066_hdmi: Convert to devm_drm_bridge_alloc() API Cristian Ciocaltea
2026-10-01 8:28 ` Maxime Ripard
2026-10-01 16:31 ` Luca Ceresoli
2026-10-01 8:25 ` [PATCH 2/2] drm/bridge: lontium-lt8713sx: Drop redundant bridge funcs assignment Cristian Ciocaltea
2026-10-01 8:29 ` Maxime Ripard
2026-10-01 16:31 ` Luca Ceresoli
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=20261001-bridge-alloc-conv-v1-0-f0a1fe040a86@collabora.com \
--to=cristian.ciocaltea@collabora.com \
--cc=Laurent.pinchart@ideasonboard.com \
--cc=airlied@gmail.com \
--cc=andrzej.hajda@intel.com \
--cc=andy.yan@rock-chips.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=heiko@sntech.de \
--cc=hjc@rock-chips.com \
--cc=jernej.skrabec@gmail.com \
--cc=jonas@kwiboo.se \
--cc=kernel@collabora.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=luca.ceresoli@bootlin.com \
--cc=maarten.lankhorst@linux.intel.com \
--cc=mripard@kernel.org \
--cc=neil.armstrong@linaro.org \
--cc=rfoss@kernel.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®