From: Suzuki K Poulose <suzuki.poulose@arm.com>
To: Anshuman Khandual <anshuman.khandual@arm.com>,
linux-arm-kernel@lists.infradead.org
Cc: Suzuki K Poulose <suzuki.poulose@arm.com>,
Mike Leach <mike.leach@linaro.org>, Leo Yan <leo.yan@linaro.org>,
coresight@lists.linaro.org, James Clark <james.clark@arm.com>,
Alexander Shishkin <alexander.shishkin@linux.intel.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH V2] coresight: tmc: Make etr buffer mode user configurable from sysfs
Date: Mon, 16 Oct 2023 23:58:42 +0100 [thread overview]
Message-ID: <169749698411.709203.13102549101679987842.b4-ty@arm.com> (raw)
In-Reply-To: <20230818082112.554638-1-anshuman.khandual@arm.com>
On Fri, 18 Aug 2023 13:51:12 +0530, Anshuman Khandual wrote:
> Currently TMC-ETR automatically selects the buffer mode from all available
> methods in the following sequentially fallback manner - also in that order.
>
> 1. FLAT mode with or without IOMMU
> 2. TMC-ETR-SG (scatter gather) mode when available
> 3. CATU mode when available
>
> [...]
Applied, thanks!
[1/1] coresight: tmc: Make etr buffer mode user configurable from sysfs
https://git.kernel.org/coresight/c/efb05212a230
Best regards,
--
Suzuki K Poulose <suzuki.poulose@arm.com>
prev parent reply other threads:[~2023-10-16 22:58 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-18 8:21 [PATCH V2] coresight: tmc: Make etr buffer mode user configurable from sysfs Anshuman Khandual
2023-08-18 9:39 ` Suzuki K Poulose
2023-08-21 19:40 ` Steve Clevenger OS
2023-08-23 23:10 ` Steve Clevenger
2023-08-26 0:14 ` Steve Clevenger
2023-08-27 21:35 ` Suzuki K Poulose
2023-08-28 16:35 ` Steve Clevenger
2023-08-30 16:04 ` Suzuki K Poulose
2023-09-01 12:22 ` Suzuki K Poulose
2023-09-07 21:31 ` Steve Clevenger
2023-12-04 21:41 ` Steve Clevenger
2023-12-11 15:42 ` Suzuki K Poulose
2023-09-15 9:53 ` Anshuman Khandual
2023-10-16 22:58 ` Suzuki K Poulose [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=169749698411.709203.13102549101679987842.b4-ty@arm.com \
--to=suzuki.poulose@arm.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=anshuman.khandual@arm.com \
--cc=coresight@lists.linaro.org \
--cc=james.clark@arm.com \
--cc=leo.yan@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mike.leach@linaro.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;
as well as URLs for NNTP newsgroup(s).