linux-mips.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Paul Burton <paul.burton@mips.com>
To: Alexandre GRIVEAUX <agriveaux@deutnet.info>
Cc: "robh+dt@kernel.org" <robh+dt@kernel.org>,
	"mark.rutland@arm.com" <mark.rutland@arm.com>,
	"ralf@linux-mips.org" <ralf@linux-mips.org>,
	"jhogan@kernel.org" <jhogan@kernel.org>,
	"linux-mips@vger.kernel.org" <linux-mips@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>
Subject: Re: [PATCH v2 5/5] MIPS: JZ4780: DTS: Add CPU nodes
Date: Tue, 1 Oct 2019 23:20:33 +0000	[thread overview]
Message-ID: <20191001232031.qaci6hk5tjo652mi@pburton-laptop> (raw)
In-Reply-To: <0dbd1986be4ee50bdd9f45c140aded7c49fddb8a.1569955865.git.agriveaux@deutnet.info>

Hi Alexandre,

On Tue, Oct 01, 2019 at 09:09:48PM +0200, Alexandre GRIVEAUX wrote:
> The JZ4780 have 2 core, adding to DT.
> 
> Signed-off-by: Alexandre GRIVEAUX <agriveaux@deutnet.info>
> ---
>  arch/mips/boot/dts/ingenic/jz4780.dtsi | 17 +++++++++++++++++
>  1 file changed, 17 insertions(+)
> 
> diff --git a/arch/mips/boot/dts/ingenic/jz4780.dtsi b/arch/mips/boot/dts/ingenic/jz4780.dtsi
> index f928329b034b..9c7346724f1f 100644
> --- a/arch/mips/boot/dts/ingenic/jz4780.dtsi
> +++ b/arch/mips/boot/dts/ingenic/jz4780.dtsi
> @@ -7,6 +7,23 @@
>  	#size-cells = <1>;
>  	compatible = "ingenic,jz4780";
>  
> +	cpus {
> +		#address-cells = <1>;
> +		#size-cells = <0>;
> +
> +		cpu@0 {
> +			compatible = "ingenic,jz4780";

This should probably be something like ingenic,xburst2. JZ4780 is the
SoC. It also should be a documented binding, but I think it would be
worth holding off on the whole thing until we actually get SMP support
merged - just in case we come up with a binding that doesn't actually
work out.

So I expect I'll just apply patches 1-4 for now.

Thanks for working on it!

    Paul

> +			device_type = "cpu";
> +			reg = <0>;
> +		};
> +
> +		cpu@1 {
> +			compatible = "ingenic,jz4780";
> +			device_type = "cpu";
> +			reg = <1>;
> +		};
> +	};
> +
>  	cpuintc: interrupt-controller {
>  		#address-cells = <0>;
>  		#interrupt-cells = <1>;
> -- 
> 2.20.1
> 

  reply	other threads:[~2019-10-01 23:20 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-01 19:08 [PATCH v2 0/5] MIPS: CI20: DTS: Add nodes to Creator CI20 board Alexandre GRIVEAUX
2019-10-01 19:08 ` [PATCH v2 1/5] MIPS: JZ4780: DTS: Add I2C nodes Alexandre GRIVEAUX
2019-10-07 17:53   ` Paul Burton
2019-10-01 19:09 ` [PATCH v2 2/5] MIPS: CI20: " Alexandre GRIVEAUX
2019-10-07 17:53   ` Paul Burton
2019-10-01 19:09 ` [PATCH v2 3/5] MIPS: CI20: DTS: Add IW8103 Wifi + bluetooth Alexandre GRIVEAUX
2019-10-07 17:53   ` Paul Burton
2019-10-01 19:09 ` [PATCH v2 4/5] MIPS: CI20: DTS: Add Leds Alexandre GRIVEAUX
2019-10-07 17:53   ` Paul Burton
2019-10-01 19:09 ` [PATCH v2 5/5] MIPS: JZ4780: DTS: Add CPU nodes Alexandre GRIVEAUX
2019-10-01 23:20   ` Paul Burton [this message]
2019-10-02 19:07     ` Alexandre GRIVEAUX

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=20191001232031.qaci6hk5tjo652mi@pburton-laptop \
    --to=paul.burton@mips.com \
    --cc=agriveaux@deutnet.info \
    --cc=devicetree@vger.kernel.org \
    --cc=jhogan@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mips@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=ralf@linux-mips.org \
    --cc=robh+dt@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).