[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <20220114173254.1876151-1-james.clark@arm.com>
Date: Fri, 14 Jan 2022 17:32:53 +0000
From: James Clark <james.clark@....com>
To: mathieu.poirier@...aro.org, coresight@...ts.linaro.org
Cc: suzuki.poulose@....com, James Clark <james.clark@....com>,
Mike Leach <mike.leach@...aro.org>,
Leo Yan <leo.yan@...aro.org>,
linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org
Subject: [PATCH 0/1] coresight: Fix TRCCONFIGR.QE sysfs interface
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(-)
--
2.17.1
Powered by blists - more mailing lists