From: shawnguo@kernel.org (Shawn Guo)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: i.MX6: add new silicon revision number 1.6
Date: Fri, 2 Feb 2018 13:36:32 +0800 [thread overview]
Message-ID: <20180202053630.GI20833@dragon> (raw)
In-Reply-To: <1515502273.2493.9.camel@googlemail.com>
On Tue, Jan 09, 2018 at 01:51:13PM +0100, Christoph Fritz wrote:
> This patch adds new silicon revision number 1.6 as specified in document
> IMX6DQCEC.pdf.
>
> Signed-off-by: Christoph Fritz <chf.fritz@googlemail.com>
We have a patch [1] from Bai Ping that reworks the code. It makes your
patch unnecessary?
Shawn
[1] https://patchwork.ozlabs.org/patch/857284/
> ---
> arch/arm/mach-imx/anatop.c | 4 ++++
> include/soc/imx/revision.h | 1 +
> 2 files changed, 5 insertions(+)
>
> diff --git a/arch/arm/mach-imx/anatop.c b/arch/arm/mach-imx/anatop.c
> index 649a84c..deb98b8 100644
> --- a/arch/arm/mach-imx/anatop.c
> +++ b/arch/arm/mach-imx/anatop.c
> @@ -157,6 +157,10 @@ void __init imx_init_revision_from_anatop(void)
> */
> revision = IMX_CHIP_REVISION_1_5;
> break;
> + case 6:
> + /* marked as 'E' in part number last character */
> + revision = IMX_CHIP_REVISION_1_6;
> + break;
> default:
> /*
> * Fail back to return raw register value instead of 0xff.
> diff --git a/include/soc/imx/revision.h b/include/soc/imx/revision.h
> index 9ea3469..cd4c847 100644
> --- a/include/soc/imx/revision.h
> +++ b/include/soc/imx/revision.h
> @@ -15,6 +15,7 @@
> #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_1_6 0x16
> #define IMX_CHIP_REVISION_2_0 0x20
> #define IMX_CHIP_REVISION_2_1 0x21
> #define IMX_CHIP_REVISION_2_2 0x22
> --
> 2.1.4
>
next prev parent reply other threads:[~2018-02-02 5:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-09 12:51 [PATCH] ARM: i.MX6: add new silicon revision number 1.6 Christoph Fritz
2018-01-10 12:15 ` Fabio Estevam
2018-02-02 5:36 ` Shawn Guo [this message]
2018-02-02 11:25 ` Christoph Fritz
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=20180202053630.GI20833@dragon \
--to=shawnguo@kernel.org \
--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