From: Mohit Dsor <mohit.dsor@oss.qualcomm.com>
To: 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>,
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>,
Sunyun Yang <syyang@lontium.com>,
Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com>,
Mohit Dsor <mdsor@qti.qualcomm.com>
Cc: dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org,
venkata.valluru@oss.qualcomm.com,
Jessica Zhang <jesszhan0024@gmail.com>,
Mohit Dsor <mohit.dsor@oss.qualcomm.com>
Subject: [PATCH v2] drm/bridge: lt9611c: use drm_atomic_commit in callbacks
Date: Tue, 07 Jul 2026 13:48:35 +0530 [thread overview]
Message-ID: <20260707-lt9611c-v7-v2-1-67d4f688b68d@oss.qualcomm.com> (raw)
DRM bridge atomic callbacks now pass struct drm_atomic_commit, and
the atomic helper functions also expect that type. The lt9611c
driver still declares its callbacks with struct drm_atomic_state,
which makes the callback assignments and helper calls fail to build
with incompatible pointer type errors.
Update the lt9611c callback signatures to match the current DRM
bridge API.
This will fix compilation issue in v7.2.rc1.
Fixes: 96d1cfec419e ("drm/bridge: Add Lontium LT9611C(EX/UXD) MIPI DSI to HDMI driver")
Signed-off-by: Mohit Dsor <mohit.dsor@oss.qualcomm.com>
---
Changes in v2:
- EDITME: describe what is new in this series revision.
- EDITME: use bulletpoints and terse descriptions.
- Link to v1: https://patch.msgid.link/20260707-lt9611c-v7-v1-1-3f48568b6e56@oss.qualcomm.com
---
drivers/gpu/drm/bridge/lontium-lt9611c.c | 7 +++----
1 file changed, 3 insertions(+), 4 deletions(-)
diff --git a/drivers/gpu/drm/bridge/lontium-lt9611c.c b/drivers/gpu/drm/bridge/lontium-lt9611c.c
index cb584855fd8f..022205177a4d 100644
--- a/drivers/gpu/drm/bridge/lontium-lt9611c.c
+++ b/drivers/gpu/drm/bridge/lontium-lt9611c.c
@@ -614,7 +614,7 @@ static void lt9611c_video_setup(struct lt9611c *lt9611c,
}
static void lt9611c_bridge_atomic_pre_enable(struct drm_bridge *bridge,
- struct drm_atomic_state *state)
+ struct drm_atomic_commit *state)
{
struct lt9611c *lt9611c = bridge_to_lt9611c(bridge);
int ret;
@@ -626,7 +626,7 @@ static void lt9611c_bridge_atomic_pre_enable(struct drm_bridge *bridge,
}
static void lt9611c_bridge_atomic_enable(struct drm_bridge *bridge,
- struct drm_atomic_state *state)
+ struct drm_atomic_commit *state)
{
struct lt9611c *lt9611c = bridge_to_lt9611c(bridge);
struct drm_connector *connector;
@@ -652,7 +652,7 @@ static void lt9611c_bridge_atomic_enable(struct drm_bridge *bridge,
}
static void lt9611c_bridge_atomic_post_disable(struct drm_bridge *bridge,
- struct drm_atomic_state *state)
+ struct drm_atomic_commit *state)
{
struct lt9611c *lt9611c = bridge_to_lt9611c(bridge);
int ret;
@@ -1238,4 +1238,3 @@ MODULE_AUTHOR("SunYun Yang <syyang@lontium.com>");
MODULE_DESCRIPTION("Lontium LT9611C(EX/UXD) MIPI DSI to HDMI driver");
MODULE_LICENSE("GPL");
MODULE_FIRMWARE(FW_FILE);
-
---
base-commit: a9f7d19810c7719ca55134a386dfc48160a1bcfc
change-id: 20260707-lt9611c-v7-4c6579cdb267
prerequisite-message-id: 20260508134009.4582-3-syyang@lontium.com
prerequisite-patch-id: e9ce15b4a5842cfde130a813afecf136798179f4
prerequisite-patch-id: 569618a60e8c3615e7347c79b48c4756b7bf85d0
Best regards,
--
Mohit Dsor <mohit.dsor@oss.qualcomm.com>
next reply other threads:[~2026-07-07 8:18 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-07 8:18 Mohit Dsor [this message]
2026-07-07 12:35 ` 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=20260707-lt9611c-v7-v2-1-67d4f688b68d@oss.qualcomm.com \
--to=mohit.dsor@oss.qualcomm.com \
--cc=Laurent.pinchart@ideasonboard.com \
--cc=airlied@gmail.com \
--cc=andrzej.hajda@intel.com \
--cc=dmitry.baryshkov@oss.qualcomm.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=jernej.skrabec@gmail.com \
--cc=jesszhan0024@gmail.com \
--cc=jonas@kwiboo.se \
--cc=linux-kernel@vger.kernel.org \
--cc=luca.ceresoli@bootlin.com \
--cc=maarten.lankhorst@linux.intel.com \
--cc=mdsor@qti.qualcomm.com \
--cc=mripard@kernel.org \
--cc=neil.armstrong@linaro.org \
--cc=rfoss@kernel.org \
--cc=simona@ffwll.ch \
--cc=syyang@lontium.com \
--cc=tzimmermann@suse.de \
--cc=venkata.valluru@oss.qualcomm.com \
/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®