From: "qinjian[覃健]" <qinjian@cqplus1.com>
To: Arnd Bergmann <arnd@arndb.de>
Cc: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>,
Rob Herring <robh+dt@kernel.org>,
Michael Turquette <mturquette@baylibre.com>,
"Stephen Boyd" <sboyd@kernel.org>,
Thomas Gleixner <tglx@linutronix.de>,
Marc Zyngier <maz@kernel.org>,
Philipp Zabel <p.zabel@pengutronix.de>,
"Russell King - ARM Linux" <linux@armlinux.org.uk>,
Linux ARM <linux-arm-kernel@lists.infradead.org>,
DTML <devicetree@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
linux-clk <linux-clk@vger.kernel.org>
Subject: RE: [PATCH v14 0/9] Add Sunplus SP7021 SoC Support
Date: Fri, 6 May 2022 08:34:17 +0000 [thread overview]
Message-ID: <23e22e4e8b9e4d7ab02caaa1c3f7b599@cqplus1.com> (raw)
In-Reply-To: <CAK8P3a0W4wpVwDmCXDkm_u9W=JozrnCnxW7zK3h2XD8f_ODy6w@mail.gmail.com>
>
> On Fri, May 6, 2022 at 5:23 AM Qin Jian <qinjian@cqplus1.com> wrote:
> >
> > This patch series add Sunplus SP7021 SoC support.
> >
> > Sunplus SP7021 is an ARM Cortex A7 (4 cores) based SoC. It integrates many
> > peripherals (ex: UART, I2C, SPI, SDIO, eMMC, USB, SD card and etc.) into a
> > single chip. It is designed for industrial control.
> >
> > SP7021 consists of two chips (dies) in a package. One is called C-chip
> > (computing chip). It is a 4-core ARM Cortex A7 CPU. It adopts high-level
> > process (22 nm) for high performance computing. The other is called P-
> > chip (peripheral chip). It has many peripherals and an ARM A926 added
> > especially for real-time control. P-chip is made for customers. It adopts
> > low-level process (ex: 0.11 um) to reduce cost.
>
> Just an update from my side about merging the platform code: the
> submission looks mostly sensible to me, but as long as the clk and irqchip
> drivers have not finished the review, I cannot take this through the soc
> tree. We could consider merging the platform code without those two
> drivers, but that seems pointless because it will not boot.
>
The reviewers no reply, I don’t know why.
> What is the reason you don't include a .dtsi file in this series? Usually
> there should be at least one board and the description of the SoC itself.
> Again, without those I'm not sure it's worth merging.
>
Sorry, I'll add the dts file in next patch.
> For the timing, we are getting close to the 5.19 merge window that
> starts once v5.18 is out, and I don't expect that all the above will
> be resolved in time, so it looks we will have to defer it by one more
> release to 5.20.
>
> Arnd
next prev parent reply other threads:[~2022-05-06 8:36 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-06 3:23 [PATCH v14 0/9] Add Sunplus SP7021 SoC Support Qin Jian
2022-05-06 3:23 ` [PATCH v14 1/9] dt-bindings: arm: sunplus: Add bindings for Sunplus SP7021 SoC boards Qin Jian
2022-05-06 3:23 ` [PATCH v14 2/9] dt-bindings: reset: Add bindings for SP7021 reset driver Qin Jian
2022-05-06 3:23 ` [PATCH v14 3/9] reset: Add Sunplus " Qin Jian
2022-05-06 3:23 ` [PATCH v14 4/9] dt-bindings: clock: Add bindings for SP7021 clock driver Qin Jian
2022-05-06 6:33 ` Krzysztof Kozlowski
2022-05-06 3:23 ` [PATCH v14 5/9] clk: Add Sunplus " Qin Jian
2022-05-06 3:23 ` [PATCH v14 6/9] dt-bindings: interrupt-controller: Add bindings for SP7021 interrupt controller Qin Jian
2022-05-06 6:35 ` Krzysztof Kozlowski
2022-05-06 7:01 ` qinjian[覃健]
2022-05-06 7:15 ` Krzysztof Kozlowski
2022-05-06 3:23 ` [PATCH v14 7/9] irqchip: Add Sunplus SP7021 interrupt controller driver Qin Jian
2022-05-06 11:01 ` Marc Zyngier
2022-05-06 19:26 ` kernel test robot
2022-05-06 3:23 ` [PATCH v14 8/9] ARM: sunplus: Add initial support for Sunplus SP7021 SoC Qin Jian
2022-05-06 11:25 ` kernel test robot
2022-05-06 3:23 ` [PATCH v14 9/9] ARM: sp7021_defconfig: Add Sunplus SP7021 defconfig Qin Jian
2022-05-06 7:31 ` [PATCH v14 0/9] Add Sunplus SP7021 SoC Support Arnd Bergmann
2022-05-06 8:34 ` qinjian[覃健] [this message]
2022-05-06 8:49 ` Arnd Bergmann
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=23e22e4e8b9e4d7ab02caaa1c3f7b599@cqplus1.com \
--to=qinjian@cqplus1.com \
--cc=arnd@arndb.de \
--cc=devicetree@vger.kernel.org \
--cc=krzysztof.kozlowski@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=maz@kernel.org \
--cc=mturquette@baylibre.com \
--cc=p.zabel@pengutronix.de \
--cc=robh+dt@kernel.org \
--cc=sboyd@kernel.org \
--cc=tglx@linutronix.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;
as well as URLs for NNTP newsgroup(s).