On 7/3/2020 3:25 PM, Peng Fan wrote:
> Sorry to break LS1021A. But I wonder why i.MX code would affect LS?
>
imx_soc_device_init() was modified to be called for all SoCs under ARCH_MXC.
multi_v7_defconfig, which is used for LS1021A, selects ARCH_MXC.
Previously imx_soc_device_init() was called
> Subject: Re: [PATCH V3 0/3] ARM: imx: move cpu code to drivers/soc/imx
>
> On 5/20/2020 9:01 AM, Peng Fan wrote:
> > From: Peng Fan
> >
> > V3:
> > Rebased to latest next tree
> > Resolved the conflicts with vf610 soc patch
> >
> > V2:
>
On 5/20/2020 9:01 AM, Peng Fan wrote:
> From: Peng Fan
>
> V3:
> Rebased to latest next tree
> Resolved the conflicts with vf610 soc patch
>
> V2:
> Keep i.MX1/2/3/5 cpu type for completness
> Correct return value in patch 1/3
> use CONFIG_ARM to guard compile soc-imx.c in patch 3/3
>
>
On Wed, May 20, 2020 at 01:51:26PM +0800, peng@nxp.com wrote:
> From: Peng Fan
>
> V3:
> Rebased to latest next tree
> Resolved the conflicts with vf610 soc patch
>
> V2:
> Keep i.MX1/2/3/5 cpu type for completness
> Correct return value in patch 1/3
> use CONFIG_ARM to guard compile
From: Peng Fan
V3:
Rebased to latest next tree
Resolved the conflicts with vf610 soc patch
V2:
Keep i.MX1/2/3/5 cpu type for completness
Correct return value in patch 1/3
use CONFIG_ARM to guard compile soc-imx.c in patch 3/3
V1:
https://patchwork.kernel.org/cover/11433689/
RFC version :
5 matches
Mail list logo