From: shawnguo@kernel.org (Shawn Guo)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/1] arm: imx7d: correct chip version information
Date: Mon, 21 Dec 2015 19:48:23 +0800 [thread overview]
Message-ID: <20151221114823.GH4703@tiger> (raw)
In-Reply-To: <1450129582-4261-1-git-send-email-Frank.Li@freescale.com>
On Mon, Dec 14, 2015 at 03:46:22PM -0600, Frank Li wrote:
> show correct soc version infomation.
s/infomation/information
I feel you should write your commit log and comments a bit more
seriously. The commit log above is not even a sentence.
For arch/arm/ patches sent to me, please use "ARM" rather than "arm" as
subject prefix.
>
> Signed-off-by: Frank Li <Frank.Li@freescale.com>
> ---
> arch/arm/mach-imx/anatop.c | 9 ++++++++-
> 1 file changed, 8 insertions(+), 1 deletion(-)
>
> diff --git a/arch/arm/mach-imx/anatop.c b/arch/arm/mach-imx/anatop.c
> index 231bb25..23a4fc1 100644
> --- a/arch/arm/mach-imx/anatop.c
> +++ b/arch/arm/mach-imx/anatop.c
> @@ -151,7 +151,14 @@ void __init imx_init_revision_from_anatop(void)
> revision = IMX_CHIP_REVISION_1_5;
> break;
> default:
> - revision = IMX_CHIP_REVISION_UNKNOWN;
> + /*
> + * Fail back to return raw register value instead of 0xff.
> + * It will be easy know version information in SOC if it
> + * can't recongized by known version. And some chip like
> + * i.MX7D soc digprog value match linux version format,
> + * needn't map again and direct use register value.
> + */
There are quite a few grammar issues in this piece of comment. Please
fix them.
> + revision = digprog & 0xff;
I'm fine with it. But we should be clear about that with this change,
the "unknown revision" message in imx_print_silicon_rev() will never work
then for digprog.
Shawn
> }
>
> mxc_set_cpu_type(digprog >> 16 & 0xff);
> --
> 2.5.2
>
>
WARNING: multiple messages have this Message-ID (diff)
From: Shawn Guo <shawnguo-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
To: Frank Li <Frank.Li-KZfg59tc24xl57MIdRCFDg@public.gmane.org>
Cc: linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org,
lznuaa-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org,
devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH 1/1] arm: imx7d: correct chip version information
Date: Mon, 21 Dec 2015 19:48:23 +0800 [thread overview]
Message-ID: <20151221114823.GH4703@tiger> (raw)
In-Reply-To: <1450129582-4261-1-git-send-email-Frank.Li-KZfg59tc24xl57MIdRCFDg@public.gmane.org>
On Mon, Dec 14, 2015 at 03:46:22PM -0600, Frank Li wrote:
> show correct soc version infomation.
s/infomation/information
I feel you should write your commit log and comments a bit more
seriously. The commit log above is not even a sentence.
For arch/arm/ patches sent to me, please use "ARM" rather than "arm" as
subject prefix.
>
> Signed-off-by: Frank Li <Frank.Li-KZfg59tc24xl57MIdRCFDg@public.gmane.org>
> ---
> arch/arm/mach-imx/anatop.c | 9 ++++++++-
> 1 file changed, 8 insertions(+), 1 deletion(-)
>
> diff --git a/arch/arm/mach-imx/anatop.c b/arch/arm/mach-imx/anatop.c
> index 231bb25..23a4fc1 100644
> --- a/arch/arm/mach-imx/anatop.c
> +++ b/arch/arm/mach-imx/anatop.c
> @@ -151,7 +151,14 @@ void __init imx_init_revision_from_anatop(void)
> revision = IMX_CHIP_REVISION_1_5;
> break;
> default:
> - revision = IMX_CHIP_REVISION_UNKNOWN;
> + /*
> + * Fail back to return raw register value instead of 0xff.
> + * It will be easy know version information in SOC if it
> + * can't recongized by known version. And some chip like
> + * i.MX7D soc digprog value match linux version format,
> + * needn't map again and direct use register value.
> + */
There are quite a few grammar issues in this piece of comment. Please
fix them.
> + revision = digprog & 0xff;
I'm fine with it. But we should be clear about that with this change,
the "unknown revision" message in imx_print_silicon_rev() will never work
then for digprog.
Shawn
> }
>
> mxc_set_cpu_type(digprog >> 16 & 0xff);
> --
> 2.5.2
>
>
--
To unsubscribe from this list: send the line "unsubscribe devicetree" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2015-12-21 11:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-14 21:46 [PATCH 1/1] arm: imx7d: correct chip version information Frank Li
2015-12-14 21:46 ` Frank Li
2015-12-21 11:48 ` Shawn Guo [this message]
2015-12-21 11:48 ` Shawn Guo
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=20151221114823.GH4703@tiger \
--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 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.