public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: arnd@arndb.de (Arnd Bergmann)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 2/6] arm64: Add DTS support for Spreadtrum's Shark64 SoC
Date: Mon, 29 Sep 2014 15:47:47 +0200	[thread overview]
Message-ID: <4004425.NZAxCnE0qr@wuerfel> (raw)
In-Reply-To: <1411992293-7729-3-git-send-email-zhang.lyra@gmail.com>

On Monday 29 September 2014 20:04:49 zhang.lyra at gmail.com wrote:
> +
> +/memreserve/ 0x80000000 0x00010000;

Maybe add a comment explaining why it is reserved?

> +	chosen {
> +		bootargs = "earlycon=serial_sprd,0x70000000";
> +      };

Just remove this for now, the command line should really be set by the
boot loader, not hardcoded in the dts file.

IIRC, the earlycon=... syntax is not recommended on DT based systems,
better use the "stdout-path" syntax instead.

> +	cpus {
> +		#address-cells = <2>;
> +		#size-cells = <0>;
> +
> +		cpu at 0 {
> +			device_type = "cpu";
> +			compatible = "arm,armv8";
> +			reg = <0x0 0x0>;
> +			enable-method = "spin-table";
> +			cpu-release-addr = <0x0 0x8000fff8>;
> +		};

New platforms should avoid using "spin-table" method. Please
change the boot loader to implement PSCI if you can.

> +	memory at 80000000 {
> +		device_type = "memory";
> +		reg = <0 0x80000000 0 0x20000000>;
> +	};
> +
> +	aliases {
> +		serial0 = &uart0;
> +		serial1 = &uart1;
> +	};

These two belong into a board-specific file. I'd suggest renaming this
file to sprd_shark64.dtsi (or whatever the SoC is called) and adding a
.dts file that includes this and sets the aliases and memory node
according to what the particular board has.

> +	intc:interrupt-controller at 71400000 {
> +		compatible = "sprd,intc";
> +		#interrupt-cells = <0>;
> +		interrupt-controller;
> +		reg =	<0 0x71400000 0 0x1000>,
> +			<0 0x71500000 0 0x1000>,
> +			<0 0x71600000 0 0x1000>,
> +			<0 0x71700000 0 0x1000>;
> +	};

This interrupt controller does not have a binding, so please add at least
a documentation for the binding as well. The name should probably be more
specific that this. Also, explain why you have an interrupt controller
that has four memory regions but only one interrupt sink but no interrupt
source.

I assume this is a nested interrupt controller to which some internal
peripherals are connected?

> +	uart0: uart at 70000000 {
> +		compatible = "sprd,serial";
> +		reg = <0 0x70000000 0 0x100>;
> +		interrupts = <0 2 0xf04>;
> +	};
> +
> +	uart1: uart at 70100000 {
> +		compatible = "sprd,serial";
> +		reg = <0 0x70100000 0 0x100>;
> +		interrupts = <0 3 0xf04>;
> +	};

Please rename these to serial at 70000000. Like the interrupt controller,
it would be good to have a more specific compatible string.
You may want to add a status="disabled" property in both these
nodes, and override them from the board.dts file for the ports that
are actually available.

	Arnd

  reply	other threads:[~2014-09-29 13:47 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-29 12:04 [PATCH 0/6] Add Spreadtrum Shark64 SoC support zhang.lyra at gmail.com
2014-09-29 12:04 ` [PATCH 1/6] Documentation: DT: Add bindings for Spreadtrum serial zhang.lyra at gmail.com
2014-09-29 13:39   ` Arnd Bergmann
2014-10-01 11:21   ` Mark Rutland
2014-10-02 15:08     ` Orson Zhai
2014-09-29 12:04 ` [PATCH 2/6] arm64: Add DTS support for Spreadtrum's Shark64 SoC zhang.lyra at gmail.com
2014-09-29 13:47   ` Arnd Bergmann [this message]
2014-10-01 11:17     ` Catalin Marinas
2014-10-15  3:17     ` Lyra Zhang
2014-10-20 19:00       ` Arnd Bergmann
2014-10-21  1:28         ` Lyra Zhang
2014-10-01 11:23   ` Mark Rutland
2014-09-29 12:04 ` [PATCH 3/6] arm64: dts/Makefile: Add " zhang.lyra at gmail.com
2014-09-29 14:47   ` Mark Brown
2014-09-30  9:51     ` Lyra Zhang
2014-09-29 12:04 ` [PATCH 4/6] arm64: Add support for Spreadtrum's Shark64 SoC in Kconfig and defconfig zhang.lyra at gmail.com
2014-09-29 12:04 ` [PATCH 5/6] tty/serial: Add Spreadtrum's serial earlycon zhang.lyra at gmail.com
2014-09-29 13:36   ` Arnd Bergmann
2014-10-01 13:55     ` Rob Herring
2014-09-29 14:53   ` Mark Brown
2014-09-29 12:04 ` [PATCH 6/6] Documentation: Add entry for Spreadtrum's Shark64 SoC zhang.lyra at gmail.com
2014-09-29 13:30   ` Arnd Bergmann
2014-09-29 13:59   ` Arnd Bergmann
2014-09-30 10:08     ` Lyra Zhang
2014-09-29 14:08 ` [PATCH 0/6] Add Spreadtrum Shark64 SoC support Arnd Bergmann
  -- strict thread matches above, loose matches on Subject: below --
2014-09-29 11:48 zhang.lyra at gmail.com
2014-09-29 11:48 ` [PATCH 2/6] arm64: Add DTS support for Spreadtrum's Shark64 SoC zhang.lyra at gmail.com
2014-09-29 14:55   ` Andreas Färber

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=4004425.NZAxCnE0qr@wuerfel \
    --to=arnd@arndb.de \
    --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