From: Aelin Reidel <aelin@mainlining.org>
To: Bjorn Andersson <andersson@kernel.org>,
Michael Turquette <mturquette@baylibre.com>,
Stephen Boyd <sboyd@kernel.org>, Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Taniya Das <quic_tdas@quicinc.com>
Cc: linux-arm-msm@vger.kernel.org, linux-clk@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux@mainlining.org, phone-devel@vger.kernel.org,
~postmarketos/upstreaming@lists.sr.ht,
Aelin Reidel <aelin@mainlining.org>
Subject: [PATCH 0/4] clk: qcom: Add support for basic clock providers on Fillmore SoC
Date: Sun, 08 Mar 2026 01:39:26 +0100 [thread overview]
Message-ID: <20260308-fillmore-clks-v1-0-976d9a6bebe7@mainlining.org> (raw)
This series adds the bare minimum clock provider (gcc and rpmh) driver
support for the Fillmore SoC (e.g. SM7450).
With this, it is possible to boot to the rootfs from the UFS storage and
have functioning USB.
The multimedia-specific clock providers will be sent in a follow-up
series.
This patch series was tested on a Xiaomi 13 Lite / Civi 2 (xiaomi-ziyi).
Signed-off-by: Aelin Reidel <aelin@mainlining.org>
---
Aelin Reidel (4):
dt-bindings: clock: qcom: document the Fillmore Global Clock Controller
dt-bindings: clock: qcom: Document the Fillmore RPMH Clock Controller
clk: qcom: Add Global Clock controller (GCC) driver for Fillmore
clk: qcom: rpmh: Add support for Fillmore rpmh clocks
.../bindings/clock/qcom,fillmore-gcc.yaml | 60 +
.../devicetree/bindings/clock/qcom,rpmhcc.yaml | 1 +
drivers/clk/qcom/Kconfig | 9 +
drivers/clk/qcom/Makefile | 1 +
drivers/clk/qcom/clk-rpmh.c | 22 +
drivers/clk/qcom/gcc-fillmore.c | 2714 ++++++++++++++++++++
include/dt-bindings/clock/qcom,fillmore-gcc.h | 195 ++
7 files changed, 3002 insertions(+)
---
base-commit: a0ae2a256046c0c5d3778d1a194ff2e171f16e5f
change-id: 20260301-fillmore-clks-9509b588e71f
Best regards,
--
Aelin Reidel <aelin@mainlining.org>
next reply other threads:[~2026-03-08 0:41 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-08 0:39 Aelin Reidel [this message]
2026-03-08 0:39 ` [PATCH 1/4] dt-bindings: clock: qcom: document the Fillmore Global Clock Controller Aelin Reidel
2026-03-08 0:50 ` Aelin Reidel
2026-03-09 7:38 ` Krzysztof Kozlowski
2026-03-09 14:56 ` Aelin Reidel
2026-03-10 13:22 ` Konrad Dybcio
2026-03-08 0:39 ` [PATCH 2/4] dt-bindings: clock: qcom: Document the Fillmore RPMH " Aelin Reidel
2026-03-09 7:39 ` Krzysztof Kozlowski
2026-03-08 0:39 ` [PATCH 3/4] clk: qcom: Add Global Clock controller (GCC) driver for Fillmore Aelin Reidel
2026-03-10 13:33 ` Dmitry Baryshkov
2026-03-10 15:15 ` Konrad Dybcio
2026-03-08 0:39 ` [PATCH 4/4] clk: qcom: rpmh: Add support for Fillmore rpmh clocks Aelin Reidel
2026-03-10 13:26 ` Konrad Dybcio
2026-03-09 10:57 ` [PATCH 0/4] clk: qcom: Add support for basic clock providers on Fillmore SoC Krzysztof Kozlowski
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=20260308-fillmore-clks-v1-0-976d9a6bebe7@mainlining.org \
--to=aelin@mainlining.org \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@mainlining.org \
--cc=mturquette@baylibre.com \
--cc=phone-devel@vger.kernel.org \
--cc=quic_tdas@quicinc.com \
--cc=robh@kernel.org \
--cc=sboyd@kernel.org \
--cc=~postmarketos/upstreaming@lists.sr.ht \
/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