diff options
| author | Michael Walle <michael@walle.cc> | 2020-10-16 19:38:18 +0200 |
|---|---|---|
| committer | Priyanka Jain <priyanka.jain@nxp.com> | 2020-10-23 16:52:09 +0530 |
| commit | 4eecc6f1a104b5f3737c7e1bbaaa022e5d3bac53 (patch) | |
| tree | 5a2752fa3c639be998325c12df234e1bcdca45bb /test/py/tests/test_fs/test_ext.py | |
| parent | 026703174a2cf8cd9c83a7c797b96b95af5af69b (diff) | |
armv8: layerscape: don't remove crypto node if just partially disabled
On all newer Layerscape SoCs, only the export-controlled ciphers of the
crypto module are 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.
Signed-off-by: Michael Walle <michael@walle.cc>
Reviewed-by: Horia Geanta <horia.geanta@nxp.com>
Reviewed-by: Priyanka Jain <priyanka.jain@nxp.com>
Diffstat (limited to 'test/py/tests/test_fs/test_ext.py')
0 files changed, 0 insertions, 0 deletions