From: Krzysztof Kozlowski <krzk@kernel.org>
To: Yuanfang Zhang <quic_yuanfang@quicinc.com>,
Suzuki K Poulose <suzuki.poulose@arm.com>,
Mike Leach <mike.leach@linaro.org>,
James Clark <james.clark@linaro.org>,
Alexander Shishkin <alexander.shishkin@linux.intel.com>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>
Cc: kernel@quicinc.com, linux-kernel@vger.kernel.org,
coresight@lists.linaro.org, linux-arm-kernel@lists.infradead.org,
kernel@oss.qualcomm.com, linux-arm-msm@vger.kernel.org,
devicetree@vger.kernel.org
Subject: Re: [PATCH v2 5/5] coresight-tnoc: add nodes to configure freq packet
Date: Wed, 26 Feb 2025 12:12:15 +0100 [thread overview]
Message-ID: <6f01269a-bd64-46e7-800f-d8d59c4bf72e@kernel.org> (raw)
In-Reply-To: <20250226-trace-noc-driver-v2-5-8afc6584afc5@quicinc.com>
On 26/02/2025 12:05, Yuanfang Zhang wrote:
> Three nodes for freq packet config are added here:
>
> 1. freq_type: used to set the type of issued ATB FREQ packets.
> 0: 'FREQ' packets; 1: 'FREQ_TS' packets.
>
> 2. freq_req_val: used to set frequency values carried by 'FREQ'
> and 'FREQ_TS' packets.
>
> 3. freq_ts_req: writing '1' to issue a 'FREQ' or 'FREQ_TS' packet.
>
> Signed-off-by: Yuanfang Zhang <quic_yuanfang@quicinc.com>
> ---
> drivers/hwtracing/coresight/coresight-tnoc.c | 97 ++++++++++++++++++++++++++++
> 1 file changed, 97 insertions(+)
>
> diff --git a/drivers/hwtracing/coresight/coresight-tnoc.c b/drivers/hwtracing/coresight/coresight-tnoc.c
> index ad973749250644760adc4dfd855240026d0a744c..24b1add4c921866b944d756e563d50b4172d583a 100644
> --- a/drivers/hwtracing/coresight/coresight-tnoc.c
> +++ b/drivers/hwtracing/coresight/coresight-tnoc.c
> @@ -112,10 +112,107 @@ static ssize_t flag_type_show(struct device *dev,
> }
> static DEVICE_ATTR_RW(flag_type);
>
> +static ssize_t freq_type_show(struct device *dev,
> + struct device_attribute *attr,
> + char *buf)
> +{
> + struct trace_noc_drvdata *drvdata = dev_get_drvdata(dev->parent);
> +
> + return sysfs_emit(buf, "%u\n", drvdata->freq_type);
> +}
> +
> +static ssize_t freq_type_store(struct device *dev,
> + struct device_attribute *attr,
> + const char *buf,
> + size_t size)
No improvements. You got here comments and you got also later my
complain that yo missed comments already.
You keep ignoring received feedback and that's a no go for me.
Maybe process needs to be improved, so reach to your colleagues and
learn how to interact with upstream. There is very comprehensive
internal guideline in Qualcomm, so follow it carefully.
I expect still to respond to my original comment or implement it fully.
Best regards,
Krzysztof
prev parent reply other threads:[~2025-02-26 11:12 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-26 11:05 [PATCH v2 0/5] coresight: Add Coresight Trace NOC driver Yuanfang Zhang
2025-02-26 11:05 ` [PATCH v2 1/5] dt-bindings: arm: Add Coresight device Trace NOC definition Yuanfang Zhang
2025-02-26 11:09 ` Krzysztof Kozlowski
2025-02-26 11:16 ` Yuanfang Zhang
2025-02-26 11:20 ` Krzysztof Kozlowski
2025-02-26 11:05 ` [PATCH v2 2/5] coresight: add coresight Trace NOC driver Yuanfang Zhang
2025-02-27 11:39 ` Leo Yan
2025-03-06 8:22 ` Yuanfang Zhang
2025-03-10 11:02 ` Leo Yan
2025-04-03 7:40 ` Yuanfang Zhang
2025-04-07 15:47 ` Mike Leach
2025-04-08 11:35 ` Yuanfang Zhang
2025-02-26 11:05 ` [PATCH v2 3/5] coresight-tnoc: add nodes to configure flush Yuanfang Zhang
2025-02-27 16:23 ` Leo Yan
2025-03-06 8:39 ` Yuanfang Zhang
2025-03-10 11:46 ` Leo Yan
2025-02-26 11:05 ` [PATCH v2 4/5] coresight-tnoc: add node to configure flag type Yuanfang Zhang
2025-02-26 11:05 ` [PATCH v2 5/5] coresight-tnoc: add nodes to configure freq packet Yuanfang Zhang
2025-02-26 11:12 ` Krzysztof Kozlowski [this message]
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=6f01269a-bd64-46e7-800f-d8d59c4bf72e@kernel.org \
--to=krzk@kernel.org \
--cc=alexander.shishkin@linux.intel.com \
--cc=conor+dt@kernel.org \
--cc=coresight@lists.linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=james.clark@linaro.org \
--cc=kernel@oss.qualcomm.com \
--cc=kernel@quicinc.com \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mike.leach@linaro.org \
--cc=quic_yuanfang@quicinc.com \
--cc=robh@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;
as well as URLs for NNTP newsgroup(s).