[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <Z2VDPQMUH61THA8r@e129823.arm.com>
Date: Fri, 20 Dec 2024 10:13:17 +0000
From: Yeoreum Yun <yeoreum.yun@....com>
To: Mike Leach <mike.leach@...aro.org>
Cc: suzuki.poulose@....com, james.clark@...aro.org,
alexander.shishkin@...ux.intel.com, bigeasy@...utronix.de,
clrkwllms@...nel.org, rostedt@...dmis.org,
coresight@...ts.linaro.org, linux-arm-kernel@...ts.infradead.org,
linux-kernel@...r.kernel.org, linux-rt-devel@...ts.linux.dev
Subject: Re: [PATCH v3 2/9] coresight-etm4x: change etmv4_drvdata spinlock
type to raw_spinlock_t
Hi Mike.
> > diff --git a/drivers/hwtracing/coresight/coresight-config.h b/drivers/hwtracing/coresight/coresight-config.h
> > index 6ba013975741..b9ebc9fcfb7f 100644
> > --- a/drivers/hwtracing/coresight/coresight-config.h
> > +++ b/drivers/hwtracing/coresight/coresight-config.h
> > @@ -206,7 +206,7 @@ struct cscfg_feature_csdev {
> > const struct cscfg_feature_desc *feat_desc;
> > struct coresight_device *csdev;
> > struct list_head node;
> > - spinlock_t *drv_spinlock;
> > + raw_spinlock_t *drv_spinlock;
> > int nr_params;
> > struct cscfg_parameter_csdev *params_csdev;
> > int nr_regs;
>
> The above changes are not etm4x specific - should be in the previous patch.
Yes, However when this changes, etm4x should be changed at the same time
because of build failures.
That's why I modified this with etm4x where currenly cscfg is used only.
Thanks
Powered by blists - more mailing lists