From: Cristian Ciocaltea <cristian.ciocaltea@collabora.com>
To: Heiko Stuebner <heiko@sntech.de>,
dmitry.baryshkov@oss.qualcomm.com, Andy Yan <andyshrk@163.com>
Cc: mripard@kernel.org, neil.armstrong@linaro.org,
andrzej.hajda@intel.com, jernej.skrabec@gmail.com,
jonas@kwiboo.se, Laurent.pinchart@ideasonboard.com,
maarten.lankhorst@linux.intel.com, rfoss@kernel.org,
simona@ffwll.ch, tzimmermann@suse.de, knaerzche@gmail.com,
devicetree@vger.kernel.org, dri-devel@lists.freedesktop.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, linux-rockchip@lists.infradead.org,
Andy Yan <andy.yan@rock-chips.com>
Subject: Re: [PATCH v7 1/2] drm/rockchip: inno-hdmi: Convert to drm bridge
Date: Wed, 3 Sep 2025 16:05:44 +0300 [thread overview]
Message-ID: <218de818-2063-432d-b61b-4537ea702cd6@collabora.com> (raw)
In-Reply-To: <5255838.1BCLMh4Saa@phil>
Hello Heiko,
On 9/3/25 2:59 PM, Heiko Stuebner wrote:
> Hi Andy,
>
> Am Mittwoch, 3. September 2025, 13:07:38 Mitteleuropäische Sommerzeit schrieb Andy Yan:
>> From: Andy Yan <andy.yan@rock-chips.com>
>>
>> Convert it to drm bridge driver, it will be convenient for us to
>> migrate the connector part to the display driver later.
>>
>> Signed-off-by: Andy Yan <andy.yan@rock-chips.com>
>
> more like a general remark, this essentially conflicts with the
> big hiword-cleanup [0] that was merged today, as the inno-hdmi driver
> "lost" its separate HIWORD_UPDATE macro in favor a nicer generic one.
>
> I'm not sure what the best way to proceed is, apart from waiting for
> 6.18-rc1.
This is actually what I also intended to ask you, as I'm in the process of
rebasing the HDMI CEC series on top of next-20250903.
Would it be possible to have an immutable branch of bitmap-for-next and get
it merged to drm-misc-next?
Regards,
Cristian
_______________________________________________
Linux-rockchip mailing list
Linux-rockchip@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-rockchip
next prev parent reply other threads:[~2025-09-03 15:46 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-03 11:07 [PATCH v7 0/2] Convert inno hdmi to drm bridge Andy Yan
2025-09-03 11:07 ` [PATCH v7 1/2] drm/rockchip: inno-hdmi: Convert " Andy Yan
2025-09-03 11:59 ` Heiko Stuebner
2025-09-03 12:27 ` Andy Yan
2025-09-03 12:30 ` Dmitry Baryshkov
2025-09-03 21:01 ` Yury Norov
2025-09-04 2:17 ` Dmitry Baryshkov
2025-09-03 13:05 ` Cristian Ciocaltea [this message]
2025-09-05 0:05 ` Dmitry Baryshkov
2025-09-05 0:40 ` Andy Yan
2025-09-05 14:32 ` Dmitry Baryshkov
2025-09-03 11:07 ` [PATCH v7 2/2] MAINTAINERS: Add entry for Innosilicon hdmi bridge library Andy Yan
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=218de818-2063-432d-b61b-4537ea702cd6@collabora.com \
--to=cristian.ciocaltea@collabora.com \
--cc=Laurent.pinchart@ideasonboard.com \
--cc=andrzej.hajda@intel.com \
--cc=andy.yan@rock-chips.com \
--cc=andyshrk@163.com \
--cc=devicetree@vger.kernel.org \
--cc=dmitry.baryshkov@oss.qualcomm.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=heiko@sntech.de \
--cc=jernej.skrabec@gmail.com \
--cc=jonas@kwiboo.se \
--cc=knaerzche@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--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