linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: jszhang@marvell.com (Jisheng Zhang)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 5/5] arm64: marvell: add Device Tree files for Armada 7K/8K
Date: Wed, 17 Feb 2016 10:21:24 +0800	[thread overview]
Message-ID: <20160217102124.7353591f@xhacker> (raw)
In-Reply-To: <20160216173840.7f93896f@free-electrons.com>

Dear Thomas,

On Tue, 16 Feb 2016 17:38:40 +0100 Thomas Petazzoni wrote:

> Hello,
> 
> On Tue, 16 Feb 2016 13:42:19 +0800, Jisheng Zhang wrote:
> 
> > > +/ {
> > > +	model = "Marvell Armada AP806";
> > > +	compatible = "marvell,armada-ap806";
> > > +	#address-cells = <2>;
> > > +	#size-cells = <2>;
> > > +
> > > +	psci {
> > > +		compatible = "arm,psci-0.2";  
> > 
> > I guess the firmware is also psci-1.0 compatible.  
> 
> At boot time, the kernel queries the PSCI firmware, and it says:
> 
> [    0.000000] psci: probing for conduit method from DT.
> [    0.000000] psci: PSCIv0.2 detected in firmware.
> [    0.000000] psci: Using standard PSCI v0.2 function IDs
> 
> So I think psci-0.2 is correct here. Should this change for the
> production revision of the chip, we'll send an update to the Device
> Tree accordingly.

Thanks for the information.

> 
> > > +	ap806 {
> > > +		#address-cells = <2>;
> > > +		#size-cells = <2>;
> > > +		compatible = "simple-bus";
> > > +		interrupt-parent = <&gic>;
> > > +		ranges;
> > > +
> > > +		config-space {
> > > +			#address-cells = <1>;
> > > +			#size-cells = <1>;
> > > +			compatible = "simple-bus";
> > > +			ranges = <0x0 0x0 0xf0000000 0x1000000>;
> > > +
> > > +			gic: interrupt-controller at 210000 {
> > > +				compatible = "arm,cortex-a15-gic",
> > > +					     "arm,cortex-a9-gic";  
> > 
> > I guess the GIC is neither the one in cortex-a15 or cortex-a9.   
> 
> What makes you think this?
> 
> The GIC is a GIC400, which is GICv2 compliant, and arm-cortex-a15-gic /

That's my point, why not "gic-400" explicitly?

Thanks,
Jisheng

> arm-cortex-a9-gic are valid compatible strings to identify a GICv2
> compliant interrupt controller.
> 
> See:
> 
> arch/arm64/boot/dts/altera/socfpga_stratix10.dtsi:              compatible = "arm,gic-400", "arm,cortex-a15-gic";
> arch/arm64/boot/dts/amd/amd-seattle-soc.dtsi:           compatible = "arm,gic-400", "arm,cortex-a15-gic";
> arch/arm64/boot/dts/apm/apm-shadowcat.dtsi:             compatible = "arm,cortex-a15-gic";
> arch/arm64/boot/dts/apm/apm-storm.dtsi:         compatible = "arm,cortex-a15-gic";
> arch/arm64/boot/dts/arm/foundation-v8.dts:              compatible = "arm,cortex-a15-gic", "arm,cortex-a9-gic";
> arch/arm64/boot/dts/arm/juno-base.dtsi:         compatible = "arm,gic-400", "arm,cortex-a15-gic";
> arch/arm64/boot/dts/arm/rtsm_ve-aemv8a.dts:             compatible = "arm,cortex-a15-gic", "arm,cortex-a9-gic";
> arch/arm64/boot/dts/marvell/armada-ap806.dtsi:                          compatible = "arm,cortex-a15-gic",
> arch/arm64/boot/dts/nvidia/tegra132.dtsi:               compatible = "arm,cortex-a15-gic";
> arch/arm64/boot/dts/xilinx/zynqmp.dtsi:                 compatible = "arm,gic-400", "arm,cortex-a15-gic";
> 
> Or do you have a more specific reason to think that this compatible
> string is wrong?
> 
> Best regards,
> 
> Thomas

  reply	other threads:[~2016-02-17  2:21 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-15  8:47 [PATCH 0/5] arm64: Initial support for Marvell Armada 7K/8K Thomas Petazzoni
2016-02-15  8:47 ` [PATCH 1/5] Documentation: arm: improve Armada 37xx description Thomas Petazzoni
2016-02-15  8:47 ` [PATCH 2/5] Documentation: arm: add Marvell Armada 7K and 8K families Thomas Petazzoni
2016-02-15  8:47 ` [PATCH 3/5] Documentation: arm: improve Marvell EBU Armada documentation Thomas Petazzoni
2016-02-15  8:47 ` [PATCH 4/5] arm64: update ARCH_MVEBU for Marvell Armada 7K/8K support Thomas Petazzoni
2016-02-15  8:47 ` [PATCH 5/5] arm64: marvell: add Device Tree files for Armada 7K/8K Thomas Petazzoni
2016-02-15  9:32   ` Marc Zyngier
2016-02-16 16:31     ` Thomas Petazzoni
2016-02-16 17:06       ` Marc Zyngier
2016-02-17 14:06         ` Thomas Petazzoni
2016-02-16  5:42   ` Jisheng Zhang
2016-02-16 16:38     ` Thomas Petazzoni
2016-02-17  2:21       ` Jisheng Zhang [this message]
2016-02-17  8:30         ` Thomas Petazzoni
2016-02-15  9:24 ` [PATCH 0/5] arm64: Initial support for Marvell " Arnd Bergmann
2016-02-15  9:37   ` Thomas Petazzoni
2016-02-15  9:42     ` Arnd Bergmann
2016-02-15  9:26 ` [PATCH] ARM: documentation: update Marvell product listing 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=20160217102124.7353591f@xhacker \
    --to=jszhang@marvell.com \
    --cc=linux-arm-kernel@lists.infradead.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).