public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: Jonathan Cameron <Jonathan.Cameron@huawei.com>
To: Junhao He <hejunhao3@huawei.com>, <linuxarm@huawei.com>
Cc: <suzuki.poulose@arm.com>, <james.clark@arm.com>,
	<leo.yan@arm.com>, <anshuman.khandual@arm.com>,
	<coresight@lists.linaro.org>,
	<linux-arm-kernel@lists.infradead.org>,
	<linux-kernel@vger.kernel.org>, <jonathan.cameron@huawei.com>,
	<yangyicong@huawei.com>, <prime.zeng@hisilicon.com>
Subject: Re: [PATCH v2 1/3] coresight: tmc: Add missing doc of tmc_drvdata::reading
Date: Fri, 20 Jun 2025 12:53:30 +0100	[thread overview]
Message-ID: <20250620125330.00004fa7@huawei.com> (raw)
In-Reply-To: <20250620075412.952934-2-hejunhao3@huawei.com>

On Fri, 20 Jun 2025 15:54:10 +0800
Junhao He <hejunhao3@huawei.com> wrote:

> From: Yicong Yang <yangyicong@hisilicon.com>
> 
> tmc_drvdata::reading is used to indicate whether a reading process
> is performed through /dev/xyz.tmc. Document it.
> 
> Reviewed-by: James Clark <james.clark@linaro.org>
> Signed-off-by: Yicong Yang <yangyicong@hisilicon.com>
> Signed-off-by: Junhao He <hejunhao3@huawei.com>
> ---
>  drivers/hwtracing/coresight/coresight-tmc.h | 1 +
>  1 file changed, 1 insertion(+)
> 
> diff --git a/drivers/hwtracing/coresight/coresight-tmc.h b/drivers/hwtracing/coresight/coresight-tmc.h
> index 6541a27a018e..3ca0d40c580d 100644
> --- a/drivers/hwtracing/coresight/coresight-tmc.h
> +++ b/drivers/hwtracing/coresight/coresight-tmc.h
> @@ -220,6 +220,7 @@ struct tmc_resrv_buf {
>   * @pid:	Process ID of the process that owns the session that is using
>   *		this component. For example this would be the pid of the Perf
>   *		process.
> + * @reading:	buffer's in the reading through "/dev/xyz.tmc" entry
Hi,

Perhaps reword:

"buffer is being read through "/dev/xyz.tmc" entry" or
"buffer read in progress through "/dev/xyz.tmc" entry"

I've not checked what this actually means - just looking at what you have here.

>   * @stop_on_flush: Stop on flush trigger user configuration.
>   * @buf:	Snapshot of the trace data for ETF/ETB.
>   * @etr_buf:	details of buffer used in TMC-ETR



  reply	other threads:[~2025-06-20 12:09 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-20  7:54 [PATCH v2 0/3] Coresight TMC-ETR some bugfixes and cleanups Junhao He
2025-06-20  7:54 ` [PATCH v2 1/3] coresight: tmc: Add missing doc of tmc_drvdata::reading Junhao He
2025-06-20 11:53   ` Jonathan Cameron [this message]
2025-07-01 13:38     ` hejunhao
2025-07-02 15:27   ` Leo Yan
2025-07-19 11:05     ` hejunhao
2025-06-20  7:54 ` [PATCH v2 2/3] coresight: tmc: refactor the tmc-etr mode setting to avoid race conditions Junhao He
2025-06-20 12:45   ` Jonathan Cameron
2025-07-01 13:35     ` hejunhao
2025-07-02 16:47   ` Leo Yan
2025-07-19 11:09     ` hejunhao
2025-06-20  7:54 ` [PATCH v2 3/3] coresight: tmc: Decouple the perf buffer allocation from sysfs mode Junhao He
2025-07-02 17:08   ` Leo Yan
2025-07-19 11:20     ` hejunhao

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=20250620125330.00004fa7@huawei.com \
    --to=jonathan.cameron@huawei.com \
    --cc=anshuman.khandual@arm.com \
    --cc=coresight@lists.linaro.org \
    --cc=hejunhao3@huawei.com \
    --cc=james.clark@arm.com \
    --cc=leo.yan@arm.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linuxarm@huawei.com \
    --cc=prime.zeng@hisilicon.com \
    --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