Adding SHA256 support to Marvell crypto driver resulted in regression
for older SoC's, not capable of handling this mode in hardware.
Details
Details
- Reviewers
zbb fabient imp • ian - Commits
- rS312744: Fix SHA256 usage on older CESA versions
Diff Detail
Diff Detail
- Lint
Lint Skipped - Unit
Tests Skipped
Event Timeline
Comment Actions
imho, this is papering over problem in DTS. If CESA device have more variants, then each one must have different 'compatible' string.
In other words, you cannot use same 'compatible' string for different devices (if the difference cannot be determined at runtime).
BTW, why you can't use 'standard' DTS for Marvell SOCs, even with FBSD specific overlay?