ramdump: write compressed data [2/2]

PD#SWPL-6193

Problem:
ramdump need write compressed data to persist storage device.
But if we write it under uboot, it may cause journal and block
bitmap mismatch due to different version of file system. This
caused kernel panic after ramdump finished.

Solution:
Write compressed data under kernel.
This change also removed some extern function of ramdump since
we use sticky register to store ramdump information.

Verify:
p212

Change-Id: Idd83ec6ead4783918b90a39cf716fd3117402278
Signed-off-by: Tao Zeng <tao.zeng@amlogic.com>
This commit is contained in:
Tao Zeng
2019-03-22 14:12:05 +08:00
committed by Luke Go
parent e56c051873
commit 6c72eb1412
4 changed files with 4 additions and 0 deletions

View File

@@ -473,6 +473,7 @@
status = "okay";
reg = <0xFF6345E0 4>;
reg-names = "PREG_STICKY_REG8";
store_device = "data";
};
jtag {

View File

@@ -281,6 +281,7 @@
status = "okay";
reg = <0xFF6345E0 4>;
reg-names = "PREG_STICKY_REG8";
store_device = "data";
};
vpu {

View File

@@ -473,6 +473,7 @@
status = "okay";
reg = <0x0 0xFF6345E0 0x0 4>;
reg-names = "PREG_STICKY_REG8";
store_device = "data";
};
jtag {

View File

@@ -262,6 +262,7 @@
status = "okay";
reg = <0x0 0xFF6345E0 0x0 4>;
reg-names = "PREG_STICKY_REG8";
store_device = "data";
};
vpu {