PD#SWPL-175587
Problem:
arm64 aml_flush_cache_all will corrupt some regs
Solution:
save and restore corrupted registers in flush cache
Verify:
S7D
Change-Id: I6e9d7edc4643fa340c592806f725d37666a0b8a6
Signed-off-by: song.han <song.han@amlogic.com>
PD#SWPL-165513
Problem:
Autosuspend can't resume when connect usb disk
and enable ramdump.
Solution:
Optimize the DDR cleaning strategy:
1.delay 120s to clean up memory.
2.stop cleaning when the remaining free size
drops to 10%.
Verify:
on t7c
Change-Id: I93e64706e1a39a7e37f3a7dd4afb081c687c1f9f
Signed-off-by: dongqing.li <dongqing.li@amlogic.com>
PD#SWPL-148227
Problem:
The crash file of ramdump cannot be parsed properly.
Solution:
1. Delay 60 seconds to clear DDR
2. Optimize print output to help parse crash files.
3. Reduce the func jump level of flush cache all.
Verify:
sc2
Change-Id: Ib82725cf2c22eb3ef9c7257cedbdfa718acd5ad9
Signed-off-by: dongqing.li <dongqing.li@amlogic.com>
PD#SWPL-132538
Problem:
The core-dump file cannot be saved to /data in Android.
Solution:
a. Fix BUG for bad page state when lazy_clear_work is running.
b. Print the parameter infor required for the crash tools.
c. Support for storing crashdump files in Android /data/vender/ramdump/
1) When a kernel panic occurs, flush cache all.
2) Restart to uboot stage and compress the full DDR.
3) Set kernel dts rsv mem based on compressed infor.
4) Crop reserved memory sub nodes to reduce mem usage.
5) Kernel stage parsing dts to configure rsv mem.
6) Android init.rc read sysnode, and generate crash file.
Verify:
sc2_ah212
Change-Id: Ic6fba2c305f9e3171445f3b89afa02c75c27a080
Signed-off-by: dongqing.li <dongqing.li@amlogic.com>
PD#SWPL-137107
Problem:
The data in the ramdump crash file is abnormal
because the cache data has not been flushed back.
Solution:
1. Use ipi_stop hook to flush online cpu cache.
2. Use panic_notifier to flush panic cpu cache.
Verify:
sc2_ah212
Change-Id: Ifad5bd4203fdde327b8c2b19357aa2d92586063f
Signed-off-by: dongqing.li <dongqing.li@amlogic.com>
song.han