From: Jinlong Mao <quic_jinlmao@quicinc.com>
To: Mike Leach <mike.leach@linaro.org>
Cc: Suzuki K Poulose <suzuki.poulose@arm.com>,
James Clark <james.clark@arm.com>, Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Alexander Shishkin <alexander.shishkin@linux.intel.com>,
<coresight@lists.linaro.org>,
<linux-arm-kernel@lists.infradead.org>,
<devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<linux-arm-msm@vger.kernel.org>,
"Tingwei Zhang" <quic_tingweiz@quicinc.com>,
Yuanfang Zhang <quic_yuanfang@quicinc.com>,
Tao Zhang <quic_taozha@quicinc.com>,
songchai <quic_songchai@quicinc.com>
Subject: Re: [PATCH v3 0/3] coresight: Add preferred trace id support
Date: Mon, 22 Jul 2024 18:34:53 +0800 [thread overview]
Message-ID: <bbfb3ab2-1b59-4e84-bdff-a150b0393378@quicinc.com> (raw)
In-Reply-To: <CAJ9a7VhG4qNLnT87J7OiXpygbtMRZ8uAvNhZhcRCBxovMEPDEg@mail.gmail.com>
On 2024/7/18 23:57, Mike Leach wrote:
> Hi,
>
> I have detailed comments in the following patches but in summary we should:
> 1) consistently use the term "static trace id" for these devices where
> the hardware sets a non-programmable trace ID
> 2) Simplify the patch set by introducing a new API function
> int coresight_trace_id_get_system_static_id(int trace_id)
> This would avoid having to change drivers which use the existing
> function where no static ID is required.
>
Thanks for the comments, Mike.
I will address your comments in next version.
Thanks
Jinlong Mao
> Regards
>
> Mike
>
>
> On Wed, 26 Jun 2024 at 07:07, Mao Jinlong <quic_jinlmao@quicinc.com> wrote:
>>
>> Some HW has static trace id which cannot be changed via
>> software programming. For this case, configure the trace id
>> in device tree with "arm,trace-id = <xxx>", and
>> call coresight_trace_id_get_system_id with the trace id value
>> in device probe function. The id will be reserved for the HW
>> all the time if the device is probed.
>>
>> Changes since V2:
>> 1. Change "trace-id" to "arm,trace-id".
>> 2. Add trace id flag for getting preferred id or ODD id.
>>
>> Changes since V1:
>> 1. Add argument to coresight_trace_id_get_system_id for preferred id
>> instead of adding new function coresight_trace_id_reserve_system_id.
>> 2. Add constraint to trace-id in dt-binding file.
>>
>> Mao Jinlong (3):
>> dt-bindings: arm: Add arm,trace-id for coresight dummy source
>> coresight: Add support to get preferred id for system trace sources
>> coresight: dummy: Add reserve atid support for dummy source
>>
>> .../sysfs-bus-coresight-devices-dummy-source | 15 +++++
>> .../arm/arm,coresight-dummy-source.yaml | 6 ++
>> drivers/hwtracing/coresight/coresight-dummy.c | 59 +++++++++++++++++--
>> .../hwtracing/coresight/coresight-platform.c | 25 ++++++++
>> drivers/hwtracing/coresight/coresight-stm.c | 2 +-
>> drivers/hwtracing/coresight/coresight-tpda.c | 2 +-
>> .../hwtracing/coresight/coresight-trace-id.c | 35 +++++++----
>> .../hwtracing/coresight/coresight-trace-id.h | 11 +++-
>> include/linux/coresight.h | 1 +
>> 9 files changed, 137 insertions(+), 19 deletions(-)
>> create mode 100644 Documentation/ABI/testing/sysfs-bus-coresight-devices-dummy-source
>>
>> --
>> 2.41.0
>>
>
>
> --
> Mike Leach
> Principal Engineer, ARM Ltd.
> Manchester Design Centre. UK
prev parent reply other threads:[~2024-07-22 10:35 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-26 6:07 [PATCH v3 0/3] coresight: Add preferred trace id support Mao Jinlong
2024-06-26 6:07 ` [PATCH v3 1/3] dt-bindings: arm: Add arm,trace-id for coresight dummy source Mao Jinlong
2024-06-28 21:47 ` Rob Herring (Arm)
2024-07-18 15:57 ` Mike Leach
2024-06-26 6:07 ` [PATCH v3 2/3] coresight: Add support to get preferred id for system trace sources Mao Jinlong
2024-07-18 15:57 ` Mike Leach
2024-06-26 6:07 ` [PATCH v3 3/3] coresight: dummy: Add reserve atid support for dummy source Mao Jinlong
2024-07-18 15:57 ` [PATCH v3 0/3] coresight: Add preferred trace id support Mike Leach
2024-07-22 10:34 ` Jinlong Mao [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=bbfb3ab2-1b59-4e84-bdff-a150b0393378@quicinc.com \
--to=quic_jinlmao@quicinc.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=conor+dt@kernel.org \
--cc=coresight@lists.linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=james.clark@arm.com \
--cc=krzk+dt@kernel.org \
--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=quic_songchai@quicinc.com \
--cc=quic_taozha@quicinc.com \
--cc=quic_tingweiz@quicinc.com \
--cc=quic_yuanfang@quicinc.com \
--cc=robh@kernel.org \
--cc=suzuki.poulose@arm.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