From: s.hauer@pengutronix.de (Sascha Hauer)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: i.MX6: add more chip revision support
Date: Mon, 21 Jul 2014 08:35:20 +0200 [thread overview]
Message-ID: <20140721063520.GR23235@pengutronix.de> (raw)
In-Reply-To: <1405921091-28748-1-git-send-email-shawn.guo@freescale.com>
On Mon, Jul 21, 2014 at 01:38:11PM +0800, Shawn Guo wrote:
> From: Jason Liu <r64343@freescale.com>
>
> Add more revision support for the new i.MX6DQ tap-out (TO1.5). This
> TO1.5 is the Rev 1.3 as documented in i.MX6DQ data sheet, because TO1.3
> and TO1.4 are never revealed.
So the chip identifies itself as 1.5 but the data sheet refers to it as
1.3. Is there a way to make that clear somewhere? Otherwise it's really
confusing.
Sascha
>
> Signed-off-by: Jason Liu <r64343@freescale.com>
> Signed-off-by: Shawn Guo <shawn.guo@freescale.com>
> ---
> arch/arm/mach-imx/anatop.c | 9 +++++++++
> arch/arm/mach-imx/mxc.h | 2 ++
> 2 files changed, 11 insertions(+)
>
> diff --git a/arch/arm/mach-imx/anatop.c b/arch/arm/mach-imx/anatop.c
> index 4a40bbb46183..459ba290744b 100644
> --- a/arch/arm/mach-imx/anatop.c
> +++ b/arch/arm/mach-imx/anatop.c
> @@ -104,6 +104,15 @@ void __init imx_init_revision_from_anatop(void)
> case 2:
> revision = IMX_CHIP_REVISION_1_2;
> break;
> + case 3:
> + revision = IMX_CHIP_REVISION_1_3;
> + break;
> + case 4:
> + revision = IMX_CHIP_REVISION_1_4;
> + break;
> + case 5:
> + revision = IMX_CHIP_REVISION_1_5;
> + break;
> default:
> revision = IMX_CHIP_REVISION_UNKNOWN;
> }
> diff --git a/arch/arm/mach-imx/mxc.h b/arch/arm/mach-imx/mxc.h
> index a39b69ef4301..17a41ca65acf 100644
> --- a/arch/arm/mach-imx/mxc.h
> +++ b/arch/arm/mach-imx/mxc.h
> @@ -43,6 +43,8 @@
> #define IMX_CHIP_REVISION_1_1 0x11
> #define IMX_CHIP_REVISION_1_2 0x12
> #define IMX_CHIP_REVISION_1_3 0x13
> +#define IMX_CHIP_REVISION_1_4 0x14
> +#define IMX_CHIP_REVISION_1_5 0x15
> #define IMX_CHIP_REVISION_2_0 0x20
> #define IMX_CHIP_REVISION_2_1 0x21
> #define IMX_CHIP_REVISION_2_2 0x22
> --
> 1.9.1
>
>
--
Pengutronix e.K. | |
Industrial Linux Solutions | http://www.pengutronix.de/ |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
next prev parent reply other threads:[~2014-07-21 6:35 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-21 5:38 [PATCH] ARM: i.MX6: add more chip revision support Shawn Guo
2014-07-21 6:35 ` Sascha Hauer [this message]
2014-07-21 6:41 ` Uwe Kleine-König
2014-07-21 7:01 ` Shawn Guo
2014-07-21 7:06 ` Shawn Guo
2014-07-21 8:21 ` Sascha Hauer
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=20140721063520.GR23235@pengutronix.de \
--to=s.hauer@pengutronix.de \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).