Hi Mathieu,
On Mon, 26 Aug 2019 at 23:59, Mathieu Poirier mathieu.poirier@linaro.org wrote:
On Mon, Aug 19, 2019 at 09:57:15PM +0100, Mike Leach wrote:
TRCACATRn registers have match bits for secure and non-secure exception levels which are not accessible by the sysfs API. This adds a new sysfs parameter to enable this - addr_exlevel_s_ns.
Signed-off-by: Mike Leach mike.leach@linaro.org
.../coresight/coresight-etm4x-sysfs.c | 39 +++++++++++++++++++ 1 file changed, 39 insertions(+)
diff --git a/drivers/hwtracing/coresight/coresight-etm4x-sysfs.c b/drivers/hwtracing/coresight/coresight-etm4x-sysfs.c index fa1d6a938f6c..7eab5d7d0b62 100644 --- a/drivers/hwtracing/coresight/coresight-etm4x-sysfs.c +++ b/drivers/hwtracing/coresight/coresight-etm4x-sysfs.c @@ -1233,6 +1233,44 @@ static ssize_t addr_context_store(struct device *dev, } static DEVICE_ATTR_RW(addr_context);
+static ssize_t addr_exlevel_s_ns_show(struct device *dev,
struct device_attribute *attr,char *buf)+{
u8 idx;unsigned long val;struct etmv4_drvdata *drvdata = dev_get_drvdata(dev->parent);struct etmv4_config *config = &drvdata->config;spin_lock(&drvdata->spinlock);idx = config->addr_idx;val = BMVAL(config->addr_acc[idx], 14, 8);spin_unlock(&drvdata->spinlock);return scnprintf(buf, PAGE_SIZE, "%#lx\n", val);+}
+static ssize_t addr_exlevel_s_ns_store(struct device *dev,
struct device_attribute *attr,const char *buf, size_t size)+{
u8 idx;unsigned long val;struct etmv4_drvdata *drvdata = dev_get_drvdata(dev->parent);struct etmv4_config *config = &drvdata->config;if (kstrtoul(buf, 16, &val))return -EINVAL;spin_lock(&drvdata->spinlock);idx = config->addr_idx;/* clear Exlevel_ns & Exlevel_s bits[14:12, 11:8] */config->addr_acc[idx] &= ~(GENMASK(14, 8));config->addr_acc[idx] |= (val << 8);spin_unlock(&drvdata->spinlock);return size;+} +static DEVICE_ATTR_RW(addr_exlevel_s_ns);
static ssize_t seq_idx_show(struct device *dev, struct device_attribute *attr, char *buf) @@ -2038,6 +2076,7 @@ static struct attribute *coresight_etmv4_attrs[] = { &dev_attr_addr_stop.attr, &dev_attr_addr_ctxtype.attr, &dev_attr_addr_context.attr,
&dev_attr_addr_exlevel_s_ns.attr, &dev_attr_seq_idx.attr, &dev_attr_seq_state.attr, &dev_attr_seq_event.attr,I'm ok with this patch but the new entry needs to be documented in [1].
It is in a later patch.
But before moving forward with that I'm wondering if this is the way to go. Would it be better to consolidate type, ctxtype, context and exlevel_s_ns in a single entry, say addr_acc_type? We'd shed a fair amount of code and make it more simple for users to configure.
It will mean the user has less writes to do - but is it really simpler to understand?
At present each feature takes the input value and interprets / shifts it to set the relevant bits in the address comparator control registers (context type being a string input rather than bit values).
The alternative is to require the user to understand the bit values - which they may well do if they are referring to the ETM docs to program in this detail, and provide a correct input value for their requirements.
My addition adds to the API, rather than changes it, but if you prefer we could go with an update to a single feature to control this value in the comparator control registers.
Mike
[1]. Documentation/ABI/testing/sysfs-bus-coresight-devices-etm4x
-- 2.17.1