linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: "Heiko Stübner" <heiko@sntech.de>
To: Andy Yan <andyshrk@163.com>,
	Sebastian Reichel <sebastian.reichel@collabora.com>
Cc: linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org,
	detlev.casanova@collabora.com,
	linux-rockchip@lists.infradead.org,
	Andy Yan <andy.yan@rock-chips.com>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 0/3] Add display subsystem dt node on rk3576
Date: Tue, 04 Mar 2025 22:16:49 +0100	[thread overview]
Message-ID: <2627393.Mh6RI2rZIc@diego> (raw)
In-Reply-To: <lfmhqurnpjmfy6pfjxd5aczxujislv2p5bsurcbl7capyt7zv3@hy2twvjj53uz>

Am Dienstag, 4. März 2025, 15:47:28 MEZ schrieb Sebastian Reichel:
> Hello,
> 
> On Tue, Dec 31, 2024 at 06:57:21AM -0600, Rob Herring (Arm) wrote:
> > On Tue, 31 Dec 2024 17:57:17 +0800, Andy Yan wrote:
> > > As the VOP[0] and HDMI[1] driver have already been submitted for review.
> > > This series enable hdmi display on sige5 board.
> > > 
> > > [0] https://lore.kernel.org/linux-rockchip/20241231090802.251787-1-andyshrk@163.com/T/#t
> > > [1] https://lore.kernel.org/linux-rockchip/20241231094425.253398-1-andyshrk@163.com/T/#t
> > > 
> > > Changes in v3:
> > > - Split from https://lore.kernel.org/linux-rockchip/3330586.aeNJFYEL58@diego/T/#t
> > > 
> > > Andy Yan (3):
> > >   arm64: dts: rockchip: Add vop for rk3576
> > >   arm64: dts: rockchip: Add hdmi for rk3576
> > >   arm64: dts: rockchip: Enable hdmi display on sige5
> > > 
> > >  .../boot/dts/rockchip/rk3576-armsom-sige5.dts |  47 +++++++
> > >  arch/arm64/boot/dts/rockchip/rk3576.dtsi      | 126 ++++++++++++++++++
> > >  2 files changed, 173 insertions(+)
> >
> > [...] (a bunch of warnings due to dependency patch series not yet
> > being in linux-next)
> 
> I think all dependencies have landed now. But it might be sensible
> to do a quick resend considering how old this is.
> 
> Would be nice to have initial RK3576 HDMI support in 6.15 :)

now we can :-)

The update was not that difficult, so did it myself when applying.


Heiko




  reply	other threads:[~2025-03-04 21:50 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-31  9:57 [PATCH v3 0/3] Add display subsystem dt node on rk3576 Andy Yan
2024-12-31  9:57 ` [PATCH v3 1/3] arm64: dts: rockchip: Add vop for rk3576 Andy Yan
2025-03-04 17:15   ` Detlev Casanova
2024-12-31  9:57 ` [PATCH v3 2/3] arm64: dts: rockchip: Add hdmi " Andy Yan
2025-03-04 17:17   ` Detlev Casanova
2024-12-31  9:57 ` [PATCH v3 3/3] arm64: dts: rockchip: Enable hdmi display on sige5 Andy Yan
2024-12-31 12:57 ` [PATCH v3 0/3] Add display subsystem dt node on rk3576 Rob Herring (Arm)
2025-03-04 14:47   ` Sebastian Reichel
2025-03-04 21:16     ` Heiko Stübner [this message]
2025-03-05  2:55       ` Andy Yan
2025-03-04 21:14 ` 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=2627393.Mh6RI2rZIc@diego \
    --to=heiko@sntech.de \
    --cc=andy.yan@rock-chips.com \
    --cc=andyshrk@163.com \
    --cc=detlev.casanova@collabora.com \
    --cc=devicetree@vger.kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rockchip@lists.infradead.org \
    --cc=sebastian.reichel@collabora.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;
as well as URLs for NNTP newsgroup(s).