All of lore.kernel.org
 help / color / mirror / Atom feed
From: gregory.clement@free-electrons.com (Gregory CLEMENT)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 04/11] ARM: mvebu: add Device Tree description of the Armada 375 SoC
Date: Mon, 10 Feb 2014 18:37:12 +0100	[thread overview]
Message-ID: <52F90E48.8010204@free-electrons.com> (raw)
In-Reply-To: <20140210173527.GR8533@titan.lakedaemon.net>

On 10/02/2014 18:35, Jason Cooper wrote:
> On Mon, Feb 10, 2014 at 06:23:15PM +0100, Thomas Petazzoni wrote:
>> From: Gregory CLEMENT <gregory.clement@free-electrons.com>
>>
>> The Armada 375 SoC is a new SoC from Marvell, based on a dual core
>> Cortex-A9 and a number of hardware blocks that are common with earlier
>> SoCs from the mvebu family.
>>
>> The provided Device Tree describes the following parts of the SoC:
>>
>>  * CPUs
>>  * Device Bus
>>  * Clocks
>>  * Interrupt controllers: GIC and MPIC
>>  * GPIO controllers
>>  * I2C buses
>>  * L2 cache
>>  * MBus controller
>>  * SDIO
>>  * Pinctrl
>>  * SATA
>>  * Serial
>>  * SPI buses
>>  * System controller (for reboot)
>>  * Timer
>>  * XOR engines
>>  * PCIe controllers
>>
>> Signed-off-by: Gregory CLEMENT <gregory.clement@free-electrons.com>
>> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
>> ---
>>  arch/arm/boot/dts/armada-375.dtsi | 439 ++++++++++++++++++++++++++++++++++++++
>>  1 file changed, 439 insertions(+)
>>  create mode 100644 arch/arm/boot/dts/armada-375.dtsi
>>
>> diff --git a/arch/arm/boot/dts/armada-375.dtsi b/arch/arm/boot/dts/armada-375.dtsi
>> new file mode 100644
>> index 0000000..2697345
>> --- /dev/null
>> +++ b/arch/arm/boot/dts/armada-375.dtsi
>> @@ -0,0 +1,439 @@
>> +/*
>> + * Device Tree Include file for Marvell Armada 375 family SoC
>> + *
>> + * Copyright (C) 2014 Marvell
>> + *
>> + * Gregory CLEMENT <gregory.clement@free-electrons.com>
>> + * Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
>> + *
>> + * This file is licensed under the terms of the GNU General Public
>> + * License version 2.  This program is licensed "as is" without any
>> + * warranty of any kind, whether express or implied.
>> + */
>> +
>> +/include/ "skeleton.dtsi"
>> +
>> +#define MBUS_ID(target,attributes) (((target) << 24) | ((attributes) << 16))
>> +
>> +/ {
>> +	model = "Marvell Armada 375 family SoC";
>> +	compatible = "marvell,armada375";
>> +
>> +	aliases {
>> +		gpio0 = &gpio0;
>> +		gpio1 = &gpio1;
>> +		gpio2 = &gpio2;
>> +	};
>> +
>> +	clocks {
>> +		/* 2 GHz fixed main PLL */
>> +		mainpll: mainpll {
>> +			compatible = "fixed-clock";
>> +			#clock-cells = <0>;
>> +			clock-frequency = <2000000000>;
>> +		};
>> +	};
>> +
>> +	cpus {
>> +		#address-cells = <1>;
>> +		#size-cells = <0>;
>> +		cpu at 0 {
>> +			device_type = "cpu";
>> +			compatible = "arm,cortex-a9";
>> +			reg = <0>;
>> +		};
>> +		cpu at 1 {
>> +			device_type = "cpu";
>> +			compatible = "arm,cortex-a9";
>> +			reg = <1>;
>> +		};
>> +	};
>> +
>> +	soc {
> ...
>> +		internal-regs {
> ...
>> +			gateclk: clock-gating-control at 18220 {
>> +				compatible = "marvell,armada-375-gating-clock";
>> +				reg = <0x18220 0x4>;
>> +				clocks = <&coreclk 0>;
>> +				#clock-cells = <1>;
>> +			};
>> +
> ...
>> +			coreclk: mvebu-sar at e8204 {
>> +				compatible = "marvell,armada-375-core-clock";
>> +				reg = <0xe8204 0x04>;
>> +				#clock-cells = <1>;
>> +			};
>> +
>> +			coredivclk: corediv-clock at e8250 {
>> +				compatible = "marvell,armada-375-corediv-clock";
>> +				reg = <0xe8250 0xc>;
>> +				#clock-cells = <1>;
>> +				clocks = <&mainpll>;
>> +				clock-output-names = "nand";
>> +			};
> 
> Thanks for putting the internal-regs nodes in order so I didn't have to
> ask.  :) Have you noticed the same problem as the other SoCs with clock
> ordering on bootup?

Yes :(

> 
> thx,
> 
> Jason.
> 


-- 
Gregory Clement, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com

  reply	other threads:[~2014-02-10 17:37 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-10 17:23 [PATCH 00/11] Core support for Marvell Armada 375 and 38x Thomas Petazzoni
2014-02-10 17:23 ` [PATCH 01/11] ARM: mvebu: add Armada 375 support to the system-controller driver Thomas Petazzoni
2014-02-10 17:23 ` [PATCH 02/11] ARM: mvebu: add initial support for the Armada 375 SOCs Thomas Petazzoni
2014-02-10 17:23 ` [PATCH 03/11] ARM: mvebu: add workaround for data abort issue on Armada 375 Thomas Petazzoni
2014-02-10 17:23 ` [PATCH 04/11] ARM: mvebu: add Device Tree description of the Armada 375 SoC Thomas Petazzoni
2014-02-10 17:35   ` Jason Cooper
2014-02-10 17:37     ` Gregory CLEMENT [this message]
2014-02-10 17:23 ` [PATCH 05/11] ARM: mvebu: add Device Tree for the Armada 375 DB board Thomas Petazzoni
2014-02-10 17:37   ` Andrew Lunn
2014-02-10 17:47     ` Thomas Petazzoni
2014-02-10 17:23 ` [PATCH 06/11] ARM: mvebu: add Armada 380/385 support to the system-controller driver Thomas Petazzoni
2014-02-10 17:39   ` Jason Cooper
2014-02-10 17:47     ` Thomas Petazzoni
2014-02-10 18:48       ` Jason Cooper
2014-02-10 19:03         ` Thomas Petazzoni
2014-02-11 14:22     ` Grant Likely
2014-02-11 15:24       ` Thomas Petazzoni
2014-02-11 15:30         ` Jason Cooper
2014-02-11 15:50           ` Gregory CLEMENT
2014-02-10 17:23 ` [PATCH 07/11] ARM: mvebu: add initial support for the Armada 380/385 SOCs Thomas Petazzoni
2014-02-10 17:44   ` Andrew Lunn
2014-02-10 17:55     ` Thomas Petazzoni
2014-02-10 17:23 ` [PATCH 08/11] ARM: mvebu: add Device Tree description of the Armada 380/385 SoCs Thomas Petazzoni
2014-02-10 17:23 ` [PATCH 09/11] ARM: mvebu: add Device Tree for the Armada 385 DB board Thomas Petazzoni
2014-02-10 17:23 ` [PATCH 10/11] ARM: mvebu: update defconfigs for Armada 375 and 38x Thomas Petazzoni
2014-02-10 17:23 ` [PATCH 11/11] Documentation: arm: update Marvell documentation about Armada 375/38x Thomas Petazzoni
2014-02-10 17:47 ` [PATCH 00/11] Core support for Marvell Armada 375 and 38x Jason Gunthorpe

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=52F90E48.8010204@free-electrons.com \
    --to=gregory.clement@free-electrons.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.