mirror of
https://github.com/torvalds/linux.git
synced 2024-12-12 14:12:51 +00:00
ARM: dts: n900: Enable omap sham and include directly omap34xx.dtsi
This patch moves content of file omap34xx-hs.dtsi into omap3-n900.dts and enable omap sham support (omap HW support for SHA + MD5). After testing both omap hwmod and omap-sham.ko drivers it looks like signed Nokia X-Loader enable L3 firewall for omap sham. There is no kernel crash with both official bootloader and crypto enable bootloader. So we can safely enable sham code. Signed-off-by: Pali Rohár <pali.rohar@gmail.com> Acked-by: Pavel Machek <pavel@ucw.cz> Signed-off-by: Tony Lindgren <tony@atomide.com>
This commit is contained in:
parent
a494e32d3a
commit
69540a7c27
@ -9,9 +9,23 @@
|
||||
|
||||
/dts-v1/;
|
||||
|
||||
#include "omap34xx-hs.dtsi"
|
||||
#include "omap34xx.dtsi"
|
||||
#include <dt-bindings/input/input.h>
|
||||
|
||||
/*
|
||||
* Default secure signed bootloader (Nokia X-Loader) does not enable L3 firewall
|
||||
* for omap AES HW crypto support. When linux kernel try to access memory of AES
|
||||
* blocks then kernel receive "Unhandled fault: external abort on non-linefetch"
|
||||
* and crash. Until somebody fix omap-aes.c and omap_hwmod_3xxx_data.c code (no
|
||||
* crash anymore) omap AES support will be disabled for all Nokia N900 devices.
|
||||
* There is "unofficial" version of bootloader which enables AES in L3 firewall
|
||||
* but it is not widely used and to prevent kernel crash rather AES is disabled.
|
||||
* There is also no runtime detection code if AES is disabled in L3 firewall...
|
||||
*/
|
||||
&aes {
|
||||
status = "disabled";
|
||||
};
|
||||
|
||||
/ {
|
||||
model = "Nokia N900";
|
||||
compatible = "nokia,omap3-n900", "ti,omap3430", "ti,omap3";
|
||||
|
Loading…
Reference in New Issue
Block a user