From: James Clark <james.clark@arm.com>
To: suzuki.poulose@arm.com, coresight@lists.linaro.org,
mathieu.poirier@linaro.org
Cc: mike.leach@linaro.org, leo.yan@linaro.org,
linux-kernel@vger.kernel.org, german.gomez@arm.com,
James Clark <james.clark@arm.com>,
Jonathan Corbet <corbet@lwn.net>,
Catalin Marinas <catalin.marinas@arm.com>,
Will Deacon <will@kernel.org>,
Alexander Shishkin <alexander.shishkin@linux.intel.com>,
linux-arm-kernel@lists.infradead.org, linux-doc@vger.kernel.org
Subject: [PATCH v3 0/2] coresight: etm4x: Expose default timestamp source in sysfs
Date: Tue, 23 Aug 2022 17:06:48 +0100 [thread overview]
Message-ID: <20220823160650.455823-1-james.clark@arm.com> (raw)
I've taken over this one from German because he's moved to a different
team. I gave it a quick check and bumped the version number in the docs
for the next release, but the month is an estimate.
Thanks
Changes since v2:
* Rebased onto coresight/next (b99ee26a1a)
* Bumped release version to 6.1
Changes since v1:
* Inline etmv4_to_ts_source() function.
* Collect review tag from Leo.
German Gomez (2):
coresight: etm4x: Expose default timestamp source in sysfs
coresight: etm4x: docs: Add documentation for 'ts_source' sysfs
interface
.../testing/sysfs-bus-coresight-devices-etm4x | 8 +++++
.../coresight/coresight-etm4x-reference.rst | 14 +++++++++
arch/arm64/include/asm/sysreg.h | 1 +
.../coresight/coresight-etm4x-sysfs.c | 29 +++++++++++++++++++
4 files changed, 52 insertions(+)
--
2.28.0
next reply other threads:[~2022-08-23 18:02 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-23 16:06 James Clark [this message]
2022-08-23 16:06 ` [PATCH v3 1/2] " James Clark
2022-08-23 16:06 ` [PATCH v3 2/2] coresight: etm4x: docs: Add documentation for 'ts_source' sysfs interface James Clark
2022-08-24 2:54 ` Bagas Sanjaya
2022-08-24 13:59 ` James Clark
2022-08-26 19:55 ` [PATCH v3 0/2] coresight: etm4x: Expose default timestamp source in sysfs Mathieu Poirier
2022-08-30 17:29 ` James Clark
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=20220823160650.455823-1-james.clark@arm.com \
--to=james.clark@arm.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=catalin.marinas@arm.com \
--cc=corbet@lwn.net \
--cc=coresight@lists.linaro.org \
--cc=german.gomez@arm.com \
--cc=leo.yan@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mathieu.poirier@linaro.org \
--cc=mike.leach@linaro.org \
--cc=suzuki.poulose@arm.com \
--cc=will@kernel.org \
/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®