From: Suzuki K Poulose <suzuki.poulose@arm.com>
To: Jie Gan <jie.gan@oss.qualcomm.com>,
Mike Leach <mike.leach@linaro.org>,
James Clark <james.clark@linaro.org>,
Alexander Shishkin <alexander.shishkin@linux.intel.com>,
Tingwei Zhang <tingwei.zhang@oss.qualcomm.com>
Cc: coresight@lists.linaro.org, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, linux-arm-msm@vger.kernel.org
Subject: Re: [PATCH v3 0/3] add sysfs nodes to configure TPDA's registers
Date: Mon, 27 Oct 2025 09:29:58 +0000 [thread overview]
Message-ID: <d71e09ff-c063-46d9-8d02-f69c18b6efe5@arm.com> (raw)
In-Reply-To: <b5762a05-8b63-4354-925e-fa3c8296e19f@oss.qualcomm.com>
On 27/10/2025 01:14, Jie Gan wrote:
>
>
> On 8/27/2025 6:55 PM, Jie Gan wrote:
>> Patchset 1 introduces configuration of the cross-trigger registers with
>> appropriate values to enable proper generation of cross-trigger packets.
>>
>> Patchset 2 introduces a logic to configure the TPDA_SYNCR register,
>> which determines the frequency of ASYNC packet generation. These packets
>> assist userspace tools in accurately identifying each valid packet.
>>
>> Patchset 3 introduces a sysfs node to initiate a flush request for the
>> specific port, forcing the data to synchronize and be transmitted to the
>> sink device.
>>
>
> Gentle reminder.
Please could you fix the dates and version to v6.19 ?
Suzuki
>
> Thanks,
> Jie
>
>> Changes in V3:
>> 1. Optimizing codes according to James's comment.
>> Link to V2 - https://lore.kernel.org/all/20250827042042.6786-1-
>> jie.gan@oss.qualcomm.com/
>>
>> Changes in V2:
>> 1. Refactoring the code based on James's comment for optimization.
>> Link to V1 - https://lore.kernel.org/all/20250826070150.5603-1-
>> jie.gan@oss.qualcomm.com/
>>
>> Tao Zhang (3):
>> coresight: tpda: add sysfs nodes for tpda cross-trigger configuration
>> coresight: tpda: add logic to configure TPDA_SYNCR register
>> coresight: tpda: add sysfs node to flush specific port
>>
>> .../testing/sysfs-bus-coresight-devices-tpda | 50 ++++
>> drivers/hwtracing/coresight/coresight-tpda.c | 278 ++++++++++++++++++
>> drivers/hwtracing/coresight/coresight-tpda.h | 33 ++-
>> 3 files changed, 360 insertions(+), 1 deletion(-)
>> create mode 100644 Documentation/ABI/testing/sysfs-bus-coresight-
>> devices-tpda
>>
>
next prev parent reply other threads:[~2025-10-27 9:30 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-27 10:55 [PATCH v3 0/3] add sysfs nodes to configure TPDA's registers Jie Gan
2025-08-27 10:55 ` [PATCH v3 1/3] coresight: tpda: add sysfs nodes for tpda cross-trigger configuration Jie Gan
2025-08-27 10:55 ` [PATCH v3 2/3] coresight: tpda: add logic to configure TPDA_SYNCR register Jie Gan
2025-08-27 10:55 ` [PATCH v3 3/3] coresight: tpda: add sysfs node to flush specific port Jie Gan
2025-08-27 11:59 ` [PATCH v3 0/3] add sysfs nodes to configure TPDA's registers James Clark
2025-09-15 2:12 ` Jie Gan
2025-10-13 8:25 ` Jie Gan
2025-10-27 1:14 ` Jie Gan
2025-10-27 9:29 ` Suzuki K Poulose [this message]
2025-10-28 1:37 ` Jie Gan
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=d71e09ff-c063-46d9-8d02-f69c18b6efe5@arm.com \
--to=suzuki.poulose@arm.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=coresight@lists.linaro.org \
--cc=james.clark@linaro.org \
--cc=jie.gan@oss.qualcomm.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=tingwei.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