From: "Rob Herring (Arm)" <robh@kernel.org>
To: Songwei Chai <songwei.chai@oss.qualcomm.com>
Cc: devicetree@vger.kernel.org, james.clark@arm.com,
suzuki.poulose@arm.com, linux-arm-kernel@lists.infradead.org,
mike.leach@linaro.org, linux-kernel@vger.kernel.org,
conor+dt@kernel.org, kernel@oss.qualcomm.com,
alexander.shishkin@linux.intel.com, krzk+dt@kernel.org,
coresight@lists.linaro.org, andersson@kernel.org,
linux-arm-msm@vger.kernel.org
Subject: Re: [PATCH v8 1/7] dt-bindings: arm: Add support for Qualcomm TGU trace
Date: Wed, 10 Dec 2025 14:55:01 -0600 [thread overview]
Message-ID: <176540010050.3328122.16194666326592248573.robh@kernel.org> (raw)
In-Reply-To: <20251203090055.2432719-2-songwei.chai@oss.qualcomm.com>
On Wed, 03 Dec 2025 01:00:49 -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 tgu.yaml file to describe the bindings required to
> define the TGU in the device trees.
>
> Signed-off-by: Songwei Chai <songwei.chai@oss.qualcomm.com>
> ---
> .../devicetree/bindings/arm/qcom,tgu.yaml | 92 +++++++++++++++++++
> 1 file changed, 92 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/arm/qcom,tgu.yaml
>
Reviewed-by: Rob Herring (Arm) <robh@kernel.org>
next prev parent reply other threads:[~2025-12-10 20:55 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-03 9:00 [PATCH v8 0/7] Provides support for Trigger Generation Unit Songwei Chai
2025-12-03 9:00 ` [PATCH v8 1/7] dt-bindings: arm: Add support for Qualcomm TGU trace Songwei Chai
2025-12-10 20:55 ` Rob Herring (Arm) [this message]
2025-12-03 9:00 ` [PATCH v8 2/7] qcom-tgu: Add TGU driver Songwei Chai
2025-12-03 9:00 ` [PATCH v8 3/7] qcom-tgu: Add signal priority support Songwei Chai
2025-12-03 9:00 ` [PATCH v8 4/7] qcom-tgu: Add TGU decode support Songwei Chai
2025-12-03 9:00 ` [PATCH v8 5/7] qcom-tgu: Add support to configure next action Songwei Chai
2025-12-03 9:00 ` [PATCH v8 6/7] qcom-tgu: Add timer/counter functionality for TGU Songwei Chai
2025-12-03 9:00 ` [PATCH v8 7/7] qcom-tgu: Add reset node to initialize Songwei Chai
2025-12-03 15:48 ` [PATCH v8 0/7] Provides support for Trigger Generation Unit Suzuki K Poulose
2025-12-05 1:13 ` Songwei Chai
2025-12-05 13:51 ` Suzuki K Poulose
2025-12-08 8:07 ` 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=176540010050.3328122.16194666326592248573.robh@kernel.org \
--to=robh@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=kernel@oss.qualcomm.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=songwei.chai@oss.qualcomm.com \
--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
all inboxes | Powered by JetHome®