Re: [PATCH v2] armv8: layerscape: don't remove crypto node if just partially disabled

2020-10-16 Thread Horia Geantă
On 8/10/2020 5:54 PM, Michael Walle wrote: > On all newer Layerscape SoCs, the crypto module is just partially > disabled on non-E parts. Thus it doesn't make sense to completely remove > the node. Linux will figure out what is there and what is not. > Could add a clarification here, saying "parti

RE: [PATCH v2] armv8: layerscape: don't remove crypto node if just partially disabled

2020-09-23 Thread Priyanka Jain (OSS)
>-Original Message- >From: U-Boot On Behalf Of Michael Walle >Sent: Monday, August 10, 2020 8:24 PM >To: u-boot@lists.denx.de >Cc: Priyanka Jain ; Horia Geanta >; Michael Walle >Subject: [PATCH v2] armv8: layerscape: don't remove crypto node if just >parti

Re: [PATCH v2] armv8: layerscape: don't remove crypto node if just partially disabled

2020-09-01 Thread Iuliana Prodan
Michael Walle-2 wrote > On all newer Layerscape SoCs, the crypto module is just partially > disabled on non-E parts. Thus it doesn't make sense to completely remove > the node. Linux will figure out what is there and what is not. > > Just remove it for older SoCs, where the module is indeed comple

[PATCH v2] armv8: layerscape: don't remove crypto node if just partially disabled

2020-08-10 Thread Michael Walle
On all newer Layerscape SoCs, the crypto module is just partially disabled on non-E parts. Thus it doesn't make sense to completely remove the node. Linux will figure out what is there and what is not. Just remove it for older SoCs, where the module is indeed completely disabled on non-E parts. S