From: Cristian Ciocaltea <cristian.ciocaltea@collabora.com>
To: "Heiko Stübner" <heiko@sntech.de>,
"Sandy Huang" <hjc@rock-chips.com>,
"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>,
"Rob Herring" <robh@kernel.org>,
"Krzysztof Kozlowski" <krzk+dt@kernel.org>,
"Conor Dooley" <conor+dt@kernel.org>
Cc: Alexandre ARNOUD <aarnoud@me.com>,
kernel@collabora.com, dri-devel@lists.freedesktop.org,
linux-arm-kernel@lists.infradead.org,
linux-rockchip@lists.infradead.org, linux-kernel@vger.kernel.org,
devicetree@vger.kernel.org
Subject: Re: [PATCH v2 0/4] Add support for HDMI1 output on RK3588 SoC
Date: Wed, 11 Dec 2024 11:16:14 +0200 [thread overview]
Message-ID: <43ae0fc5-d775-49d7-80cd-af111ff8fb25@collabora.com> (raw)
In-Reply-To: <12942826.iMDcRRXYNz@diego>
Hi Heiko,
On 12/11/24 10:46 AM, Heiko Stübner wrote:
> Hi Cristian,
>
> Am Mittwoch, 11. Dezember 2024, 00:06:13 CET schrieb Cristian Ciocaltea:
>> The patches provide the basic support to handle the second HDMI output
>> port found on Rockchip RK3588 SoC.
>>
>> For now I enabled it on Radxa ROCK 5B only, the board I've been using to
>> validate this.
>>
>> ** IMPORTANT **
>>
>> The series has a runtime dependency on "phy: phy-rockchip-samsung-hdptx:
>> Don't use dt aliases to determine phy-id", a patch submitted recently by
>> Heiko [1]. Without applying it, the functionality on both HDMI TX ports
>> will break.
>
> Looking at the drm/rockchip patch, that should not cause disruptions on
> its own, right?
>
> Only with the dts-parts enabled would we run into phy-issue.
> (Asking, because things go through different trees and the drm
> part looks ready)
That's right, I should have better explained this - all patches except
the last one (that is actually enabling HDMI1 on a specific board) can
be safely applied.
Thanks,
Cristian
WARNING: multiple messages have this Message-ID (diff)
From: Cristian Ciocaltea <cristian.ciocaltea@collabora.com>
To: "Heiko Stübner" <heiko@sntech.de>,
"Sandy Huang" <hjc@rock-chips.com>,
"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>,
"Rob Herring" <robh@kernel.org>,
"Krzysztof Kozlowski" <krzk+dt@kernel.org>,
"Conor Dooley" <conor+dt@kernel.org>
Cc: Alexandre ARNOUD <aarnoud@me.com>,
kernel@collabora.com, dri-devel@lists.freedesktop.org,
linux-arm-kernel@lists.infradead.org,
linux-rockchip@lists.infradead.org, linux-kernel@vger.kernel.org,
devicetree@vger.kernel.org
Subject: Re: [PATCH v2 0/4] Add support for HDMI1 output on RK3588 SoC
Date: Wed, 11 Dec 2024 11:16:14 +0200 [thread overview]
Message-ID: <43ae0fc5-d775-49d7-80cd-af111ff8fb25@collabora.com> (raw)
In-Reply-To: <12942826.iMDcRRXYNz@diego>
Hi Heiko,
On 12/11/24 10:46 AM, Heiko Stübner wrote:
> Hi Cristian,
>
> Am Mittwoch, 11. Dezember 2024, 00:06:13 CET schrieb Cristian Ciocaltea:
>> The patches provide the basic support to handle the second HDMI output
>> port found on Rockchip RK3588 SoC.
>>
>> For now I enabled it on Radxa ROCK 5B only, the board I've been using to
>> validate this.
>>
>> ** IMPORTANT **
>>
>> The series has a runtime dependency on "phy: phy-rockchip-samsung-hdptx:
>> Don't use dt aliases to determine phy-id", a patch submitted recently by
>> Heiko [1]. Without applying it, the functionality on both HDMI TX ports
>> will break.
>
> Looking at the drm/rockchip patch, that should not cause disruptions on
> its own, right?
>
> Only with the dts-parts enabled would we run into phy-issue.
> (Asking, because things go through different trees and the drm
> part looks ready)
That's right, I should have better explained this - all patches except
the last one (that is actually enabling HDMI1 on a specific board) can
be safely applied.
Thanks,
Cristian
_______________________________________________
Linux-rockchip mailing list
Linux-rockchip@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-rockchip
next prev parent reply other threads:[~2024-12-11 9:17 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-10 23:06 [PATCH v2 0/4] Add support for HDMI1 output on RK3588 SoC Cristian Ciocaltea
2024-12-10 23:06 ` Cristian Ciocaltea
2024-12-10 23:06 ` [PATCH v2 1/4] drm/rockchip: dw_hdmi_qp: Add support for RK3588 HDMI1 output Cristian Ciocaltea
2024-12-10 23:06 ` Cristian Ciocaltea
2024-12-10 23:55 ` Dmitry Baryshkov
2024-12-10 23:55 ` Dmitry Baryshkov
2024-12-10 23:06 ` [PATCH v2 2/4] arm64: dts: rockchip: Add PHY node for HDMI1 TX port on RK3588 Cristian Ciocaltea
2024-12-10 23:06 ` Cristian Ciocaltea
2024-12-27 13:17 ` Jagan Teki
2024-12-27 13:17 ` Jagan Teki
2024-12-10 23:06 ` [PATCH v2 3/4] arm64: dts: rockchip: Add HDMI1 node " Cristian Ciocaltea
2024-12-10 23:06 ` Cristian Ciocaltea
2024-12-27 13:19 ` Jagan Teki
2024-12-27 13:19 ` Jagan Teki
2024-12-10 23:06 ` [PATCH v2 4/4] arm64: dts: rockchip: Enable HDMI1 on rock-5b Cristian Ciocaltea
2024-12-10 23:06 ` Cristian Ciocaltea
2025-03-31 19:01 ` Mark Brown
2025-03-31 19:01 ` Mark Brown
2025-03-31 20:30 ` Sebastian Reichel
2025-03-31 20:30 ` Sebastian Reichel
2024-12-11 8:46 ` [PATCH v2 0/4] Add support for HDMI1 output on RK3588 SoC Heiko Stübner
2024-12-11 8:46 ` Heiko Stübner
2024-12-11 9:16 ` Cristian Ciocaltea [this message]
2024-12-11 9:16 ` Cristian Ciocaltea
2024-12-11 9:42 ` Alexandre ARNOUD
2024-12-11 9:42 ` Alexandre ARNOUD
2024-12-11 9:52 ` Cristian Ciocaltea
2024-12-11 9:52 ` Cristian Ciocaltea
2024-12-11 10:43 ` (subset) " Heiko Stuebner
2024-12-11 10:43 ` Heiko Stuebner
2025-02-11 9:28 ` Heiko Stuebner
2025-02-11 9:28 ` Heiko Stuebner
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=43ae0fc5-d775-49d7-80cd-af111ff8fb25@collabora.com \
--to=cristian.ciocaltea@collabora.com \
--cc=aarnoud@me.com \
--cc=airlied@gmail.com \
--cc=andy.yan@rock-chips.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=heiko@sntech.de \
--cc=hjc@rock-chips.com \
--cc=kernel@collabora.com \
--cc=krzk+dt@kernel.org \
--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=robh@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.