android_kernel_zuk_msm8996.git

	Commit message (Collapse)	Author	Age
*	firmware: qcom: tz_log: update interrupt info offset	Zhen Kong	2017-06-28
\| \| \| \| \| \| \| \| \|	As interrupt info table is changed after TZ 4.0, update its offset according to TZ version when tz_log driver reads it. Change-Id: I28750a12b79a3920904c00fd52a2f4c7ffef7000 Signed-off-by: Zhen Kong <zkong@codeaurora.org>
*	Merge "firmware: qcom: tz_log: update datatype for int_count"	Linux Build Service Account	2017-03-21
\|\
\| *	firmware: qcom: tz_log: update datatype for int_count	Zhen Kong	2017-03-17
\| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \|	int_count variable datatype is uint64 in tz version 2.X/3.0, and is changed to uint32 in tz version >=4.X, so updating int_count according to the TZ version. Change-Id: I72e128e6ad41711fd49416faf6aebfc869187ee2 Signed-off-by: Zhen Kong <zkong@codeaurora.org>
* \|	firmware: tz_log: Enable asynchronous driver probing	Zhen Kong	2017-03-15
\|/ \| \| \| \| \| \| \| \|	Do asynchronous driver probing of TZ log driver to improve the device boot-up time. Change-Id: Ic972be12f820787db1a5bc957b109461354875fb Signed-off-by: AnilKumar Chimata <anilc@codeaurora.org> Signed-off-by: Zhen Kong <zkong@codeaurora.org>
*	firmware: qcom: tz_log: fix reading log issue on secure boot enabled device	Zhen Kong	2017-03-13
\| \| \| \| \| \| \| \| \| \| \| \|	Unlike other debug logs, qsee and hyp log buffer are separated from tz diag region, so it is not necessary to read tz diag region before reading qsee or hyp logs. Otherwise, when tz diag region is encrypted and locked on secure boot enabled devices, reading qsee or hyp logs will cause XPU violation at tz diag region. Also, update the diagnostic table with some new items. Change-Id: I2872c4dce876763b5dac5656a982f6ce29cc81f4 Signed-off-by: Zhen Kong <zkong@codeaurora.org>
*	firmware: qcom: tz_log: fix incorrect datatype for warm_jmp_addr.	Mallikarjuna Reddy Amireddy	2016-08-09
\| \| \| \| \| \| \| \| \| \| \|	warm_jmp_addr variable datatype is uint32 in tz version 2.X (32 -bit) and uint64 in tz version >=3.X (64 bit). But HLOS side always hadling with uint32. So this is causing mismatch data types between Tz and HLOS side, which is providing wrong 'Warmboot jump address'. So updating tzdbg_boot_info according to the TZ versions. Change-Id: I216f9d4407592ae0112902fe423a807ae3c146d0 Signed-off-by: Mallikarjuna Reddy Amireddy <mamire@codeaurora.org>
*	firmware: qcom: add snapshot of tz_log.c	Zhen Kong	2016-03-23
	This snapshot is taken as of msm-3.18 commit e70ad0cd (Promotion of kernel.lnx.3.18-151201.) Acked-by: Shabnam Aboughadareh <shabnama@qti.qualcomm.com> Signed-off-by: Zhen Kong <zkong@codeaurora.org>