mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Yuanfang Zhang <quic_yuanfang@quicinc.com>
To: Suzuki K Poulose <suzuki.poulose@arm.com>,
	Mike Leach <mike.leach@linaro.org>,
	James Clark <james.clark@linaro.org>,
	Rob Herring <robh@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>,
	Alexander Shishkin <alexander.shishkin@linux.intel.com>
Cc: <kernel@oss.qualcomm.com>, <linux-arm-msm@vger.kernel.org>,
	<coresight@lists.linaro.org>,
	<linux-arm-kernel@lists.infradead.org>,
	<devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
	"Krzysztof Kozlowski" <krzysztof.kozlowski@linaro.org>,
	Leo Yan <leo.yan@arm.com>
Subject: Re: [PATCH v10 0/2] coresight: Add Coresight Trace Network On Chip driver
Date: Wed, 9 Jul 2025 16:25:23 +0800	[thread overview]
Message-ID: <c6cfc51b-ca0e-4eac-8462-00dcbc136afd@quicinc.com> (raw)
In-Reply-To: <20250611-trace-noc-v10-0-a83b5c63da34@quicinc.com>

On 6/11/2025 6:42 PM, Yuanfang Zhang wrote:
> The Trace Network On Chip (TNOC) is an integration hierarchy which is a
> hardware component that integrates the functionalities of TPDA and
> funnels. It collects trace from subsystems and transfers it to coresight
> sink.
> 
> In addition to the generic TNOC mentioned above, there is also a special type
> of TNOC called Interconnect TNOC. Unlike the generic TNOC, the Interconnect
> TNOC doesn't need ATID. Its primary function is to connect the source of
> subsystems to the Aggregator TNOC. Its driver is different from this patch and
> will describe it and upstream its driver separately.
> 
> Signed-off-by: Yuanfang Zhang <quic_yuanfang@quicinc.com>
> ---
> Changes in v10:
> - Rebase to coresight/next branch.
> - Link to v9: https://lore.kernel.org/r/20250611-trace-noc-v9-0-4322d4cf8f4b@quicinc.com
> 
> Changes in v9:
> - Mention the binding is only for Aggregator TNOC.
> - Link to v8: https://lore.kernel.org/r/20250606-trace-noc-v8-0-833f94712c57@quicinc.com
> 
> Changes in v8:
> - Add sysfs node to expose atid.
> - Link to v7: https://lore.kernel.org/r/20250523-trace-noc-v7-0-d65edbab2997@quicinc.com
> 
> Changes in v7:
> - Move the content in header file into coresight-tnoc.c.
> - Use scoped_guard() to replace spin_lock().
> - Invoke coresight_trace_id_put_system_id() for registration failure.
> - Link to v6: https://lore.kernel.org/r/20250522-trace-noc-v6-0-f5a9bcae90ee@quicinc.com
> 
> Changes in v6:
> - Add a newline after return statements.
> - Use 'x &= foo' to replace 'x = x & foo'.
> - Use 'x |= foo' to replace 'x = x | foo'.
> - Link to v5: https://lore.kernel.org/r/20250512-trace-noc-v5-0-f2ef070baee5@quicinc.com
> 
> Changes in v5:
> - update cover-letter to describe the Interconnect TNOC.
> - Link to v4: https://lore.kernel.org/r/20250415-trace-noc-v4-0-979938fedfd8@quicinc.com
> 
> Changes in v4:
> - Fix dt_binding warning.
> - update mask of trace_noc amba_id.
> - Modify driver comments.
> - rename TRACE_NOC_SYN_VAL to TRACE_NOC_SYNC_INTERVAL.
> - Link to v3: https://lore.kernel.org/r/20250411-trace-noc-v3-0-1f19ddf7699b@quicinc.com
> 
> Changes in v3:
> - Remove unnecessary sysfs nodes.
> - update commit messages.
> - Use 'writel' instead of 'write_relaxed' when writing to the register for the last time.
> - Add trace_id ops.
> - Link to v2: https://lore.kernel.org/r/20250226-trace-noc-driver-v2-0-8afc6584afc5@quicinc.com
> 
> Changes in v2:
> - Modified the format of DT binging file.
> - Fix compile warnings.
> - Link to v1: https://lore.kernel.org/r/46643089-b88d-49dc-be05-7bf0bb21f847@quicinc.com
> 
> ---
> Yuanfang Zhang (2):
>       dt-bindings: arm: Add device Trace Network On Chip definition
>       coresight: add coresight Trace Network On Chip driver
> 
>  .../bindings/arm/qcom,coresight-tnoc.yaml          | 113 ++++++++++
>  drivers/hwtracing/coresight/Kconfig                |  12 +
>  drivers/hwtracing/coresight/Makefile               |   1 +
>  drivers/hwtracing/coresight/coresight-tnoc.c       | 242 +++++++++++++++++++++
>  4 files changed, 368 insertions(+)
> ---
> base-commit: 408c97c4a5e0b634dcd15bf8b8808b382e888164
> change-id: 20250403-trace-noc-f8286b30408e
> 
> Best regards,

Hi Suzuki, Mike,

I wanted to check in on the status of this patch series ([v10 0/2]). I’d like to confirm whether
it is planned to be picked for this cycle, or if there’s anything further I should address.

thanks,
Yuanfang.

      parent reply	other threads:[~2025-07-09  8:25 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-11 10:42 Yuanfang Zhang
2025-06-11 10:42 ` [PATCH v10 1/2] dt-bindings: arm: Add device Trace Network On Chip definition Yuanfang Zhang
2025-07-11 13:50   ` Mike Leach
2025-06-11 10:42 ` [PATCH v10 2/2] coresight: add coresight Trace Network On Chip driver Yuanfang Zhang
2025-07-09 13:19   ` Suzuki K Poulose
2025-07-10  5:48     ` Yuanfang Zhang
2025-07-09  8:25 ` Yuanfang Zhang [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=c6cfc51b-ca0e-4eac-8462-00dcbc136afd@quicinc.com \
    --to=quic_yuanfang@quicinc.com \
    --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=krzk+dt@kernel.org \
    --cc=krzysztof.kozlowski@linaro.org \
    --cc=leo.yan@arm.com \
    --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=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

all inboxes | Powered by JetHome®