public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Matthias Brugger <mbrugger@suse.com>
To: Vladimir Murzin <vladimir.murzin@arm.com>, sudeep.holla@arm.com
Cc: lorenzo.pieralisi@arm.com, linux@arm.linux.org.uk, arnd@arndb.de,
	liviu.dudau@arm.com, linux-kernel@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 4/5] ARM: dts: introduce MPS2 AN399/AN400
Date: Mon, 25 Apr 2016 11:24:34 +0200	[thread overview]
Message-ID: <571DE252.6080402@suse.com> (raw)
In-Reply-To: <1461574157-23580-5-git-send-email-vladimir.murzin@arm.com>



On 25/04/16 10:49, Vladimir Murzin wrote:
> Application Notes 399 and 400 shares the same memory map and
> features. Both are shipped with Cortex-M7 and have the same  peripheral
> as AN385/AN386, but with different location of PSRAM and Ethernet
> controller.
>
> Signed-off-by: Vladimir Murzin <vladimir.murzin@arm.com>
> ---
>   arch/arm/boot/dts/Makefile       |    4 +-
>   arch/arm/boot/dts/mps2-an399.dts |   92 ++++++++++++++++++++++++++++++++++++++
>   2 files changed, 95 insertions(+), 1 deletion(-)
>   create mode 100644 arch/arm/boot/dts/mps2-an399.dts
>
> diff --git a/arch/arm/boot/dts/Makefile b/arch/arm/boot/dts/Makefile
> index 1efa5a2..c7a78c9 100644
> --- a/arch/arm/boot/dts/Makefile
> +++ b/arch/arm/boot/dts/Makefile
> @@ -253,7 +253,9 @@ dtb-$(CONFIG_ARCH_MMP) += \
>   dtb-$(CONFIG_MACH_MESON8B) += \
>   	meson8b-mxq.dtb \
>   	meson8b-odroidc1.dtb
> -dtb-$(CONFIG_ARCH_MPS2) += mps2-an385.dtb
> +dtb-$(CONFIG_ARCH_MPS2) += \
> +	mps2-an385.dtb \
> +	mps2-an399.dtb
>   dtb-$(CONFIG_ARCH_MOXART) += \
>   	moxart-uc7112lx.dtb
>   dtb-$(CONFIG_SOC_IMX1) += \
> diff --git a/arch/arm/boot/dts/mps2-an399.dts b/arch/arm/boot/dts/mps2-an399.dts
> new file mode 100644
> index 0000000..776595f
> --- /dev/null
> +++ b/arch/arm/boot/dts/mps2-an399.dts
> @@ -0,0 +1,92 @@
> +/*
> + * Copyright (C) 2015 ARM Limited
> + *
> + * Author: Vladimir Murzin <vladimir.murzin@arm.com>
> + *
> + * This file is dual-licensed: you can use it either under the terms
> + * of the GPL or the X11 license, at your option. Note that this dual
> + * licensing only applies to this file, and not this project as a
> + * whole.
> + *
> + *  a) This file 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.
> + *
> + *     This file is distributed in the hope that it will be useful,
> + *     but WITHOUT ANY WARRANTY; without even the implied warranty of
> + *     MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
> + *     GNU General Public License for more details.
> + *
> + * Or, alternatively,
> + *
> + *  b) Permission is hereby granted, free of charge, to any person
> + *     obtaining a copy of this software and associated documentation
> + *     files (the "Software"), to deal in the Software without
> + *     restriction, including without limitation the rights to use,
> + *     copy, modify, merge, publish, distribute, sublicense, and/or
> + *     sell copies of the Software, and to permit persons to whom the
> + *     Software is furnished to do so, subject to the following
> + *     conditions:
> + *
> + *     The above copyright notice and this permission notice shall be
> + *     included in all copies or substantial portions of the Software.
> + *
> + *     THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND,
> + *     EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES
> + *     OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND
> + *     NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT
> + *     HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY,
> + *     WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING
> + *     FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR
> + *     OTHER DEALINGS IN THE SOFTWARE.
> + */
> +
> +/dts-v1/;
> +
> +#include "mps2.dtsi"
> +
> +/ {
> +	model = "ARM MPS2 Application Note 399/400";
> +	compatible = "arm,mps2";
> +
> +	aliases {
> +		serial0 = &uart0;
> +	};
> +
> +	chosen {
> +		bootargs = "rdinit=/sbin/init earlycon";

Same here.

  reply	other threads:[~2016-04-25  9:25 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-25  8:49 [PATCH 0/5] Support MPS2 platform Vladimir Murzin
2016-04-25  8:49 ` [PATCH 1/5] ARM: vexpress/mps2: introduce " Vladimir Murzin
2016-04-25  8:49 ` [PATCH 2/5] ARM: configs: add MPS2 defconfig Vladimir Murzin
2016-04-25  8:49 ` [PATCH 3/5] ARM: dts: introduce MPS2 AN385/AN386 Vladimir Murzin
2016-04-25  9:23   ` Matthias Brugger
2016-04-25 10:15     ` Vladimir Murzin
2016-04-25 11:32       ` Arnd Bergmann
2016-04-25 12:03         ` Vladimir Murzin
2016-04-25 13:52           ` Sudeep Holla
2016-04-25  8:49 ` [PATCH 4/5] ARM: dts: introduce MPS2 AN399/AN400 Vladimir Murzin
2016-04-25  9:24   ` Matthias Brugger [this message]
2016-04-25  8:49 ` [PATCH 5/5] MAINTAINERS: Update ARM Versatile Express platform entry Vladimir Murzin

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=571DE252.6080402@suse.com \
    --to=mbrugger@suse.com \
    --cc=arnd@arndb.de \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@arm.linux.org.uk \
    --cc=liviu.dudau@arm.com \
    --cc=lorenzo.pieralisi@arm.com \
    --cc=sudeep.holla@arm.com \
    --cc=vladimir.murzin@arm.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