From: Alex Elder <elder@riscstar.com>
To: sboyd@kernel.org, bmasney+clk@redhat.com,
jbrunet+clk@baylibre.com, robh@kernel.org, krzk+dt@kernel.org,
conor+dt@kernel.org, andersson@kernel.org,
konradybcio@kernel.org
Cc: abelvesa@kernel.org, kees@kernel.org, gustavoars@kernel.org,
mohd.anwar@oss.qualcomm.com, lorenzo.bianconi@oss.qualcomm.com,
danielt@kernel.org, linux-clk@vger.kernel.org,
devicetree@vger.kernel.org, linux-arm-msm@vger.kernel.org,
linux-hardening@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH v2 0/3] clk: introduce TC9564 clock support
Date: Mon, 5 Oct 2026 18:09:23 -0500 [thread overview]
Message-ID: <20261005230927.2000398-1-elder@riscstar.com> (raw)
This series adds support for the clock controller present within
the Toshiba TC9564 SoC.
This SoC attaches to a host system via PCIe. It includes a PCIe
switch with three downstream ports. To one of these ports an
embedded PCIe endpoint is attached, and it implements two PCI
functions. BAR 4 for both PCI functions provides access to the
registers that enable or disable a set of clocks.
Both TC9564 PCI functions provide PCI endpoint buses via devicetree.
Each PCI endpoint bus provides access to one of the function's BARs.
Subordinate devices (like the clock controller) can then be defined
as nodes accessible on the endpoint bus.
Only one of the two PCI functions is permitted to define the clock
device node.
-Alex
NOTE:
This series is built upon linux-next, with this patch applied:
https://lore.kernel.org/lkml/20261002181849.790275-1-elder@riscstar.com/
It is available in this git branch:
https://github.com/alexelder/linux/tree/outgoing/clock-v2
Between version 1 and version 2:
- Previously, this driver also included reset functionality. That
is now in a separate reset (only) driver, which will be sent for
review separately
- Dropped the "config syscon" devicetree binding
- Reworded the clock binding description to focus on hardware only
- Clock IDs are now consecutive (no more commented-out values)
- Get the definition of of_device_id from <linux/device_id/of.h>
rather than <linux/platform_device.h>
- Dropped a comma that followed a ternminating empty array entry
- Config option COMMON_CLK_TC9564 now selects MFD_SYSCON
- Clarified in config help text that the reset and stmmac drivers
are the "others" that use the config syscon
- Moved the clock devicetree node to be a peer (rather than a child) of
the syscon node.
Version 1 is available here:
https://lore.kernel.org/lkml/20260918165234.687224-1-elder@riscstar.com/
Alex Elder (3):
dt-bindings: clock: introduce toshiba,tc9564-clock.yaml
clk: toshiba: introduce a TC9564 SoC clock driver
arm64: dts: qcom: qcs6490-rb3gen2: add the clock controller
.../bindings/clock/toshiba,tc9564-clock.yaml | 54 ++++
MAINTAINERS | 8 +
arch/arm64/boot/dts/qcom/qcs6490-rb3gen2.dts | 16 +-
drivers/clk/Kconfig | 12 +
drivers/clk/Makefile | 1 +
drivers/clk/clk-tc9564.c | 262 ++++++++++++++++++
include/dt-bindings/clock/toshiba,tc9564.h | 34 +++
7 files changed, 386 insertions(+), 1 deletion(-)
create mode 100644 Documentation/devicetree/bindings/clock/toshiba,tc9564-clock.yaml
create mode 100644 drivers/clk/clk-tc9564.c
create mode 100644 include/dt-bindings/clock/toshiba,tc9564.h
base-commit: e8e67c48ac5cd9b0e7ba4ba2cef9decfa7327833
--
2.53.0
next reply other threads:[~2026-10-05 23:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-05 23:09 Alex Elder [this message]
2026-10-05 23:09 ` [PATCH v2 1/3] dt-bindings: clock: introduce toshiba,tc9564-clock.yaml Alex Elder
2026-10-05 23:09 ` [PATCH v2 2/3] clk: toshiba: introduce a TC9564 SoC clock driver Alex Elder
2026-10-05 23:09 ` [PATCH v2 3/3] arm64: dts: qcom: qcs6490-rb3gen2: add the clock controller Alex Elder
2026-10-06 0:30 ` Alex Elder
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=20261005230927.2000398-1-elder@riscstar.com \
--to=elder@riscstar.com \
--cc=abelvesa@kernel.org \
--cc=andersson@kernel.org \
--cc=bmasney+clk@redhat.com \
--cc=conor+dt@kernel.org \
--cc=danielt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=gustavoars@kernel.org \
--cc=jbrunet+clk@baylibre.com \
--cc=kees@kernel.org \
--cc=konradybcio@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-hardening@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lorenzo.bianconi@oss.qualcomm.com \
--cc=mohd.anwar@oss.qualcomm.com \
--cc=robh@kernel.org \
--cc=sboyd@kernel.org \
/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®