mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Arnd Bergmann <arnd@arndb.de>
To: Neil Zhang <zhangwm@marvell.com>
Cc: grant.likely@linaro.org, haojian.zhuang@gmail.com,
	devicetree-discuss@lists.ozlabs.org,
	linux-kernel@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org,
	Chao Xie <chao.xie@marvell.com>
Subject: Re: [PATCH V3 3/3] ARM: mmp: bring up pxa988 with device tree support
Date: Wed, 10 Jul 2013 00:05:21 +0200	[thread overview]
Message-ID: <201307100005.21769.arnd@arndb.de> (raw)
In-Reply-To: <1373352166-10064-4-git-send-email-zhangwm@marvell.com>

On Tuesday 09 July 2013, Neil Zhang wrote:
> +	soc {
> +		compatible = "simple-bus";
> +		#address-cells = <1>;
> +		#size-cells = <1>;
> +		interrupt-parent = <&gic>;
> +		ranges;
> +
> +		gic: interrupt-controller@d1dfe100 {
> +			compatible = "arm,cortex-a9-gic";
> +			#interrupt-cells = <3>;
> +			#address-cells = <1>;
> +			interrupt-controller;
> +			reg = <0xd1dff000 0x1000>,
> +			      <0xd1dfe100 0x0100>;
> +		};
> +
> +		L2: l2-cache-controller@d1dfb000 {
> +			compatible = "arm,pl310-cache";
> +			reg = <0xd1dfb000 0x1000>;
> +			arm,data-latency = <2 1 1>;
> +			arm,tag-latency = <2 1 1>;
> +			arm,pwr-dynamic-clk-gating;
> +			arm,pwr-standby-mode;
> +			cache-unified;
> +			cache-level = <2>;
> +		};
> +
> +		local-timer@d1dfe600 {
> +			compatible = "arm,cortex-a9-twd-timer";
> +			reg = <0xd1dfe600 0x20>;
> +			interrupts = <1 13 0x304>;
> +		};
> +
> +		axi@d4200000 {	/* AXI */
> +			compatible = "simple-bus";
> +			#address-cells = <1>;
> +			#size-cells = <1>;
> +			ranges = <0xd4200000 0xd4200000 0x00200000>;
> +
> +			intc: wakeupgen@d4282000 {
> +				compatible = "marvell,mmp-intc";
> +				reg = <0xd4282000 0x1000>;
> +				marvell,intc-wakeup = <0x114 0x3
> +						    0x144 0x3>;
> +			};
> +		};

I am guessing that the structure does not actually reflect the hardware.

Shouldn't AXI be the top-level bus, with the other stuff under it?

> +
> +
> +			uart1: uart@d4017000 {
> +				compatible = "marvell,mmp-uart";
> +				reg = <0xd4017000 0x1000>;
> +				interrupts = <0 27 0x4>;
> +				status = "disabled";
> +			};

The uart node should be called "serial@d4017000" instead of "uart@d4017000".

> diff --git a/arch/arm/mach-mmp/reset.c b/arch/arm/mach-mmp/reset.c
> new file mode 100644
> index 0000000..b90ec54
> --- /dev/null
> +++ b/arch/arm/mach-mmp/reset.c
> @@ -0,0 +1,66 @@
> +/*
> + * linux/arch/arm/mach-mmp/reset.c

I think this could just be part of the smp.c file.

> + *
> + * Author:	Neil Zhang <zhangwm@marvell.com>
> + * Copyright:	(C) 2012 Marvell International Ltd.
> + *
> + * This program is free software; you can redistribute it and/or modify
> + * it under the terms of the GNU General Public License as published by
> + * the Free Software Foundation; either version 2 of the License, or
> + * (at your option) any later version.
> + */
> +
> +#include <linux/kernel.h>
> +#include <linux/smp.h>
> +
> +#include <asm/io.h>
> +#include <asm/cacheflush.h>
> +#include <asm/mach/map.h>
> +
> +#include <mach/addr-map.h>
> +
> +#include "reset.h"
> +
> +#define PMU_CC2_AP			APMU_REG(0x0100)
> +#define CIU_CA9_WARM_RESET_VECTOR	CIU_REG(0x00d8)

You should not hardcode the addresses here, better find them from the device tree.
> +
> +#define CPU_CORE_RST(n)	(1 << ((n) * 4 + 16))
> +#define CPU_DBG_RST(n)	(1 << ((n) * 4 + 18))
> +#define CPU_WDOG_RST(n)	(1 << ((n) * 4 + 19))

This should probably go into a reset controller driver, in drivers/reset/

	Arnd

  reply	other threads:[~2013-07-09 22:05 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-09  6:42 [PATCH V3 0/3] bring up pxa988 with DT Neil Zhang
2013-07-09  6:42 ` [PATCH V3 1/3] dts: change Marvell prefix to 'marvell' Neil Zhang
2013-07-09 12:49   ` Jason Cooper
2013-07-10  7:25     ` Neil Zhang
2013-07-10 12:20       ` Jason Cooper
2013-07-10 14:41         ` Daniel Drake
2013-07-10  8:19     ` Haojian Zhuang
2013-07-10 12:24       ` Jason Cooper
2013-07-10 14:08         ` Haojian Zhuang
2013-07-10 21:50           ` Jason Cooper
2013-07-11 23:54             ` Haojian Zhuang
2013-07-12 15:10               ` Daniel Drake
2013-07-12 15:57                 ` Jason Cooper
2013-07-12 16:05                   ` Daniel Drake
2013-07-12 16:14                     ` Jason Cooper
2013-07-13  0:35                 ` Haojian Zhuang
2013-07-13 14:30                   ` Daniel Drake
2013-07-13 19:56             ` Olof Johansson
2013-07-15  4:39               ` Jason Cooper
2013-07-10 20:50     ` Matt Sealey
2013-07-10 21:49       ` Jason Cooper
2013-07-11 11:20         ` Neil Zhang
2013-07-14 19:29           ` Arnd Bergmann
2013-07-17 13:37             ` Neil Zhang
2013-07-09  6:42 ` [PATCH V3 2/3] clocksource: mmp: support CLOCKSOURCE OF DECLARE Neil Zhang
2013-07-09 16:14   ` Thomas Petazzoni
2013-07-09 21:16     ` Arnd Bergmann
2013-07-10  5:58       ` Haojian Zhuang
2013-07-11 11:23         ` Neil Zhang
2013-07-11 23:51           ` Haojian Zhuang
2013-07-09  6:42 ` [PATCH V3 3/3] ARM: mmp: bring up pxa988 with device tree support Neil Zhang
2013-07-09 22:05   ` Arnd Bergmann [this message]
2013-07-11 11:35     ` Neil Zhang

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=201307100005.21769.arnd@arndb.de \
    --to=arnd@arndb.de \
    --cc=chao.xie@marvell.com \
    --cc=devicetree-discuss@lists.ozlabs.org \
    --cc=grant.likely@linaro.org \
    --cc=haojian.zhuang@gmail.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=zhangwm@marvell.com \
    /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

Powered by JetHome