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>

Conflicts:
	arch/arm/boot/dts/amlogic/mesonaxg.dtsi
	arch/arm/boot/dts/amlogic/mesong12a.dtsi
	arch/arm/boot/dts/amlogic/mesongxl.dtsi
	arch/arm/boot/dts/amlogic/mesongxm.dtsi
	arch/arm/boot/dts/amlogic/mesontl1.dtsi
	arch/arm/boot/dts/amlogic/mesontxl.dtsi
	arch/arm/boot/dts/amlogic/mesontxlx.dtsi
	arch/arm64/boot/dts/amlogic/mesonaxg.dtsi
	arch/arm64/boot/dts/amlogic/mesong12a.dtsi
	arch/arm64/boot/dts/amlogic/mesongxl.dtsi
	arch/arm64/boot/dts/amlogic/mesongxm.dtsi
	arch/arm64/boot/dts/amlogic/mesontxl.dtsi
	arch/arm64/boot/dts/amlogic/mesontxlx.dtsi
	drivers/amlogic/memory_ext/ram_dump.c
	include/linux/amlogic/ramdump.h

include/linux/amlogic/ramdump.h

@@ -20,7 +20,9 @@
 
 #define SET_REBOOT_REASON		0x82000049
 
-extern int ramdump_disabled(void);
+#define AMLOGIC_KERNEL_BOOTED		0x8000
+#define RAMDUMP_STICKY_DATA_MASK	0xFFFF
+
 extern void ramdump_sync_data(void);
 
 #endif /* __RAMDUMP_H__ */