I was working on refactoring some of the magic numbers for the register accesses and I saw this issue with programming one of the values.
I don't have any evidence that someone encountered it not working, probably there is no hardware where QSUPP==0b10, or it just didn't get used yet. But the issue is that this silently writes a reserved value even if the user provided one was correct so it might ruin someones day if it ever comes up.
It's a small change so I didn't see the harm in fixing it.
Applies to coresight/next f9809d565135
James Clark (1): coresight: Fix TRCCONFIGR.QE sysfs interface
drivers/hwtracing/coresight/coresight-etm4x-sysfs.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)