linux-kernel - Re: [PATCH 4/8] ARM: add Marvell Berlin SoC familiy to Marvell doc

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <525C7993.40408@gmail.com>
Date:	Tue, 15 Oct 2013 01:09:07 +0200
From:	Sebastian Hesselbarth <sebastian.hesselbarth@...il.com>
To:	Sebastian Hesselbarth <sebastian.hesselbarth@...il.com>,
	Sebastian Hesselbarth <sebastian.hesselbarth@...il.com>
CC:	Jason Cooper <jason@...edaemon.net>,
	Thomas Petazzoni <thomas.petazzoni@...e-electrons.com>,
	Arnd Bergmann <arnd@...db.de>, Rob Landley <rob@...dley.net>,
	linux-doc@...r.kernel.org, linux-arm-kernel@...ts.infradead.org,
	linux-kernel@...r.kernel.org, Jisheng Zhang <jszhang@...vell.com>
Subject: Re: [PATCH 4/8] ARM: add Marvell Berlin SoC familiy to Marvell doc

On 10/08/2013 02:24 PM, Sebastian Hesselbarth wrote:
> This adds known facts and rumors about the Marvell Berlin (88DE3xxx) SoC
> family to the Marvell SoC documentation.
>
> Signed-off-by: Sebastian Hesselbarth <sebastian.hesselbarth@...il.com>
> Reviewed-by: Jason Cooper <jason@...edaemon.net>
> Reviewed-by: Thomas Petazzoni <thomas.petazzoni@...e-electrons.com>
> Reviewed-by: Arnd Bergmann <arnd@...db.de>
> ---
> Changelog:
> RFCv2->v1:
> - move Berlin below PXA/MMP[23] where it belongs to
> - add note about IP (re-)used in Berlin SoCs
> RFCv1->RFCv2:
> - initial patch
>
> Cc: Jason Cooper <jason@...edaemon.net>
> Cc: Thomas Petazzoni <thomas.petazzoni@...e-electrons.com>
> Cc: Arnd Bergmann <arnd@...db.de>
> Cc: Rob Landley <rob@...dley.net>
> Cc: linux-doc@...r.kernel.org
> Cc: linux-arm-kernel@...ts.infradead.org
> Cc: linux-kernel@...r.kernel.org
> ---
>   Documentation/arm/Marvell/README |   29 +++++++++++++++++++++++++++++
>   1 file changed, 29 insertions(+)
>
> diff --git a/Documentation/arm/Marvell/README b/Documentation/arm/Marvell/README
> index 8f08a86..993c45d 100644
> --- a/Documentation/arm/Marvell/README
> +++ b/Documentation/arm/Marvell/README
> @@ -210,6 +210,35 @@ MMP/MMP2 family (communication processor)
>      Linux kernel mach directory: arch/arm/mach-mmp
>      Linux kernel plat directory: arch/arm/plat-pxa
>
> +Berlin family (Digital Entertainment)
> +-------------------------------------
> +
> +  Flavors:
> +	88DE3005, Armada 1500-mini
> +		Design name:	BG2CD(A0)
> +		Core:		ARM Cortex-A9, PL310 L2CC
> +		Homepage:	http://www.marvell.com/digital-entertainment/armada-1500-mini/
> +	88DE3010, Armada 1000
> +		Design name:	BG2(?)
> +		Core:		Marvell PJ4B (ARMv7), Tauros3 L2CC
> +		Product Brief:	http://www.marvell.com/digital-entertainment/assets/armada_1000_pb.pdf
> +	88DE3100, Armada 1500
> +		Design name:	BG2(A0)
> +		Core:		Marvell PJ4B (ARMv7), Tauros3 L2CC
> +		Homepage:	http://www.marvell.com/digital-entertainment/armada-1500/
> +		Product Brief:	http://www.marvell.com/digital-entertainment/armada-1500/assets/Marvell-ARMADA-1500-Product-Brief.pdf
> +	88DE????
> +		Design name:	BG3
> +		Core:		ARM Cortex-A15, CA15 integrated L2CC

Jisheng,

can you comment on the above and fill in the missing pieces?

Especially, if we want to base device tree compatibles later, we should
make it right in the first place.

Sebastian

> +  Homepage: http://www.marvell.com/digital-entertainment/
> +  Directory: arch/arm/mach-berlin
> +
> +  Comments:
> +   * This line of SoCs is based on Marvell Sheeva or ARM Cortex CPUs
> +     with Synopsys DesignWare (IRQ, GPIO, Timers, ...) and PXA IP (SDHCI, USB, ETH, ...).
> +   * Currently known design names are: C2, BG2(Z1), BG2(A0), BG2CD(A0), BG2CT(A0)
> +
>   Long-term plans
>   ---------------
>
>

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/