public inbox for linux-riscv@lists.infradead.org
 help / color / mirror / Atom feed
From: Yixun Lan <dlan@gentoo.org>
To: Jisheng Zhang <jszhang@kernel.org>
Cc: Rob Herring <robh@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>,
	Conor Dooley <conor@kernel.org>,
	Paul Walmsley <paul.walmsley@sifive.com>,
	Palmer Dabbelt <palmer@dabbelt.com>,
	Albert Ou <aou@eecs.berkeley.edu>,
	Daniel Lezcano <daniel.lezcano@linaro.org>,
	Thomas Gleixner <tglx@linutronix.de>,
	Samuel Holland <samuel.holland@sifive.com>,
	Anup Patel <anup@brainfault.org>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Jiri Slaby <jirislaby@kernel.org>,
	Lubomir Rintel <lkundrak@v3.sk>,
	devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
	Yangyu Chen <cyy@cyyself.name>,
	Conor Dooley <conor.dooley@microchip.com>,
	Inochi Amaoto <inochiama@outlook.com>,
	linux-serial@vger.kernel.org, linux-riscv@lists.infradead.org,
	Meng Zhang <zhangmeng.kevin@spacemit.com>
Subject: Re: [PATCH v3 06/11] dt-bindings: serial: 8250: Add SpacemiT K1 uart compatible
Date: Fri, 5 Jul 2024 06:47:21 +0000	[thread overview]
Message-ID: <20240705064721.GB3042186@ofsar> (raw)
In-Reply-To: <ZoarsYMNJRu1-_wn@xhacker>


On 22:03 Thu 04 Jul     , Jisheng Zhang wrote:
> On Wed, Jul 03, 2024 at 02:55:09PM +0000, Yixun Lan wrote:
> > Found SpacemiT's K1 uart controller is compatible with
> > Intel's Xscale uart, but it's still worth to introduce a new compatible.
> 
> Per vendor's kernel source code, all the uarts support 64Bytes FIFO.
> So if it's compatible with Xscale, it's a xscale uart 64 Bytes FIFO.
yes, I agree

further question would how to implement specific support for spacemit's k1 SoC
one possible option to add a PORT_SPACEMIT compatible data to 8250_port.c - uart_config[]


> >From this PoV, the uart isn't a Xscale but a mrvl pxa.
see my previous comment, probably need further clarification/investigation..

> 
> But I have one question: is the uart really a mrvl/intel pxa uart? or is just
No, I'm unable to answer this, I'm not an employee of SpacemiT
All informations are based on public available source + docs..

> reg programming compatible with pxa?
> 
To my knowledge, it's compatible with pxa, but it would be great that vendor can clarify this

> > 
> > Acked-by: Conor Dooley <conor.dooley@microchip.com>
> > Signed-off-by: Yixun Lan <dlan@gentoo.org>
> > ---
> >  Documentation/devicetree/bindings/serial/8250.yaml | 4 +++-
> >  1 file changed, 3 insertions(+), 1 deletion(-)
> > 
> > diff --git a/Documentation/devicetree/bindings/serial/8250.yaml b/Documentation/devicetree/bindings/serial/8250.yaml
> > index 692aa05500fd5..0bde2379e8647 100644
> > --- a/Documentation/devicetree/bindings/serial/8250.yaml
> > +++ b/Documentation/devicetree/bindings/serial/8250.yaml
> > @@ -111,7 +111,9 @@ properties:
> >                - mediatek,mt7623-btif
> >            - const: mediatek,mtk-btif
> >        - items:
> > -          - const: mrvl,mmp-uart
> > +          - enum:
> > +              - mrvl,mmp-uart
> > +              - spacemit,k1-uart
> >            - const: intel,xscale-uart
> >        - items:
> >            - enum:
> > 
> > -- 
> > 2.45.2
> > 
> > 
> > _______________________________________________
> > linux-riscv mailing list
> > linux-riscv@lists.infradead.org
> > http://lists.infradead.org/mailman/listinfo/linux-riscv

