From: Yuanfang Zhang <quic_yuanfang@quicinc.com>
To: Leo Yan <leo.yan@arm.com>
Cc: 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>,
<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>
Subject: Re: [PATCH v6 2/2] coresight: add coresight Trace Network On Chip driver
Date: Fri, 6 Jun 2025 17:20:21 +0800 [thread overview]
Message-ID: <b786f35a-c11b-45e8-877e-aa1996c09d3a@quicinc.com> (raw)
In-Reply-To: <20250603122504.GA8020@e132581.arm.com>
On 6/3/2025 8:25 PM, Leo Yan wrote:
> On Tue, Jun 03, 2025 at 11:22:58AM +0800, Yuanfang Zhang wrote:
>
> [...]
>
>> Using both dynamic and self-contained IDs within the same system can result in ID conflicts, which may cause decoding failures.
>
> If so, please follow up Suzuki's suggestion to expose Sysfs interface
> in TNOC device node.
>
> Leo
Done in patch V8.
prev parent reply other threads:[~2025-06-06 9:20 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-22 8:07 [PATCH v6 0/2] coresight: Add Coresight Trace Network On Chip driver Yuanfang Zhang
2025-05-22 8:07 ` [PATCH v6 1/2] dt-bindings: arm: Add device Trace Network On Chip definition Yuanfang Zhang
2025-05-22 8:07 ` [PATCH v6 2/2] coresight: add coresight Trace Network On Chip driver Yuanfang Zhang
2025-05-22 13:05 ` Leo Yan
2025-05-23 8:37 ` Yuanfang Zhang
2025-05-22 13:13 ` Suzuki K Poulose
2025-05-23 8:08 ` Yuanfang Zhang
2025-05-23 8:56 ` Leo Yan
2025-05-27 10:19 ` Suzuki K Poulose
2025-05-30 10:28 ` Yuanfang Zhang
2025-05-30 11:32 ` Suzuki K Poulose
2025-05-30 12:59 ` Leo Yan
2025-06-03 3:22 ` Yuanfang Zhang
2025-06-03 12:25 ` Leo Yan
2025-06-06 9:20 ` 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=b786f35a-c11b-45e8-877e-aa1996c09d3a@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=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