[U-Boot] [PATCH v2 1/2] configs: mx6_common: Restrict CONFIG_ARM_ERRATA_742230 for multi-core

Hui.Liu at freescale.com Hui.Liu at freescale.com
Thu Jan 9 04:50:06 CET 2014


> -----Original Message-----
> From: Fabio Estevam [mailto:festevam at gmail.com]
> Sent: Wednesday, January 08, 2014 10:00 PM
> To: sbabic at denx.de
> Cc: shawn.guo at linaro.org; Liu Hui-R64343; u-boot at lists.denx.de; Estevam
> Fabio-R49496
> Subject: [PATCH v2 1/2] configs: mx6_common: Restrict
> CONFIG_ARM_ERRATA_742230 for multi-core
> 
> From: Fabio Estevam <fabio.estevam at freescale.com>
> 
> According to e9fd66defd (ARM: mx6: define CONFIG_ARM_ERRATA_742230), the
> CONFIG_ARM_ERRATA_742230 option should only be applied to multi-core
> variants, so restrict its usage for quad and dual-lite only.
> 
> Quoting Shawn Guo [2]:
> 
> "The sololite has the same core version as dual/quad - r2p10.  The help
> text of erratum 742230 in kernel suggests that only version
> r1p0..r2p2 are affected.  So it sounds like the erratum 742230 should be
> irrelevant to i.MX6 SoCs.  However we were running into a reboot issue on
> multi-core i.MX6 SoCs.  There was a quite long discussion [1] about it.
> Though we did not reach a conclusion in the thread, one ARM people sent
> me a private message, suggesting this should be an ARM core issue and
> workaround for erratum 742230 might help.  And it turns out what he said
> is true.  And that's why I came up with the commit e9fd66defd (ARM:
> mx6: define CONFIG_ARM_ERRATA_742230) to turn on the erratum for imx6
> dual/quad.
> 
> Shawn
> 
> [1] http://lists.infradead.org/pipermail/linux-arm-kernel/2012-
> August/thread.html#113096"
> 
> [2] http://lists.denx.de/pipermail/u-boot/2014-January/170424.html


The commit log really get me confused, why we need enable one ERRATA which should not be applied?
This will make customer confused at all. We need find the real root-cause for it other than hack it
Otherwise, you will get more and more problems sooner or later...

If you looking at the link in [1], it said, this issue only affected with v6+v7 one zImage kernel,
And not exist with v7 only kernel, which means something should be wrong with v6+v7 one zImage kernel.


Jason Liu

> 
> Signed-off-by: Fabio Estevam <fabio.estevam at freescale.com>
> ---
> Changes since v1:
> - Improve commit log
> 
>  include/configs/mx6_common.h | 2 ++
>  1 file changed, 2 insertions(+)
> 
> diff --git a/include/configs/mx6_common.h b/include/configs/mx6_common.h
> index 514d634..0b8db85 100644
> --- a/include/configs/mx6_common.h
> +++ b/include/configs/mx6_common.h
> @@ -17,7 +17,9 @@
>  #ifndef __MX6_COMMON_H
>  #define __MX6_COMMON_H
> 
> +#if defined(CONFIG_MX6Q) ||  defined(CONFIG_MX6DL)
>  #define CONFIG_ARM_ERRATA_742230
> +#endif
>  #define CONFIG_ARM_ERRATA_743622
>  #define CONFIG_ARM_ERRATA_751472
>  #define CONFIG_BOARD_POSTCLK_INIT
> --
> 1.8.1.2
> 
> 



More information about the U-Boot mailing list