From: mark.rutland@arm.com (Mark Rutland)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v5 05/11] ARM: dts: add imx7d soc dtsi file
Date: Tue, 21 Apr 2015 18:28:34 +0100 [thread overview]
Message-ID: <20150421172834.GF10164@leverpostej> (raw)
In-Reply-To: <1429628007-8892-6-git-send-email-Frank.Li@freescale.com>
> +/*
> + cpu1: cpu at 1 {
> + compatible = "arm,cortex-a7";
> + device_type = "cpu";
> + reg = <1>;
> + };
> +*/
Why have it commented out? If it's not available, leave it out entirely.
> + intc: interrupt-controller at 31001000 {
> + compatible = "arm,cortex-a7-gic";
> + #interrupt-cells = <3>;
> + interrupt-controller;
> + reg = <0x31001000 0x1000>,
> + <0x31002000 0x100>;
> + };
GICC should be larger than 0x100 bytes.
What about GICH, GICV?
What state do CPUs enter the kernel?
> +
> + clocks {
> + #address-cells = <1>;
> + #size-cells = <0>;
> +
> + ckil: clock at 0 {
> + compatible = "fixed-clock";
> + reg = <0>;
> + #clock-cells = <0>;
> + clock-frequency = <32768>;
> + clock-output-names = "ckil";
> + };
> +
> + osc: clock at 1 {
> + compatible = "fixed-clock";
> + reg = <1>;
> + #clock-cells = <0>;
> + clock-frequency = <24000000>;
> + clock-output-names = "osc";
> + };
> +
> + };
Get rid of the clocks container node, and put these under the root.
> +
> + timer {
> + compatible = "arm,armv7-timer";
> + arm,cpu-registers-not-fw-configured;
This was bad enough the first time...
> + interrupts = <GIC_PPI 13
> + (GIC_CPU_MASK_SIMPLE(4) | IRQ_TYPE_LEVEL_LOW)>,
> + <GIC_PPI 14
> + (GIC_CPU_MASK_SIMPLE(4) | IRQ_TYPE_LEVEL_LOW)>;
Two interrupts are missing.
> + interrupt-parent = <&intc>;
> + clock-frequency = <8000000>;
Why isn't this programmed?
> + };
> +
> + soc {
> + #address-cells = <1>;
> + #size-cells = <1>;
> + compatible = "simple-bus";
> + interrupt-parent = <&intc>;
> + ranges;
> +
> + pmu {
> + compatible = "arm,cortex-a7-pmu";
> + interrupts = <GIC_SPI 92 IRQ_TYPE_LEVEL_HIGH>;
> + status = "disabled";
> + };
Move this under the root. It doesn't live on an SoC-specific bus.
Why disabled?
Thanks,
Mark.
next prev parent reply other threads:[~2015-04-21 17:28 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-21 14:53 [PATCH v5 00/11] Add Freescale i.mx7d support Frank.Li at freescale.com
2015-04-21 14:53 ` [PATCH v5 01/11] ARM: dts: add pinfunc include file to support imx7d Frank.Li at freescale.com
2015-04-21 14:53 ` [PATCH v5 02/11] ARM: dts: add pinfunc include file gpio1 " Frank.Li at freescale.com
2015-04-21 14:53 ` [PATCH v5 03/11] ARM: dts: add clock include file " Frank.Li at freescale.com
2015-04-21 14:53 ` [PATCH v5 04/11] Document: dt: binding: imx: update document for imx7d support Frank.Li at freescale.com
2015-04-21 14:53 ` [PATCH v5 05/11] ARM: dts: add imx7d soc dtsi file Frank.Li at freescale.com
2015-04-21 17:28 ` Mark Rutland [this message]
2015-04-21 18:48 ` Zhi Li
2015-04-21 19:34 ` Zhi Li
2015-04-22 9:12 ` Mark Rutland
2015-04-22 14:08 ` Zhi Li
2015-04-21 14:53 ` [PATCH v5 06/11] pinctrl: add imx7d support Frank.Li at freescale.com
2015-04-21 14:53 ` [PATCH v5 07/11] ARM: imx: add msl support for imx7d Frank.Li at freescale.com
2015-04-21 15:12 ` Russell King - ARM Linux
2015-04-21 15:19 ` Zhi Li
2015-04-21 17:31 ` Mark Rutland
2015-04-21 18:51 ` Zhi Li
2015-04-21 20:22 ` Rob Herring
2015-04-21 20:37 ` Zhi Li
2015-04-21 14:53 ` [PATCH v5 08/11] ARM: imx: add gpt system timer " Frank.Li at freescale.com
2015-04-21 20:25 ` Rob Herring
2015-04-21 14:53 ` [PATCH v5 09/11] ARM: imx: add imx7d clk tree support Frank.Li at freescale.com
2015-04-21 20:30 ` Rob Herring
2015-04-21 20:39 ` Zhi Li
2015-04-21 20:47 ` Rob Herring
2015-04-21 20:51 ` Zhi Li
2015-04-24 8:28 ` Shawn Guo
2015-04-21 14:53 ` [PATCH v5 10/11] arm: dts: add imx7d-sdb support Frank.Li at freescale.com
2015-04-21 14:53 ` [PATCH v5 11/11] ARM: config: imx_v6_v7_defconfig add imx7d support Frank.Li at freescale.com
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=20150421172834.GF10164@leverpostej \
--to=mark.rutland@arm.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