From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mout-p-101.mailbox.org (mout-p-101.mailbox.org [80.241.56.151]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id B1AF84192E3; Fri, 5 Jun 2026 09:33:36 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=80.241.56.151 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1780652019; cv=none; b=RlZsp1WM9eCoD7+oZ+sYIkyqwODHmi/8Z+OMEF8SivxEBy70wP//xP1HEF/NRIzM31BtnW2SFr9glxnXgmyOdSgoX/5fDBqxLw+bkHd3DMQOVEdUBDXtuVqqZJvMjqdlBwS4HTpoW6Lxg3M12vY13ZMt1isIw4l2uToMeVnCpJo= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1780652019; c=relaxed/simple; bh=6bNZUcvnY+5Blv3aY9YAqimAK5AIGlF+H59bfPEl9HE=; h=Mime-Version:Content-Type:Date:Message-Id:Cc:Subject:From:To: References:In-Reply-To; b=VEC5bOvWpm9aG/Y6TnbknvONrHvC0ReWzc35kseQjE0FOENQxif7kSg2HZFFo00oiGdwfhj2VxQWz96ZiyQ84G6SMfaeF7gailIiB2e4VO8vi7wfbzR5o1ZlDMa8wT2GpBQ6KHe1L9Cv8WdUE4mqqC/bselv6w+X6x2/SsS0/Io= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=pass (p=reject dis=none) header.from=mailbox.org; spf=pass smtp.mailfrom=mailbox.org; dkim=pass (2048-bit key) header.d=mailbox.org header.i=@mailbox.org header.b=Qhv75Hp5; arc=none smtp.client-ip=80.241.56.151 Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=reject dis=none) header.from=mailbox.org Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=mailbox.org Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=mailbox.org header.i=@mailbox.org header.b="Qhv75Hp5" Received: from smtp1.mailbox.org (smtp1.mailbox.org [IPv6:2001:67c:2050:b231:465::1]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by mout-p-101.mailbox.org (Postfix) with ESMTPS id 4gWx7x26TDz9twd; Fri, 5 Jun 2026 11:33:33 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mailbox.org; s=mail20150812; t=1780652013; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=3QhLZZ7DF5RQcecWKZHROUBnz5EbLkvAFAJ8ZXow1xg=; b=Qhv75Hp5L7mhw4yvb9CtlBJWQgGZJ0hczOCA7bUsBW/xavDLSqRI3Qtd59VcpkyZZFFIoN 5TGJRbhXsiwhimVe/mfUqrhxDaFSgzCOVRkdqM2kjFVZ7jYr+0+z0bpIl3yGVymhPmnyUF XIr4fx10cX6eAV5tV1JWJgxH8K3C+2BWVoRCJMvdi8XkQuWeaDCRaLlykuTQrnGRn1u2xt 3OCykKdhQHhxmyKt34pr2R74/42tMYdGQl1jpFLbq2BQknDp2eZMp8u+rq4lw28Av9X8Zc 8LUGDogh3C/U5JE0pg3ZCw5PWyREMgacDMsfWbxIuE2B2awLPQVSrDScA3AO7g== Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: Mime-Version: 1.0 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=UTF-8 Date: Fri, 05 Jun 2026 17:33:23 +0800 Message-Id: Cc: , , , , , , "linux-riscv" Subject: Re: [PATCH v5 RESEND 4/5] riscv64: dts: sophgo: add SG2000 dtsi From: "Shuwei Wu" To: "Joshua Milas" , , , , , , , , , , , , , , , , , , References: <20260530173347.33533-1-josh.milas@gmail.com> <20260530173347.33533-5-josh.milas@gmail.com> In-Reply-To: <20260530173347.33533-5-josh.milas@gmail.com> X-MBO-RS-META: cnakhfhm6eenn8abomp48ddt71ztasak X-MBO-RS-ID: e6d4df9cfa9ec01b400 Hi Joshua, On Sun May 31, 2026 at 1:33 AM CST, Joshua Milas wrote: > Adds sg2000.dtsi on the RISCV side. > > Signed-off-by: Joshua Milas > --- > arch/riscv/boot/dts/sophgo/sg2000.dtsi | 53 ++++++++++++++++++++++++++ > 1 file changed, 53 insertions(+) > create mode 100644 arch/riscv/boot/dts/sophgo/sg2000.dtsi > > diff --git a/arch/riscv/boot/dts/sophgo/sg2000.dtsi b/arch/riscv/boot/dts= /sophgo/sg2000.dtsi > new file mode 100644 > index 0000000000000..412adacc00576 > --- /dev/null > +++ b/arch/riscv/boot/dts/sophgo/sg2000.dtsi > @@ -0,0 +1,53 @@ > +// SPDX-License-Identifier: (GPL-2.0 OR MIT) > + > +#define SOC_PERIPHERAL_IRQ(nr) ((nr) + 16) > + > +#include > +#include > +#include "cv180x-cpus.dtsi" > +#include "cv180x.dtsi" > +#include "cv181x.dtsi" > + > +/ { > + compatible =3D "sophgo,sg2000"; > + > + memory@80000000 { > + device_type =3D "memory"; > + reg =3D <0x80000000 0x10000000>; > + }; I noticed that this describes 256 MiB of RAM. The Milk-V Duo documentation = lists the SG2000-based Duo boards as having 512 MB of DRAM [1]. Is the 256 MiB size intentional here, or should the Duo S board DTS overrid= e it with the documented 512 MB DRAM size? [1] https://milkv.io/docs/duo/overview > + > + soc { > + interrupt-parent =3D <&plic>; > + dma-noncoherent; > + > + pinctrl: pinctrl@3001000 { > + compatible =3D "sophgo,sg2000-pinctrl"; > + reg =3D <0x03001000 0x1000>, > + <0x05027000 0x1000>; > + reg-names =3D "sys", "rtc"; > + }; > + > + clk: clock-controller@3002000 { > + compatible =3D "sophgo,sg2000-clk"; > + reg =3D <0x03002000 0x1000>; > + clocks =3D <&osc>; > + #clock-cells =3D <1>; > + }; > + > + plic: interrupt-controller@70000000 { > + compatible =3D "sophgo,sg2000-plic", "thead,c900-plic"; > + reg =3D <0x70000000 0x4000000>; > + interrupts-extended =3D <&cpu0_intc 11>, <&cpu0_intc 9>; > + interrupt-controller; > + #address-cells =3D <0>; > + #interrupt-cells =3D <2>; > + riscv,ndev =3D <101>; > + }; > + > + clint: timer@74000000 { > + compatible =3D "sophgo,sg2000-clint", "thead,c900-clint"; > + reg =3D <0x74000000 0x10000>; > + interrupts-extended =3D <&cpu0_intc 3>, <&cpu0_intc 7>; > + }; > + }; > +}; --=20 Best regards, Shuwei Wu