linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Peter Chen <peter.chen@cixtech.com>
To: Marc Zyngier <maz@kernel.org>
Cc: soc@kernel.org, robh@kernel.org, krzk+dt@kernel.org,
	conor+dt@kernel.org, catalin.marinas@arm.com, will@kernel.org,
	arnd@arndb.de, linux-arm-kernel@lists.infradead.org,
	devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
	cix-kernel-upstream@cixtech.com, marcin@juszkiewicz.com.pl,
	kajetan.puchalski@arm.com,
	Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>,
	Fugang Duan <fugang.duan@cixtech.com>
Subject: Re: [PATCH v5 5/6] arm64: dts: cix: add initial CIX P1(SKY1) dts support
Date: Thu, 27 Mar 2025 14:44:38 +0800	[thread overview]
Message-ID: <Z-Tz1moMNozx23k6@nchen-desktop> (raw)
In-Reply-To: <861pukm9yd.wl-maz@kernel.org>

> >
> > On 25-03-25 10:52:10, Marc Zyngier wrote:
> > > > +     timer {
> > > > +             compatible = "arm,armv8-timer";
> > > > +             interrupt-names = "sec-phys", "phys", "virt", "hyp-phys", "hyp-virt";
> > > > +             interrupts = <GIC_PPI 13 IRQ_TYPE_LEVEL_LOW 0>,
> > > > +                          <GIC_PPI 14 IRQ_TYPE_LEVEL_LOW 0>,
> > > > +                          <GIC_PPI 11 IRQ_TYPE_LEVEL_LOW 0>,
> > > > +                          <GIC_PPI 10 IRQ_TYPE_LEVEL_LOW 0>,
> > > > +                          <GIC_PPI 12 IRQ_TYPE_LEVEL_LOW 0>;
> > > > +     };
> > > > +};
> > >
> > > I don't think there is anything wrong here, but it is also a pretty
> > > useless DT. There isn't even a UART to interact with the machine and
> > > find out whether it has actually booted.
> > >
> >
> > UEFI uses the same UART, so we could see all kernel boot logs until
> > switch to use kernel UART driver for printk. If you would like boot
> > to the console at initramfs, just add uart node like patchset v1.
> 
> What's the point in upstreaming something that requires extra changes
> just to boot it? It only outlines these patches are not useful as they
> stand.
> 
> >
> > > I reckon this should be part of the initial DT, as this otherwise
> > > serves little purpose.
> > >
> >
> > Without this initial support, we can't add some base drivers, like
> > mailbox. The dt_binding_check will report warnings/errors [1].
> 
> Of course you can. You just add additional patches to this series,
> making it something that is actually useful. So far, this series only
> serves as marketing material.
> 
> > Full UART support depends on clock, clock control needs mailbox
> > to talk with FW using SCMI protocol.
> 
> Then do it. You obviously have existing DT support for it already.
> 
> > There is no any support for CIX SoC, so we had to add one small step by
> > step.
> 
> No, you are deliberately choosing to make this platform useless.
> 
> That's a bit sad, and a waste of everybody's time.
> 

Hi Marc,

Thanks for your interesting of our platform, and your comments
help us a lot. But I don't think it wastes reviewers and maintainers
time, a clean patch set saves everyone's time during upstream process.

For how to organize the patch set for SoC, Krzysztof gave good summary
at [1]. We are going on upstream [2], this patch set is just a start
and base but not like you said for marketing purpose.

[1] https://lore.kernel.org/linux-samsung-soc/CADrjBPq_0nUYRABKpskRF_dhHu+4K=duPVZX==0pr+cjSL_caQ@mail.gmail.com/T/#m2d9130a1342ab201ab49670fa6c858ee3724c83c
[2] https://lore.kernel.org/lkml/20250325101807.2202758-1-guomin.chen@cixtech.com/

-- 

Best regards,
Peter


  reply	other threads:[~2025-03-27  6:47 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-24  6:24 [PATCH v5 0/6] arm64: Introduce CIX P1 (SKY1) SoC Peter Chen
2025-03-24  6:24 ` [PATCH v5 1/6] dt-bindings: vendor-prefixes: Add CIX Technology Group Co., Ltd Peter Chen
2025-03-24  6:24 ` [PATCH v5 2/6] dt-bindings: arm: add CIX P1 (SKY1) SoC Peter Chen
2025-03-24  6:24 ` [PATCH v5 3/6] arm64: Kconfig: add ARCH_CIX for cix silicons Peter Chen
2025-03-24  6:24 ` [PATCH v5 4/6] arm64: defconfig: Enable CIX SoC Peter Chen
2025-03-24  6:24 ` [PATCH v5 5/6] arm64: dts: cix: add initial CIX P1(SKY1) dts support Peter Chen
2025-03-25 10:52   ` Marc Zyngier
2025-03-26  3:26     ` Peter Chen
2025-03-26  9:12       ` Marc Zyngier
2025-03-27  6:44         ` Peter Chen [this message]
2025-03-27  7:16           ` Krzysztof Kozlowski
2025-03-27  8:18             ` Arnd Bergmann
2025-03-27  9:31               ` Peter Chen
2025-03-27 10:29                 ` Arnd Bergmann
2025-03-27  8:35             ` Peter Chen
2025-03-27  8:40               ` Krzysztof Kozlowski
2025-03-27  9:47                 ` Peter Chen
2025-03-27 13:06                   ` Krzysztof Kozlowski
2025-03-24  6:24 ` [PATCH v5 6/6] MAINTAINERS: Add CIX SoC maintainer entry Peter Chen

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=Z-Tz1moMNozx23k6@nchen-desktop \
    --to=peter.chen@cixtech.com \
    --cc=arnd@arndb.de \
    --cc=catalin.marinas@arm.com \
    --cc=cix-kernel-upstream@cixtech.com \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=fugang.duan@cixtech.com \
    --cc=kajetan.puchalski@arm.com \
    --cc=krzk+dt@kernel.org \
    --cc=krzysztof.kozlowski@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marcin@juszkiewicz.com.pl \
    --cc=maz@kernel.org \
    --cc=robh@kernel.org \
    --cc=soc@kernel.org \
    --cc=will@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;
as well as URLs for NNTP newsgroup(s).