From: andrew@lunn.ch (Andrew Lunn)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: mvebu: Update the SoC ID and revision definitions
Date: Fri, 9 Jan 2015 16:22:35 +0100 [thread overview]
Message-ID: <20150109152235.GC18832@lunn.ch> (raw)
In-Reply-To: <1420729688-31882-1-git-send-email-gregory.clement@free-electrons.com>
On Thu, Jan 08, 2015 at 04:08:08PM +0100, Gregory CLEMENT wrote:
> Add the missing SoC and revision ID for the Armada 370 and 38x SoCs.
>
> Signed-off-by: Gregory CLEMENT <gregory.clement@free-electrons.com>
Added to mvebu/soc
Andrew
> ---
> arch/arm/mach-mvebu/mvebu-soc-id.h | 18 ++++++++++++++++++
> 1 file changed, 18 insertions(+)
>
> diff --git a/arch/arm/mach-mvebu/mvebu-soc-id.h b/arch/arm/mach-mvebu/mvebu-soc-id.h
> index c16bb68ca81f..e124a0b82a3e 100644
> --- a/arch/arm/mach-mvebu/mvebu-soc-id.h
> +++ b/arch/arm/mach-mvebu/mvebu-soc-id.h
> @@ -20,10 +20,28 @@
> #define MV78XX0_A0_REV 0x1
> #define MV78XX0_B0_REV 0x2
>
> +/* Amada 370 ID */
> +#define ARMADA_370_DEV_ID 0x6710
> +
> +/* Amada 370 Revision */
> +#define ARMADA_370_A1_REV 0x1
> +
> +/* Armada 375 ID */
> +#define ARMADA_375_DEV_ID 0x6720
> +
> /* Armada 375 */
> #define ARMADA_375_Z1_REV 0x0
> #define ARMADA_375_A0_REV 0x3
>
> +/* Armada 38x ID */
> +#define ARMADA_380_DEV_ID 0x6810
> +#define ARMADA_385_DEV_ID 0x6820
> +#define ARMADA_388_DEV_ID 0x6828
> +
> +/* Armada 38x Revision */
> +#define ARMADA_38x_Z1_REV 0x0
> +#define ARMADA_38x_A0_REV 0x4
> +
> #ifdef CONFIG_ARCH_MVEBU
> int mvebu_get_soc_id(u32 *dev, u32 *rev);
> #else
> --
> 1.9.1
>
>
> _______________________________________________
> linux-arm-kernel mailing list
> linux-arm-kernel at lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
prev parent reply other threads:[~2015-01-09 15:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-08 15:08 [PATCH] ARM: mvebu: Update the SoC ID and revision definitions Gregory CLEMENT
2015-01-09 15:22 ` Andrew Lunn [this message]
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=20150109152235.GC18832@lunn.ch \
--to=andrew@lunn.ch \
--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.