Linux ARM-MSM sub-architecture
 help / color / mirror / Atom feed
From: "Rob Herring (Arm)" <robh@kernel.org>
To: Songwei Chai <quic_songchai@quicinc.com>
Cc: Rob Herring <robh+dt@kernel.org>,
	James Clark <james.clark@arm.com>,
	linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org, Conor Dooley <conor+dt@kernel.org>,
	devicetree@vger.kernel.org, coresight@lists.linaro.org,
	Bjorn Andersson <andersson@kernel.org>,
	linux-arm-msm@vger.kernel.org, Mike Leach <mike.leach@linaro.org>,
	Alexander Shishkin <alexander.shishkin@linux.intel.com>,
	Suzuki K Poulose <suzuki.poulose@arm.com>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Andy Gross <agross@kernel.org>
Subject: Re: [PATCH v5 1/7] dt-bindings: arm: Add support for Coresight TGU trace
Date: Thu, 5 Jun 2025 11:27:43 -0500	[thread overview]
Message-ID: <174914086148.2803656.8177326064551626527.robh@kernel.org> (raw)
In-Reply-To: <20250529081949.26493-2-quic_songchai@quicinc.com>


On Thu, 29 May 2025 16:19:42 +0800, Songwei Chai wrote:
> The Trigger Generation Unit (TGU) is designed to detect patterns or
> sequences within a specific region of the System on Chip (SoC). Once
> configured and activated, it monitors sense inputs and can detect a
> pre-programmed state or sequence across clock cycles, subsequently
> producing a trigger.
> 
>    TGU configuration space
>         offset table
>  x-------------------------x
>  |                         |
>  |                         |
>  |                         |                           Step configuration
>  |                         |                             space layout
>  |   coresight management  |                           x-------------x
>  |        registers        |                     |---> |             |
>  |                         |                     |     |  reserve    |
>  |                         |                     |     |             |
>  |-------------------------|                     |     |-------------|
>  |                         |                     |     | priority[3] |
>  |         step[7]         |<--                  |     |-------------|
>  |-------------------------|   |                 |     | priority[2] |
>  |                         |   |                 |     |-------------|
>  |           ...           |   |Steps region     |     | priority[1] |
>  |                         |   |                 |     |-------------|
>  |-------------------------|   |                 |     | priority[0] |
>  |                         |<--                  |     |-------------|
>  |         step[0]         |-------------------->      |             |
>  |-------------------------|                           |  condition  |
>  |                         |                           |             |
>  |     control and status  |                           x-------------x
>  |           space         |                           |             |
>  x-------------------------x                           |Timer/Counter|
>                                                        |             |
> 						       x-------------x
> TGU Configuration in Hardware
> 
> The TGU provides a step region for user configuration, similar
> to a flow chart. Each step region consists of three register clusters:
> 
> 1.Priority Region: Sets the required signals with priority.
> 2.Condition Region: Defines specific requirements (e.g., signal A
> reaches three times) and the subsequent action once the requirement is
> met.
> 3.Timer/Counter (Optional): Provides timing or counting functionality.
> 
> Add a new coresight-tgu.yaml file to describe the bindings required to
> define the TGU in the device trees.
> 
> Signed-off-by: Songwei Chai <quic_songchai@quicinc.com>
> ---
>  .../bindings/arm/qcom,coresight-tgu.yaml      | 92 +++++++++++++++++++
>  1 file changed, 92 insertions(+)
>  create mode 100644 Documentation/devicetree/bindings/arm/qcom,coresight-tgu.yaml
> 

Reviewed-by: Rob Herring (Arm) <robh@kernel.org>


  reply	other threads:[~2025-06-05 16:27 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-05-29  8:19 [PATCH v5 0/7] Provides support for Trigger Generation Unit Songwei Chai
2025-05-29  8:19 ` [PATCH v5 1/7] dt-bindings: arm: Add support for Coresight TGU trace Songwei Chai
2025-06-05 16:27   ` Rob Herring (Arm) [this message]
2025-05-29  8:19 ` [PATCH v5 2/7] coresight: Add coresight TGU driver Songwei Chai
2025-05-29 11:26   ` Jonathan Cameron
2025-05-29  8:19 ` [PATCH v5 3/7] coresight-tgu: Add signal priority support Songwei Chai
2025-05-29 11:29   ` Jonathan Cameron
2025-06-06  2:52     ` songchai
2025-05-29  8:19 ` [PATCH v5 4/7] coresight-tgu: Add TGU decode support Songwei Chai
2025-05-29 11:32   ` Jonathan Cameron
2025-06-06  2:56     ` songchai
2025-05-29  8:19 ` [PATCH v5 5/7] coresight-tgu: add support to configure next action Songwei Chai
2025-05-29  8:19 ` [PATCH v5 6/7] coresight-tgu: add timer/counter functionality for TGU Songwei Chai
2025-05-29  8:19 ` [PATCH v5 7/7] coresight-tgu: add reset node to initialize Songwei Chai
2025-06-27  6:28 ` [PATCH v5 0/7] Provides support for Trigger Generation Unit Songwei Chai
  -- strict thread matches above, loose matches on Subject: below --
2025-04-23  6:34 Songwei Chai
2025-04-23  6:34 ` [PATCH v5 1/7] dt-bindings: arm: Add support for Coresight TGU trace Songwei Chai

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=174914086148.2803656.8177326064551626527.robh@kernel.org \
    --to=robh@kernel.org \
    --cc=agross@kernel.org \
    --cc=alexander.shishkin@linux.intel.com \
    --cc=andersson@kernel.org \
    --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=robh+dt@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