From: "Heiko Stübner" <heiko@sntech.de>
To: linux-rockchip@lists.infradead.org, Jagan Teki <jagan@edgeble.ai>
Cc: Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
Cristian Ciocaltea <cristian.ciocaltea@collabora.com>
Subject: Re: [PATCH V2] arm64: dts: rockchip: Enable HDMI1 out for Edgeble-6TOPS Modules
Date: Mon, 10 Feb 2025 14:12:47 +0100 [thread overview]
Message-ID: <2928143.Icojqenx9y@diego> (raw)
In-Reply-To: <CA+VMnFwHEXWP=d_X0T0E9fHFDCkXHxpvgML6jAHNfh9ikXTZWw@mail.gmail.com>
Hi Jagan,
Am Montag, 10. Februar 2025, 13:51:07 MEZ schrieb Jagan Teki:
> On Fri, 27 Dec 2024 at 18:59, Jagan Teki <jagan@edgeble.ai> wrote:
> >
> > Edgeble-6TOPS modules configure HDMI1 for HDMI Out from RK3588.
> >
> > Enable it on Edgeble-6TOPS IO Board dtsi.
> >
> > Cc: Cristian Ciocaltea <cristian.ciocaltea@collabora.com>
> > Signed-off-by: Jagan Teki <jagan@edgeble.ai>
> > ---
> > Changes for v2:
> > - Rebase on top of Cristian's series
> > https://patchwork.kernel.org/project/linux-rockchip/cover/20241211-rk3588-hdmi1-v2-0-02cdca22ff68@collabora.com/
> > - Update hdptxphy1
>
> Cristian's seems merged, please queue this as well.
only partially, i.e. I merged patch 1 of 4, because actually enabling the
hdmi1 controller needs the alias-removal from the phy driver, see
Cristian's link "[1]" in his cover letter.
And phy maintainers seem to still be otherwise occupied [2].
Heiko
[1] https://lore.kernel.org/lkml/20241206103401.1780416-3-heiko@sntech.de/
[2] https://git.kernel.org/pub/scm/linux/kernel/git/phy/linux-phy.git/log/?h=next
next prev parent reply other threads:[~2025-02-10 13:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-27 13:29 [PATCH V2] arm64: dts: rockchip: Enable HDMI1 out for Edgeble-6TOPS Modules Jagan Teki
2025-02-10 12:51 ` Jagan Teki
2025-02-10 13:12 ` Heiko Stübner [this message]
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=2928143.Icojqenx9y@diego \
--to=heiko@sntech.de \
--cc=conor+dt@kernel.org \
--cc=cristian.ciocaltea@collabora.com \
--cc=devicetree@vger.kernel.org \
--cc=jagan@edgeble.ai \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=robh@kernel.org \
/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