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 v3 1/7] coresight: Convert tag clear function to take a struct cs_access
Date: Tue, 25 Mar 2025 12:00:00 +0000 [thread overview]
Message-ID: <47e8486c-7d7a-46cf-a4e1-9420a3be4357@linaro.org> (raw)
In-Reply-To: <2d3fb704-172c-4632-9e95-02bbfb8c0f90@arm.com>
On 21/03/2025 12:42 pm, Suzuki K Poulose wrote:
> On 21/03/2025 11:02, Suzuki K Poulose wrote:
>> On 20/03/2025 14:34, 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.
>>>
>>> These look functions look like they set the whole tags register as one
>>> value, but they only set and clear the self hosted bit using a SET/CLR
>>> bits mechanism so also rename the functions to reflect this better.
>>>
>>> Reviewed-by: Leo Yan <leo.yan@arm.com>
>>> Signed-off-by: James Clark <james.clark@linaro.org>
>>> ---
>>> drivers/hwtracing/coresight/coresight-core.c | 27 +++++++++++++++++
>>> + +--------
>>> include/linux/coresight.h | 3 ++-
>>> 2 files changed, 21 insertions(+), 9 deletions(-)
>>>
>>> diff --git a/drivers/hwtracing/coresight/coresight-core.c b/drivers/
>>> hwtracing/coresight/coresight-core.c
>>> index fb43ef6a3b1f..8471aefeac76 100644
>>> --- a/drivers/hwtracing/coresight/coresight-core.c
>>> +++ b/drivers/hwtracing/coresight/coresight-core.c
>>> @@ -144,19 +144,30 @@ static inline bool
>>> coresight_is_claimed_any(struct coresight_device *csdev)
>>> return coresight_read_claim_tags(csdev) != 0;
>>> }
>>> -static inline void coresight_set_claim_tags(struct coresight_device
>>> *csdev)
>>> +static inline void coresight_set_self_claim_tag(struct
>>> coresight_device *csdev)
>>
>> nit: For consistency, this should be renamed to _unlocked ?
>>
>
> minor nit on the subject;
>
> s/cs_access/csdev_access/
>
> Suzuki
>
>
>>
>
> Rest looks fine to me
Fixed those two in v4, thanks.
next prev parent reply other threads:[~2025-03-25 12:00 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-20 14:34 [PATCH v3 0/7] coresight: Clear self hosted claim tag on probe James Clark
2025-03-20 14:34 ` [PATCH v3 1/7] coresight: Convert tag clear function to take a struct cs_access James Clark
2025-03-21 11:02 ` Suzuki K Poulose
2025-03-21 12:42 ` Suzuki K Poulose
2025-03-25 12:00 ` James Clark [this message]
2025-03-20 14:34 ` [PATCH v3 2/7] coresight: Only check bottom two claim bits James Clark
2025-03-21 12:10 ` Suzuki K Poulose
2025-03-25 13:47 ` James Clark
2025-03-20 14:34 ` [PATCH v3 3/7] coresight: Add claim tag warnings and debug messages James Clark
2025-03-20 14:34 ` [PATCH v3 4/7] coresight: etm3x: Convert raw base pointer to struct coresight access James Clark
2025-03-20 14:34 ` [PATCH v3 5/7] coresight: Clear self hosted claim tag on probe James Clark
2025-03-20 14:34 ` [PATCH v3 6/7] coresight: Remove inlines from static function definitions James Clark
2025-03-20 14:34 ` [PATCH v3 7/7] coresight: Remove extern from function declarations James Clark
2025-03-20 15:48 ` [PATCH v3 0/7] coresight: Clear self hosted claim tag on probe Yeoreum Yun
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=47e8486c-7d7a-46cf-a4e1-9420a3be4357@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