From: Heiko Stuebner <heiko@sntech.de>
To: Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Jiri Slaby <jirislaby@kernel.org>,
Chris Morgan <macromorgan@hotmail.com>,
Jonas Karlman <jonas@kwiboo.se>, Tim Lunn <tim@feathertop.org>,
Andy Yan <andyshrk@163.com>,
Muhammed Efe Cetin <efectn@protonmail.com>,
Jagan Teki <jagan@edgeble.ai>, Dragan Simic <dsimic@manjaro.org>,
Ondrej Jirman <megi@xff.cz>,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-rockchip@lists.infradead.org, linux-kernel@vger.kernel.org,
linux-serial@vger.kernel.org, Yao Zi <ziyao@disroot.org>
Cc: Celeste Liu <CoelacanthusHex@gmail.com>
Subject: Re: [PATCH v4 0/4] Add initial support for Rockchip RK3528 SoC
Date: Wed, 18 Sep 2024 01:13:25 +0200 [thread overview]
Message-ID: <23655990.6Emhk5qWAg@phil> (raw)
In-Reply-To: <ZunjLMQGEcES2zIV@pineapple>
Hey,
Am Dienstag, 17. September 2024, 22:14:36 CEST schrieb Yao Zi:
> On Thu, Aug 29, 2024 at 09:27:01AM +0000, Yao Zi wrote:
> > Rockchip RK3528 is a quad-core ARM Cortex-A53 SoC designed for
> > multimedia application. This series add a basic device tree with CPU,
> > interrupts and UART nodes for it and is able to boot into a kernel with
> > only UART console.
> >
> > Has been tested on Radxa E20C board[1] with vendor U-boot, successfully
> > booted into initramfs with this log[2].
> Ping on this thread. Is it possible to get this merged in v6.12? Or
> anything else I need to do?
sadly nope. From a timeline point of view things should ideally be in the
Rockchip tree by -rc6 . Which then move to the soc tree and from there
to Linus' tree.
There is this rule that all new development for a -rc1 kernel should be
present in linux-next _before_ the merge-window opens.
The thing we need to figure out for your series is the uart binding,
because that _should_ go through the tree handling serial drivers.
Greg is in your cc list but with the amount of mail he gets, I don't
think he has single-parts of patch series on his radar.
So I guess the easiest way would be to send the uart-binding from patch 1
as a completely separate patch with adapted Cc list, so that it's obvious
this should go through the serial tree.
From talking with Collabora people today at the Open Source Summit, it
seems that's also their plan for the rk3576 that is stuck at a similar
state.
Hope that helps a bit to explain
Heiko
next prev parent reply other threads:[~2024-09-17 23:15 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-29 9:27 [PATCH v4 0/4] Add initial support for Rockchip RK3528 SoC Yao Zi
2024-08-29 9:27 ` [PATCH v4 1/4] dt-bindings: serial: snps-dw-apb-uart: Document Rockchip RK3528 Yao Zi
2024-08-29 9:27 ` [PATCH v4 2/4] dt-bindings: arm: rockchip: Add Radxa E20C board Yao Zi
2024-08-29 9:27 ` [PATCH v4 3/4] arm64: dts: rockchip: Add base DT for rk3528 SoC Yao Zi
2024-08-29 9:27 ` [PATCH v4 4/4] arm64: dts: rockchip: Add Radxa e20c board Yao Zi
2024-09-17 20:14 ` [PATCH v4 0/4] Add initial support for Rockchip RK3528 SoC Yao Zi
2024-09-17 23:13 ` Heiko Stuebner [this message]
2024-09-18 6:21 ` Greg Kroah-Hartman
2024-09-19 10:44 ` Yao Zi
2024-10-12 19:07 ` (subset) " 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=23655990.6Emhk5qWAg@phil \
--to=heiko@sntech.de \
--cc=CoelacanthusHex@gmail.com \
--cc=andyshrk@163.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dsimic@manjaro.org \
--cc=efectn@protonmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=jagan@edgeble.ai \
--cc=jirislaby@kernel.org \
--cc=jonas@kwiboo.se \
--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=linux-serial@vger.kernel.org \
--cc=macromorgan@hotmail.com \
--cc=megi@xff.cz \
--cc=robh@kernel.org \
--cc=tim@feathertop.org \
--cc=ziyao@disroot.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;
as well as URLs for NNTP newsgroup(s).