On 2/22/22 1:38 PM, Sean Anderson wrote:
> This erratum is reported to cause problems on these processors [1-3].
> The problem is usually with the clocking, which is supposed to be
> configured by the RCW [4]. However, if it is not set, or if the default
> clocking is not correct, then this erratum will cause an SError.
> However, according to Ran Wang in [1]:
> 
>> ... this erratum is used to pass USB compliance test only, you could
>> disable this workaround on your board if you don't any USB issue on
>> normal use case, I think it's fine.
> 
> So just disable this erratum by default for these processors.
> 
> [1] https://lore.kernel.org/all/761ddd61-05c1-d9b8-ac90-b8f425afd...@denx.de/
> [2] 
> https://community.nxp.com/t5/Layerscape/LS1046A-U-BOOT-HALT-AT-ERRATUM-A0090078/m-p/742993
> [3] 
> https://community.nxp.com/t5/QorIQ/Why-does-the-LS1043A-U-Boot-hang-at-code-that-fixes-erratum/m-p/644412
> [4] 
> https://source.codeaurora.org/external/qoriq/qoriq-components/rcw/tree/ls1046ardb/usb_phy_freq.rcw
> 
> Signed-off-by: Sean Anderson <sean.ander...@seco.com>
> ---
> 
>  arch/arm/cpu/armv7/ls102xa/Kconfig        | 1 -
>  arch/arm/cpu/armv8/fsl-layerscape/Kconfig | 2 --
>  2 files changed, 3 deletions(-)
> 
> diff --git a/arch/arm/cpu/armv7/ls102xa/Kconfig 
> b/arch/arm/cpu/armv7/ls102xa/Kconfig
> index 6a948d7ba7..cec93a27db 100644
> --- a/arch/arm/cpu/armv7/ls102xa/Kconfig
> +++ b/arch/arm/cpu/armv7/ls102xa/Kconfig
> @@ -7,7 +7,6 @@ config ARCH_LS1021A
>       select SYS_FSL_ERRATUM_A008407
>       select SYS_FSL_ERRATUM_A008850
>       select SYS_FSL_ERRATUM_A008997 if USB
> -     select SYS_FSL_ERRATUM_A009007 if USB
>       select SYS_FSL_ERRATUM_A009008 if USB
>       select SYS_FSL_ERRATUM_A009663
>       select SYS_FSL_ERRATUM_A009798 if USB
> diff --git a/arch/arm/cpu/armv8/fsl-layerscape/Kconfig 
> b/arch/arm/cpu/armv8/fsl-layerscape/Kconfig
> index 9bb870dcd8..f5a18053e6 100644
> --- a/arch/arm/cpu/armv8/fsl-layerscape/Kconfig
> +++ b/arch/arm/cpu/armv8/fsl-layerscape/Kconfig
> @@ -74,7 +74,6 @@ config ARCH_LS1043A
>       select SYS_FSL_DDR_VER_50
>       select SYS_FSL_ERRATUM_A008850 if !TFABOOT
>       select SYS_FSL_ERRATUM_A008997
> -     select SYS_FSL_ERRATUM_A009007
>       select SYS_FSL_ERRATUM_A009008
>       select SYS_FSL_ERRATUM_A009660 if !TFABOOT
>       select SYS_FSL_ERRATUM_A009663 if !TFABOOT
> @@ -112,7 +111,6 @@ config ARCH_LS1046A
>       select SYS_FSL_ERRATUM_A008511 if !TFABOOT
>       select SYS_FSL_ERRATUM_A008850 if !TFABOOT
>       select SYS_FSL_ERRATUM_A008997
> -     select SYS_FSL_ERRATUM_A009007
>       select SYS_FSL_ERRATUM_A009008
>       select SYS_FSL_ERRATUM_A009798
>       select SYS_FSL_ERRATUM_A009801
> 

ping? Can someone from NXP comment on this (either for or against)?

--Sean

Reply via email to