devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
* [PATCH 1/1] arm: imx7d: correct chip version information
@ 2015-12-14 21:46 Frank Li
       [not found] ` <1450129582-4261-1-git-send-email-Frank.Li-KZfg59tc24xl57MIdRCFDg@public.gmane.org>
  0 siblings, 1 reply; 2+ messages in thread
From: Frank Li @ 2015-12-14 21:46 UTC (permalink / raw)
  To: shawnguo, linux-arm-kernel; +Cc: lznuaa, devicetree

show correct soc version infomation.

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.
+		 */
+		revision = digprog & 0xff;
 	}
 
 	mxc_set_cpu_type(digprog >> 16 & 0xff);
-- 
2.5.2

^ permalink raw reply related	[flat|nested] 2+ messages in thread

* Re: [PATCH 1/1] arm: imx7d: correct chip version information
       [not found] ` <1450129582-4261-1-git-send-email-Frank.Li-KZfg59tc24xl57MIdRCFDg@public.gmane.org>
@ 2015-12-21 11:48   ` Shawn Guo
  0 siblings, 0 replies; 2+ messages in thread
From: Shawn Guo @ 2015-12-21 11:48 UTC (permalink / raw)
  To: Frank Li
  Cc: linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r,
	lznuaa-Re5JQEeQqe8AvxtiuMwx3w, devicetree-u79uwXL29TY76Z2rM5mHXA

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

^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2015-12-21 11:48 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2015-12-14 21:46 [PATCH 1/1] arm: imx7d: correct chip version information Frank Li
     [not found] ` <1450129582-4261-1-git-send-email-Frank.Li-KZfg59tc24xl57MIdRCFDg@public.gmane.org>
2015-12-21 11:48   ` Shawn Guo

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).