From: "Rob Herring (Arm)" <robh@kernel.org>
To: Yuanfang Zhang <yuanfang.zhang@oss.qualcomm.com>
Cc: coresight@lists.linaro.org, kernel@oss.qualcomm.com,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
devicetree@vger.kernel.org,
Suzuki K Poulose <suzuki.poulose@arm.com>,
linux-kernel@vger.kernel.org,
James Clark <james.clark@linaro.org>,
linux-arm-kernel@lists.infradead.org,
Alexander Shishkin <alexander.shishkin@linux.intel.com>,
linux-arm-msm@vger.kernel.org, Conor Dooley <conor+dt@kernel.org>,
Mike Leach <mike.leach@linaro.org>
Subject: Re: [PATCH v3 1/3] dt-bindings: arm: qcom: Add Coresight Interconnect TNOC
Date: Fri, 29 Aug 2025 12:50:47 -0500 [thread overview]
Message-ID: <175648984746.1068381.2779865131984484045.robh@kernel.org> (raw)
In-Reply-To: <20250828-itnoc-v3-1-f1b55dea7a27@oss.qualcomm.com>
On Thu, 28 Aug 2025 02:27:22 -0700, Yuanfang Zhang wrote:
> Add device tree binding for Qualcomm Coresight Interconnect Trace
> Network On Chip (ITNOC). This TNOC acts as a CoreSight
> graph link that forwards trace data from a subsystem to the
> Aggregator TNOC, without aggregation or ATID functionality.
>
> Signed-off-by: Yuanfang Zhang <yuanfang.zhang@oss.qualcomm.com>
> ---
> .../bindings/arm/qcom,coresight-itnoc.yaml | 90 ++++++++++++++++++++++
> 1 file changed, 90 insertions(+)
>
Reviewed-by: Rob Herring (Arm) <robh@kernel.org>
next prev parent reply other threads:[~2025-08-29 17:50 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-28 9:27 [PATCH v3 0/3] coresight-tnoc: Add support for " Yuanfang Zhang
2025-08-28 9:27 ` [PATCH v3 1/3] dt-bindings: arm: qcom: Add Coresight " Yuanfang Zhang
2025-08-29 17:50 ` Rob Herring (Arm) [this message]
2025-08-28 9:27 ` [PATCH v3 2/3] coresight-tnoc: add platform driver to support " Yuanfang Zhang
2025-08-29 8:24 ` Leo Yan
2025-08-28 9:27 ` [PATCH v3 3/3] coresight-tnoc: Add runtime PM support for " Yuanfang Zhang
2025-08-29 8:41 ` Leo Yan
2025-08-29 8:49 ` [PATCH v3 0/3] coresight-tnoc: Add " Leo Yan
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=175648984746.1068381.2779865131984484045.robh@kernel.org \
--to=robh@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=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=suzuki.poulose@arm.com \
--cc=yuanfang.zhang@oss.qualcomm.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®