From: James Clark <james.clark@linaro.org>
To: Suzuki K Poulose <suzuki.poulose@arm.com>
Cc: coresight@lists.linaro.org, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org,
linux-stm32@st-md-mailman.stormreply.com,
Mike Leach <mike.leach@linaro.org>,
Alexander Shishkin <alexander.shishkin@linux.intel.com>,
Maxime Coquelin <mcoquelin.stm32@gmail.com>,
Alexandre Torgue <alexandre.torgue@foss.st.com>,
leo.yan@arm.com
Subject: Re: [PATCH v2 2/8] coresight: Convert tag clear function to take a struct cs_access
Date: Wed, 19 Mar 2025 12:30:17 +0000 [thread overview]
Message-ID: <2700171e-dbaa-4218-9b46-5d181f5afee7@linaro.org> (raw)
In-Reply-To: <cc68d43f-4719-4f57-a38c-fb5afe8d29cc@arm.com>
On 19/03/2025 12:00 pm, Suzuki K Poulose wrote:
> On 18/03/2025 16:21, James Clark wrote:
>> The self hosted claim tag will be reset on device probe in a later
>> commit. We'll want to do this before coresight_register() is called so
>> won't have a coresight_device and have to use cs_access instead.
>>
>> Also make them public and create locked and unlocked versions for
>> later use.
>>
>> Signed-off-by: James Clark <james.clark@linaro.org>
>
> minor nit:
>
> The restructuring looks a bit confusing. Could we start with :
>
> coresight_{set,clear}_self_claim_tag_unlocked in Patch 1. Rather
> than rename what we renamed in patch 1 again here.
>
>
I considered collapsing these two actually, would you be ok with that?
>> ---
>> drivers/hwtracing/coresight/coresight-core.c | 17 +++++++++++++----
>> include/linux/coresight.h | 3 ++-
>> 2 files changed, 15 insertions(+), 5 deletions(-)
>>
>> diff --git a/drivers/hwtracing/coresight/coresight-core.c b/drivers/
>> hwtracing/coresight/coresight-core.c
>> index 3f1c996d668a..9ff601e2415a 100644
>> --- a/drivers/hwtracing/coresight/coresight-core.c
>> +++ b/drivers/hwtracing/coresight/coresight-core.c
>> @@ -151,12 +151,21 @@ static inline void
>> coresight_set_self_claim_tag(struct coresight_device *csdev)
>> isb();
>> }
>> -static inline void coresight_clear_self_claim_tag(struct
>> coresight_device *csdev)
>> +void coresight_clear_self_claim_tag(struct csdev_access *csa)
>> {
>> - csdev_access_relaxed_write32(&csdev->access,
>> CORESIGHT_CLAIM_SELF_HOSTED,
>> + CS_UNLOCK(csa->base);
>
> This looks to be hard coding MMIO based access ? Should we abstract it
> based on the csdev_access_** ?
>
>
> Suzuki
>
>
I did something similar earlier but it ended up being huge to do it
properly and I wasn't sure of the benefits so I deleted it. By
'properly' I mean change all of the CS_UNLOCK() calls to be abstracted
and delete etm4_cs_unlock() because CS_UNLOCK() would handle both. It
ends adding in an if and indirection for every lock/unlock for devices
that are never sysreg access anyway.
Because there's already this:
static void etm4_cs_unlock(struct etmv4_drvdata *drvdata,
struct csdev_access *csa)
{
if (csa->io_mem)
CS_UNLOCK(csa->base);
But yeah I can add the if into coresight_clear_self_claim_tag(),
although it technically doesn't do anything now because it's never
called by any devices that aren't MMIO. And then it makes
etm4_cs_unlock() stand out a bit because its not a core function when it
could be. But that's probably fine.
next prev parent reply other threads:[~2025-03-19 12:30 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-18 16:21 [PATCH v2 0/8] coresight: Clear self hosted claim tag on probe James Clark
2025-03-18 16:21 ` [PATCH v2 1/8] coresight: Rename coresight_{set,clear}_claim_tags() James Clark
2025-03-18 16:21 ` [PATCH v2 2/8] coresight: Convert tag clear function to take a struct cs_access James Clark
2025-03-19 8:24 ` Leo Yan
2025-03-19 12:00 ` Suzuki K Poulose
2025-03-19 12:30 ` James Clark [this message]
2025-03-18 16:21 ` [PATCH v2 3/8] coresight: Only check bottom two claim bits James Clark
2025-03-18 16:21 ` [PATCH v2 4/8] coresight: Add claim tag warnings and debug messages James Clark
2025-03-19 8:27 ` Leo Yan
2025-03-18 16:21 ` [PATCH v2 5/8] coresight: etm3x: Convert raw base pointer to struct coresight access James Clark
2025-03-19 8:30 ` Leo Yan
2025-03-18 16:22 ` [PATCH v2 6/8] coresight: Clear self hosted claim tag on probe James Clark
2025-03-19 9:13 ` Leo Yan
2025-03-18 16:22 ` [PATCH v2 7/8] coresight: Remove inlines from static function definitions James Clark
2025-03-19 8:36 ` Leo Yan
2025-03-18 16:22 ` [PATCH v2 8/8] coresight: Remove extern from function declarations James Clark
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=2700171e-dbaa-4218-9b46-5d181f5afee7@linaro.org \
--to=james.clark@linaro.org \
--cc=alexander.shishkin@linux.intel.com \
--cc=alexandre.torgue@foss.st.com \
--cc=coresight@lists.linaro.org \
--cc=leo.yan@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-stm32@st-md-mailman.stormreply.com \
--cc=mcoquelin.stm32@gmail.com \
--cc=mike.leach@linaro.org \
--cc=suzuki.poulose@arm.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®