evie/android_kernel_oneplus_msm8998
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

coresight-etm4x: use trace ids starting 0x1 for ETMs devices

Browse source 
ETM parser expects ETM trace ids starting from 0x1.

This change fixes the start of ETM trace id to make it compatible with
ETM parser.

Change-Id: Icc5c6de317468b845448dae22a447e8b9a82ea54
Signed-off-by: Shashank Mittal <mittals@codeaurora.org>
This commit is contained in:
Shashank Mittal 2016-03-09 16:46:34 -08:00 • committed by David Keitel
parent 22867419a7
commit 1f99478c12
1 changed files with 2 additions and 4 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

6
drivers/hwtracing/coresight/coresight-etm4x.c
View file

@ -2543,11 +2543,9 @@ static void etm4_init_default_data(struct etmv4_drvdata *drvdata)
drvdata->vmid_mask1 = 0x0;
/*
* A trace ID value of 0 is invalid, so let's start at some
* random value that fits in 7 bits. ETMv3.x has 0x10 so let's
* start at 0x20.
* Start trace id from 0x1.
*/
drvdata->trcid = 0x20 + drvdata->cpu;
drvdata->trcid = 0x1 + drvdata->cpu;
}
static int etm4_late_init(struct etmv4_drvdata *drvdata)