From: Suzuki K Poulose <suzuki.poulose@arm.com>
To: James Clark <james.clark@linaro.org>,
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
Cc: coresight@lists.linaro.org, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org,
linux-stm32@st-md-mailman.stormreply.com
Subject: Re: [PATCH v3 2/7] coresight: Only check bottom two claim bits
Date: Fri, 21 Mar 2025 12:10:47 +0000 [thread overview]
Message-ID: <40e30ec8-a7ea-46b9-b687-aa7efa8cf0e1@arm.com> (raw)
In-Reply-To: <20250320-james-coresight-claim-tags-v3-2-d3145c153820@linaro.org>
On 20/03/2025 14:34, James Clark wrote:
> The use of the whole register and == could break the claim mechanism if
> any of the other bits are used in the future. The referenced doc "PSCI -
> ARM DEN 0022D" also says to only read and clear the bottom two bits.
>
> Use FIELD_GET() to extract only the relevant part.
>
> Reviewed-by: Leo Yan <leo.yan@arm.com>
> Signed-off-by: James Clark <james.clark@linaro.org>
> ---
> drivers/hwtracing/coresight/coresight-core.c | 3 ++-
> drivers/hwtracing/coresight/coresight-priv.h | 1 +
> 2 files changed, 3 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/hwtracing/coresight/coresight-core.c b/drivers/hwtracing/coresight/coresight-core.c
> index 8471aefeac76..26d149a4c579 100644
> --- a/drivers/hwtracing/coresight/coresight-core.c
> +++ b/drivers/hwtracing/coresight/coresight-core.c
> @@ -131,7 +131,8 @@ coresight_find_out_connection(struct coresight_device *csdev,
>
> static inline u32 coresight_read_claim_tags(struct coresight_device *csdev)
> {
> - return csdev_access_relaxed_read32(&csdev->access, CORESIGHT_CLAIMCLR);
> + return FIELD_GET(CORESIGHT_CLAIM_MASK,
> + csdev_access_relaxed_read32(&csdev->access, CORESIGHT_CLAIMCLR));
> }
>
> static inline bool coresight_is_claimed_self_hosted(struct coresight_device *csdev)
> diff --git a/drivers/hwtracing/coresight/coresight-priv.h b/drivers/hwtracing/coresight/coresight-priv.h
> index 82644aff8d2b..38bb4e8b50ef 100644
> --- a/drivers/hwtracing/coresight/coresight-priv.h
> +++ b/drivers/hwtracing/coresight/coresight-priv.h
> @@ -35,6 +35,7 @@ extern const struct device_type coresight_dev_type[];
> * Coresight device CLAIM protocol.
> * See PSCI - ARM DEN 0022D, Section: 6.8.1 Debug and Trace save and restore.
> */
> +#define CORESIGHT_CLAIM_MASK GENMASK(1, 0)
> #define CORESIGHT_CLAIM_SELF_HOSTED BIT(1)
I am checking with the Arm CoreSight architects on this. This is
problematic, if another agent is assigned, say BIT(2) and we wouldn't
forward compatible.
Suzuki
>
> #define TIMEOUT_US 100
>
next prev parent reply other threads:[~2025-03-21 12:10 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
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 [this message]
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=40e30ec8-a7ea-46b9-b687-aa7efa8cf0e1@arm.com \
--to=suzuki.poulose@arm.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=alexandre.torgue@foss.st.com \
--cc=coresight@lists.linaro.org \
--cc=james.clark@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 \
/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