From: Tao Zhang <quic_taozha@quicinc.com>
To: Suzuki K Poulose <suzuki.poulose@arm.com>,
Mathieu Poirier <mathieu.poirier@linaro.org>,
Alexander Shishkin <alexander.shishkin@linux.intel.com>,
Konrad Dybcio <konradybcio@gmail.com>,
Mike Leach <mike.leach@linaro.org>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>
Cc: Jinlong Mao <quic_jinlmao@quicinc.com>,
Leo Yan <leo.yan@linaro.org>,
"Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
<coresight@lists.linaro.org>,
<linux-arm-kernel@lists.infradead.org>,
<linux-kernel@vger.kernel.org>, <devicetree@vger.kernel.org>,
Tingwei Zhang <quic_tingweiz@quicinc.com>,
Yuanfang Zhang <quic_yuanfang@quicinc.com>,
Trilok Soni <quic_tsoni@quicinc.com>,
Song Chai <quic_songchai@quicinc.com>,
<linux-arm-msm@vger.kernel.org>, <andersson@kernel.org>
Subject: Re: [PATCH v3 3/8] coresight-tpdm: Add CMB dataset support
Date: Wed, 20 Dec 2023 16:56:42 +0800 [thread overview]
Message-ID: <0d4e2aa7-23e3-4851-bc43-80e7737f3a1a@quicinc.com> (raw)
In-Reply-To: <df433a15-2698-4e1f-9d15-db52befb7541@arm.com>
On 12/19/2023 9:56 PM, Suzuki K Poulose wrote:
> On 19/12/2023 09:22, Tao Zhang wrote:
>>
>> On 12/18/2023 6:34 PM, Suzuki K Poulose wrote:
>>> On 21/11/2023 02:24, Tao Zhang wrote:
>>>> CMB (continuous multi-bit) is one of TPDM's dataset type. CMB subunit
>>>> can be enabled for data collection by writing 1 to the first bit of
>>>> CMB_CR register. This change is to add enable/disable function for
>>>> CMB dataset by writing CMB_CR register.
>>>>
>>>> Reviewed-by: James Clark <james.clark@arm.com>
>>>> Signed-off-by: Tao Zhang <quic_taozha@quicinc.com>
>>>> Signed-off-by: Jinlong Mao <quic_jinlmao@quicinc.com>
>>>> ---
>>>> drivers/hwtracing/coresight/coresight-tpdm.c | 31
>>>> ++++++++++++++++++++
>>>> drivers/hwtracing/coresight/coresight-tpdm.h | 8 +++++
>>>> 2 files changed, 39 insertions(+)
>>>>
>>>> diff --git a/drivers/hwtracing/coresight/coresight-tpdm.c
>>>> b/drivers/hwtracing/coresight/coresight-tpdm.c
>>>> index 97654aa4b772..c8bb38822e08 100644
>>>> --- a/drivers/hwtracing/coresight/coresight-tpdm.c
>>>> +++ b/drivers/hwtracing/coresight/coresight-tpdm.c
>>>> @@ -131,6 +131,11 @@ static bool tpdm_has_dsb_dataset(struct
>>>> tpdm_drvdata *drvdata)
>>>> return (drvdata->datasets & TPDM_PIDR0_DS_DSB);
>>>> }
>>>> +static bool tpdm_has_cmb_dataset(struct tpdm_drvdata *drvdata)
>>>> +{
>>>> + return (drvdata->datasets & TPDM_PIDR0_DS_CMB);
>>>> +}
>>>> +
>>>> static umode_t tpdm_dsb_is_visible(struct kobject *kobj,
>>>> struct attribute *attr, int n)
>>>> {
>>>> @@ -267,6 +272,17 @@ static void tpdm_enable_dsb(struct
>>>> tpdm_drvdata *drvdata)
>>>> writel_relaxed(val, drvdata->base + TPDM_DSB_CR);
>>>> }
>>>> +static void tpdm_enable_cmb(struct tpdm_drvdata *drvdata)
>>>> +{
>>>> + u32 val;
>>>> +
>>>> + val = readl_relaxed(drvdata->base + TPDM_CMB_CR);
>>>> + val |= TPDM_CMB_CR_ENA;
>>>> +
>>>> + /* Set the enable bit of CMB control register to 1 */
>>>> + writel_relaxed(val, drvdata->base + TPDM_CMB_CR);
>>>> +}
>>>> +
>>>> /*
>>>> * TPDM enable operations
>>>> * The TPDM or Monitor serves as data collection component for
>>>> various
>>>> @@ -281,6 +297,8 @@ static void __tpdm_enable(struct tpdm_drvdata
>>>> *drvdata)
>>>> if (tpdm_has_dsb_dataset(drvdata))
>>>> tpdm_enable_dsb(drvdata);
>>>> + if (tpdm_has_cmb_dataset(drvdata))
>>>> + tpdm_enable_cmb(drvdata);
>>>
>>> Don't we need to add this check in the "property read" section ?
>>> Otherwise, we could generate warnings unnecessarily ?
>>>
>>> i.e, if (tpdm_has_cmb_..())
>>> rc |= fwnode_..read_property(cmb-elem-size...)
>>>
>>> Similarly for DSB.
>>
>> TPDM and TPDA are two independent hardware. If you want to modify
>> them in this way, the
>>
>
> You don't have to, as long as the header files are included ?
>
> Read my response in the other patch, where it applies.
Got it. I will update in the next patch series.
Best,
Tao
>
> Suzuki
>
>> two independent drivers will be coupled to each other. At the same
>> time, this configuration
>>
>> is manually set in the devicetree by the users, and this check cannot
>> avoid manual setting errors.
>>
>> Even if the configuration is wrong, it will not cause the driver to
>> stop working, it will only cause
>>
>> the data to be lost from the TPDM.
>>
>>>
>>>> CS_LOCK(drvdata->base);
>>>> }
>>>> @@ -314,6 +332,17 @@ static void tpdm_disable_dsb(struct
>>>> tpdm_drvdata *drvdata)
>>>> writel_relaxed(val, drvdata->base + TPDM_DSB_CR);
>>>> }
>>>> +static void tpdm_disable_cmb(struct tpdm_drvdata *drvdata)
>>>> +{
>>>> + u32 val;
>>>> +
>>>> + val = readl_relaxed(drvdata->base + TPDM_CMB_CR);
>>>> + val &= ~TPDM_CMB_CR_ENA;
>>>> +
>>>> + /* Set the enable bit of CMB control register to 0 */
>>>> + writel_relaxed(val, drvdata->base + TPDM_CMB_CR);
>>>> +}
>>>> +
>>>> /* TPDM disable operations */
>>>> static void __tpdm_disable(struct tpdm_drvdata *drvdata)
>>>> {
>>>> @@ -321,6 +350,8 @@ static void __tpdm_disable(struct tpdm_drvdata
>>>> *drvdata)
>>>> if (tpdm_has_dsb_dataset(drvdata))
>>>> tpdm_disable_dsb(drvdata);
>>>> + if (tpdm_has_cmb_dataset(drvdata))
>>>> + tpdm_disable_cmb(drvdata);
>>>
>>> minor nit: Instead of having these :
>>>
>>> if (tpdm_has_XY_()
>>> tpdm_{enable/disable}_XY_()
>>> I prefer :
>>>
>>> tpdm_{enable/disable}_XY_
>>>
>>> and the helper take care of returning early if the feature is
>>> not present.
>> Does the following sample modification meet your expectation?
>> static void tpdm_disable_dsb(struct tpdm_drvdata *drvdata)
>> {
>> u32 val;
>>
>> if (tpdm_has_dsb_dataset(drvdata)) {
>> /* Set the enable bit of DSB control register to 0 */
>> val = readl_relaxed(drvdata->base + TPDM_DSB_CR);
>> val &= ~TPDM_DSB_CR_ENA;
>> writel_relaxed(val, drvdata->base + TPDM_DSB_CR);
>> }
>> }
>>
>> static void tpdm_disable_cmb(struct tpdm_drvdata *drvdata)
>> {
>> u32 val;
>>
>> if (tpdm_has_cmb_dataset(drvdata)) {
>> val = readl_relaxed(drvdata->base + TPDM_CMB_CR);
>> val &= ~TPDM_CMB_CR_ENA;
>>
>> /* Set the enable bit of CMB control register to 0 */
>> writel_relaxed(val, drvdata->base + TPDM_CMB_CR);
>> }
>> }
>>
>> /* TPDM disable operations */
>> static void __tpdm_disable(struct tpdm_drvdata *drvdata)
>> {
>> CS_UNLOCK(drvdata->base);
>>
>> tpdm_disable_dsb(drvdata);
>> tpdm_disable_cmb(drvdata);
>>
>
> Yes, thats exactly I was looking for.
Got it. I will update in the next patch series.
Best,
Tao
>
>> CS_LOCK(drvdata->base);
>>
>> }
>>
>>
>> Best,
>>
>> Tao
>>
>>>
>>>
>>> Suzuki
>>>
>>>
>>>> CS_LOCK(drvdata->base);
>>>> }
>>>> diff --git a/drivers/hwtracing/coresight/coresight-tpdm.h
>>>> b/drivers/hwtracing/coresight/coresight-tpdm.h
>>>> index 4115b2a17b8d..0098c58dfdd6 100644
>>>> --- a/drivers/hwtracing/coresight/coresight-tpdm.h
>>>> +++ b/drivers/hwtracing/coresight/coresight-tpdm.h
>>>> @@ -9,6 +9,12 @@
>>>> /* The max number of the datasets that TPDM supports */
>>>> #define TPDM_DATASETS 7
>>>> +/* CMB Subunit Registers */
>>>> +#define TPDM_CMB_CR (0xA00)
>>>> +
>>>> +/* Enable bit for CMB subunit */
>>>> +#define TPDM_CMB_CR_ENA BIT(0)
>>>> +
>>>> /* DSB Subunit Registers */
>>>> #define TPDM_DSB_CR (0x780)
>>>> #define TPDM_DSB_TIER (0x784)
>>>> @@ -79,10 +85,12 @@
>>>> *
>>>> * PERIPHIDR0[0] : Fix to 1 if ImplDef subunit present, else 0
>>>> * PERIPHIDR0[1] : Fix to 1 if DSB subunit present, else 0
>>>> + * PERIPHIDR0[2] : Fix to 1 if CMB subunit present, else 0
>>>> */
>>>> #define TPDM_PIDR0_DS_IMPDEF BIT(0)
>>>> #define TPDM_PIDR0_DS_DSB BIT(1)
>>>> +#define TPDM_PIDR0_DS_CMB BIT(2)
>>>> #define TPDM_DSB_MAX_LINES 256
>>>> /* MAX number of EDCR registers */
>>>
>
next prev parent reply other threads:[~2023-12-20 8:57 UTC|newest]
Thread overview: 54+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-21 2:24 [PATCH v3 0/8] Add support to configure TPDM CMB subunit Tao Zhang
2023-11-21 2:24 ` [PATCH v3 1/8] dt-bindings: arm: Add support for CMB element size Tao Zhang
2023-11-21 7:24 ` Krzysztof Kozlowski
2023-12-19 0:14 ` Tao Zhang
2023-12-15 11:19 ` James Clark
2023-12-18 9:21 ` Tao Zhang
2023-11-21 2:24 ` [PATCH v3 2/8] coresight-tpda: Add support to configure CMB element Tao Zhang
2023-12-15 11:20 ` James Clark
2023-12-18 10:27 ` Suzuki K Poulose
2023-12-19 2:13 ` Tao Zhang
2023-12-19 13:54 ` Suzuki K Poulose
2023-12-20 0:27 ` Tao Zhang
2023-12-19 13:59 ` Suzuki K Poulose
2023-12-20 8:55 ` Tao Zhang
2023-11-21 2:24 ` [PATCH v3 3/8] coresight-tpdm: Add CMB dataset support Tao Zhang
2023-12-18 10:34 ` Suzuki K Poulose
2023-12-19 9:22 ` Tao Zhang
2023-12-19 13:56 ` Suzuki K Poulose
2023-12-20 8:56 ` Tao Zhang [this message]
2023-11-21 2:24 ` [PATCH v3 4/8] coresight-tpdm: Add support to configure CMB Tao Zhang
2023-11-21 2:24 ` [PATCH v3 5/8] coresight-tpdm: Add pattern registers support for CMB Tao Zhang
2023-11-21 2:24 ` [PATCH v3 6/8] coresight-tpdm: Add timestamp control register support for the CMB Tao Zhang
2023-12-18 10:46 ` Suzuki K Poulose
2023-12-19 2:43 ` Tao Zhang
2023-12-19 13:51 ` Suzuki K Poulose
2023-12-20 9:51 ` Tao Zhang
2023-12-20 11:07 ` Suzuki K Poulose
2023-12-25 1:55 ` Tao Zhang
2023-12-30 9:39 ` Suzuki K Poulose
2024-01-05 7:49 ` Tao Zhang
2024-01-08 10:42 ` Suzuki K Poulose
2024-01-12 2:42 ` Tao Zhang
2024-01-12 9:29 ` Suzuki K Poulose
2023-11-21 2:24 ` [PATCH v3 7/8] dt-bindings: arm: Add support for TPDM CMB MSR register Tao Zhang
2023-11-21 7:24 ` Krzysztof Kozlowski
2023-12-18 10:47 ` Suzuki K Poulose
2023-12-18 11:23 ` Tingwei Zhang
2023-12-18 11:56 ` Suzuki K Poulose
2023-12-18 12:17 ` Jinlong Mao
2023-12-19 10:27 ` Jinlong Mao
2023-11-21 2:24 ` [PATCH v3 8/8] coresight-tpdm: Add msr register support for CMB Tao Zhang
2023-12-15 11:24 ` James Clark
2023-12-18 11:02 ` Suzuki K Poulose
2023-12-19 6:58 ` Tao Zhang
2023-12-19 14:09 ` Suzuki K Poulose
2023-12-20 9:06 ` Tao Zhang
2024-01-12 9:12 ` Tao Zhang
2024-01-12 9:43 ` Suzuki K Poulose
2024-01-15 6:20 ` Tao Zhang
2024-01-15 9:20 ` Suzuki K Poulose
2024-01-15 14:15 ` Tao Zhang
2024-01-15 9:55 ` James Clark
2024-01-15 9:57 ` James Clark
2024-01-12 11:57 ` [PATCH v3 0/8] Add support to configure TPDM CMB subunit Suzuki K Poulose
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=0d4e2aa7-23e3-4851-bc43-80e7737f3a1a@quicinc.com \
--to=quic_taozha@quicinc.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=andersson@kernel.org \
--cc=coresight@lists.linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=konradybcio@gmail.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=leo.yan@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mathieu.poirier@linaro.org \
--cc=mike.leach@linaro.org \
--cc=quic_jinlmao@quicinc.com \
--cc=quic_songchai@quicinc.com \
--cc=quic_tingweiz@quicinc.com \
--cc=quic_tsoni@quicinc.com \
--cc=quic_yuanfang@quicinc.com \
--cc=robh+dt@kernel.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