From: Junhao He <hejunhao3@huawei.com>
To: <suzuki.poulose@arm.com>, <james.clark@arm.com>,
<anshuman.khandual@arm.com>, <mike.leach@linaro.org>,
<leo.yan@arm.com>
Cc: <coresight@lists.linaro.org>,
<linux-arm-kernel@lists.infradead.org>,
<linux-kernel@vger.kernel.org>, <linuxarm@huawei.com>,
<jonathan.cameron@huawei.com>, <yangyicong@huawei.com>,
<hejunhao3@huawei.com>
Subject: [PATCH 0/4] Coresight TMC-ETR some bugfixes and cleanups
Date: Fri, 18 Apr 2025 13:58:16 +0800 [thread overview]
Message-ID: <20250418055820.3689408-1-hejunhao3@huawei.com> (raw)
This patchset builds upon Yicong's previous patches [1].
Introducing fix two race issues found by using TMC-ETR and CATU, Two
cleanups found when debugging the issues.
[1] https://lore.kernel.org/linux-arm-kernel/20241202092419.11777-1-yangyicong@huawei.com/
Junhao He (2):
coresight: catu: add locking to catu enable/disable functions
coresight: tmc: refactor the tmc-etr mode setting
Yicong Yang (2):
coresight: tmc: Add missing doc of tmc_drvdata::reading
coresight: tmc-etr: Decouple the perf buffer allocation from sysfs
mode
drivers/hwtracing/coresight/coresight-catu.c | 6 +
drivers/hwtracing/coresight/coresight-catu.h | 1 +
.../hwtracing/coresight/coresight-tmc-etr.c | 106 +++++++++---------
drivers/hwtracing/coresight/coresight-tmc.h | 1 +
4 files changed, 64 insertions(+), 50 deletions(-)
--
2.33.0
next reply other threads:[~2025-04-18 6:04 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-18 5:58 Junhao He [this message]
2025-04-18 5:58 ` [PATCH 1/4] coresight: tmc: Add missing doc of tmc_drvdata::reading Junhao He
2025-04-18 5:58 ` [PATCH 2/4] coresight: catu: add locking to catu enable/disable functions Junhao He
2025-04-18 5:58 ` [PATCH 3/4] coresight: tmc: refactor the tmc-etr mode setting Junhao He
2025-04-18 7:12 ` Jie Gan
2025-04-22 12:52 ` hejunhao
2025-04-23 2:07 ` Jie Gan
2025-04-25 2:16 ` hejunhao
2025-04-18 5:58 ` [PATCH 4/4] coresight: tmc-etr: Decouple the perf buffer allocation from sysfs mode Junhao He
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=20250418055820.3689408-1-hejunhao3@huawei.com \
--to=hejunhao3@huawei.com \
--cc=anshuman.khandual@arm.com \
--cc=coresight@lists.linaro.org \
--cc=james.clark@arm.com \
--cc=jonathan.cameron@huawei.com \
--cc=leo.yan@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxarm@huawei.com \
--cc=mike.leach@linaro.org \
--cc=suzuki.poulose@arm.com \
--cc=yangyicong@huawei.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