-- 
Yixun Lan (dlan)
Gentoo Linux Developer
GPG Key ID AABEFD55

_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv

  reply	other threads:[~2024-07-05  6:47 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-03 14:55 [PATCH v3 00/11] riscv: add initial support for SpacemiT K1 Yixun Lan
2024-07-03 14:55 ` [PATCH v3 01/11] dt-bindings: vendor-prefixes: add spacemit Yixun Lan
2024-07-03 14:55 ` [PATCH v3 02/11] dt-bindings: riscv: Add SpacemiT X60 compatibles Yixun Lan
2024-07-03 14:55 ` [PATCH v3 03/11] dt-bindings: riscv: add SpacemiT K1 bindings Yixun Lan
2024-07-03 16:35   ` Matthias Brugger
2024-07-03 14:55 ` [PATCH v3 04/11] dt-bindings: timer: Add SpacemiT K1 CLINT Yixun Lan
2024-07-03 14:55 ` [PATCH v3 05/11] dt-bindings: interrupt-controller: Add SpacemiT K1 PLIC Yixun Lan
2024-07-03 16:00   ` Conor Dooley
2024-07-03 14:55 ` [PATCH v3 06/11] dt-bindings: serial: 8250: Add SpacemiT K1 uart compatible Yixun Lan
2024-07-04 14:03   ` Jisheng Zhang
2024-07-05  6:47     ` Yixun Lan [this message]
2024-07-06  8:02       ` 张猛
2024-07-06  8:05         ` Greg Kroah-Hartman
2024-07-03 14:55 ` [PATCH v3 07/11] riscv: add SpacemiT SoC family Kconfig support Yixun Lan
2024-07-03 14:55 ` [PATCH v3 08/11] riscv: dts: add initial SpacemiT K1 SoC device tree Yixun Lan
2024-07-04  1:17   ` Jesse Taube
2024-07-04 11:39     ` Yixun Lan
2024-07-04 13:46   ` Jisheng Zhang
2024-07-04 14:18     ` Jisheng Zhang
2024-07-05  6:38     ` Yixun Lan
2024-07-06  4:12       ` Jisheng Zhang
2024-07-06  5:05         ` Yixun Lan
2024-07-06 10:40           ` Jisheng Zhang
2024-07-06 14:24             ` Yixun Lan
2024-07-08 12:31               ` Jisheng Zhang
2024-07-05  5:55   ` 张猛
2024-07-05  6:28     ` Conor Dooley
2024-07-03 14:55 ` [PATCH v3 09/11] riscv: dts: spacemit: add Banana Pi BPI-F3 board " Yixun Lan
2024-07-03 14:55 ` [PATCH v3 10/11] riscv: defconfig: enable SpacemiT SoC Yixun Lan
2024-07-04  0:48   ` Jesse Taube
2024-07-03 14:55 ` [PATCH v3 11/11] riscv: dts: spacemit: add uart1 node for K1 SoC Yixun Lan
2024-07-04 14:05   ` Jisheng Zhang
2024-07-05  6:49     ` Yixun Lan

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=20240705064721.GB3042186@ofsar \
    --to=dlan@gentoo.org \
    --cc=anup@brainfault.org \
    --cc=aou@eecs.berkeley.edu \
    --cc=conor+dt@kernel.org \
    --cc=conor.dooley@microchip.com \
    --cc=conor@kernel.org \
    --cc=cyy@cyyself.name \
    --cc=daniel.lezcano@linaro.org \
    --cc=devicetree@vger.kernel.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=inochiama@outlook.com \
    --cc=jirislaby@kernel.org \
    --cc=jszhang@kernel.org \
    --cc=krzk+dt@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-riscv@lists.infradead.org \
    --cc=linux-serial@vger.kernel.org \
    --cc=lkundrak@v3.sk \
    --cc=palmer@dabbelt.com \
    --cc=paul.walmsley@sifive.com \
    --cc=robh@kernel.org \
    --cc=samuel.holland@sifive.com \
    --cc=tglx@linutronix.de \
    --cc=zhangmeng.kevin@spacemit.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