From: Imran Shaik <imran.shaik@oss.qualcomm.com>
To: Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Richard Cochran <richardcochran@gmail.com>,
Andrew Lunn <andrew+netdev@lunn.ch>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
Bjorn Andersson <andersson@kernel.org>,
Konrad Dybcio <konradybcio@kernel.org>
Cc: Ajit Pandey <ajit.pandey@oss.qualcomm.com>,
Taniya Das <taniya.das@oss.qualcomm.com>,
Jagadeesh Kona <jagadeesh.kona@oss.qualcomm.com>,
linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
Imran Shaik <imran.shaik@oss.qualcomm.com>
Subject: [PATCH 0/6] Add support for Qualcomm TSCSS hardware
Date: Mon, 27 Jul 2026 19:40:56 +0530 [thread overview]
Message-ID: <20260727-tscss-v1-0-beed14e72510@oss.qualcomm.com> (raw)
This series introduces support for the Qualcomm Timestamp Counter Subsystem
(TSCSS) hardware, a time synchronization subsystem present on Qualcomm
Lemans, Monaco and QDU1000 SoCs.
TSCSS is composed of two main hardware blocks:
- Timestamp Counter (TSC): a free-running hardware counter that provides
continuous timekeeping for the SoC, and is functional with a GCC TSC AHB
config clock and a global counter clock. The TSC counter resolution and
supported functionalities vary across SoC variants.
- Event Timestamp Unit (ETU): an optional block that captures TSC counter
timestamps against external hardware events. Each ETU slice binds a
slice identifier to an external event selector, and the ETU additionally
requires its own clock, pinctrl along with either a per-slice interrupt
(QDU1000) or a single summary interrupt across all ETU slices (Lemans
and Monaco).
+------------------------------------------------+ +------------------+
| Global clock controller - TSC AHB/CNTR/ETU CLK | | EVENT_IN[0:15] |
+------------------------------------------------+ +------------------+
| |
v v
+----------------------------------------------------------------------+
| Timestamp Counter Subsystem (TSCSS) |
| |
| +----------------------------------------------+ |
| +------------+ | Event Timestamp Unit (ETU) | |
| | Timestamp | | 0x01C90000-0x01C9FFFF | |
| | Counter | | +------------------------------------------+ | |
| | (TSC) | | | ETU Slices | | |
| | | | | [Slice 0] [Slice 1] [...] [Slice 15] | | |
| | 0x1C80000 | | | 0x1C90000 0x1C91000 0x1C9F000 | | |
| +------------+ | | | | |
| | +-----------+------------------------------+ | |
| +-------------|--------------------+-----------+ |
| | | |
+---------------------------------|--------------------|---------------+
| |
v v
+----------------------------------------+
| per-slice IRQ (OR) summary IRQ |
| (QDU1000) (Lemans) |
+----------------------------------------+
|
v
+-----------------------------+
| Interrupt Controller |
+-----------------------------+
The address offsets shown in the diagram above are specific to Qualcomm
Lemans SoC.
This series currently covers only the TSC block driver functionality; ETU
driver support will follow in a later series.
Signed-off-by: Imran Shaik <imran.shaik@oss.qualcomm.com>
---
Imran Shaik (6):
dt-bindings: ptp: Document the TSCSS on Qualcomm Lemans and Monaco SoCs
dt-bindings: ptp: Document TSCSS hardware on Qualcomm QDU1000 SoC
ptp: qcom: Add PTP driver for the Qualcomm TSC hardware
arm64: defconfig: Enable Qualcomm TSC driver
arm64: dts: qcom: lemans: Add support for TSCSS node
arm64: dts: qcom: qdu1000: Add support for TSCSS node
.../devicetree/bindings/ptp/qcom,lemans-tscss.yaml | 198 ++++++++++
.../bindings/ptp/qcom,qdu1000-tscss.yaml | 187 ++++++++++
arch/arm64/boot/dts/qcom/lemans.dtsi | 11 +
arch/arm64/boot/dts/qcom/qdu1000.dtsi | 11 +
arch/arm64/configs/defconfig | 1 +
drivers/ptp/Kconfig | 10 +
drivers/ptp/Makefile | 1 +
drivers/ptp/ptp_qcom_tsc.c | 413 +++++++++++++++++++++
8 files changed, 832 insertions(+)
---
base-commit: c5e32e86ca02b003f86e095d379b38148999293d
change-id: 20260705-tscss-441d844c1ee7
Best regards,
--
Imran Shaik <imran.shaik@oss.qualcomm.com>
next reply other threads:[~2026-07-27 14:11 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-27 14:10 Imran Shaik [this message]
2026-07-27 14:10 ` [PATCH 1/6] dt-bindings: ptp: Document the TSCSS on Qualcomm Lemans and Monaco SoCs Imran Shaik
2026-07-27 14:10 ` [PATCH 2/6] dt-bindings: ptp: Document TSCSS hardware on Qualcomm QDU1000 SoC Imran Shaik
2026-07-27 14:10 ` [PATCH 3/6] ptp: qcom: Add PTP driver for the Qualcomm TSC hardware Imran Shaik
2026-07-27 14:11 ` [PATCH 4/6] arm64: defconfig: Enable Qualcomm TSC driver Imran Shaik
2026-07-27 14:11 ` [PATCH 5/6] arm64: dts: qcom: lemans: Add support for TSCSS node Imran Shaik
2026-07-27 14:44 ` Konrad Dybcio
2026-07-27 14:11 ` [PATCH 6/6] arm64: dts: qcom: qdu1000: " Imran Shaik
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=20260727-tscss-v1-0-beed14e72510@oss.qualcomm.com \
--to=imran.shaik@oss.qualcomm.com \
--cc=ajit.pandey@oss.qualcomm.com \
--cc=andersson@kernel.org \
--cc=andrew+netdev@lunn.ch \
--cc=conor+dt@kernel.org \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=edumazet@google.com \
--cc=jagadeesh.kona@oss.qualcomm.com \
--cc=konradybcio@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=richardcochran@gmail.com \
--cc=robh@kernel.org \
--cc=taniya.das@oss.qualcomm.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