From: Artur Weber <aweber.kernel@gmail.com>
To: Michael Turquette <mturquette@baylibre.com>,
Stephen Boyd <sboyd@kernel.org>,
Florian Fainelli <florian.fainelli@broadcom.com>,
Ray Jui <rjui@broadcom.com>,
Scott Branden <sbranden@broadcom.com>,
Broadcom internal kernel review list
<bcm-kernel-feedback-list@broadcom.com>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>
Cc: Alex Elder <elder@kernel.org>,
Stanislav Jakubek <stano.jakubek@gmail.com>,
linux-clk@vger.kernel.org, linux-kernel@vger.kernel.org,
devicetree@vger.kernel.org,
~postmarketos/upstreaming@lists.sr.ht,
Artur Weber <aweber.kernel@gmail.com>,
Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>,
Alex Elder <elder@riscstar.com>
Subject: [PATCH v4 0/8] clk: bcm: kona: Add bus clock support, bus clocks for BCM21664/BCM281xx
Date: Tue, 18 Mar 2025 09:13:22 +0100 [thread overview]
Message-ID: <20250318-kona-bus-clock-v4-0-f54416e8328f@gmail.com> (raw)
This patchset does the following:
- Introduce support for bus clocks. These are fairly similar to
peripheral clocks, but only implement policy, gate and hyst.
- Add matching bus clocks for BCM21664 and BCM281xx peripheral clocks
and update device tree bindings to match.
The previous (RFC) version of this patchset also introduced a
prerequisite clock mechanism to enable bus clocks before their
corresponding peripheral clocks. It seems that this is unnecessary -
the way these clocks are initialized leaves them enabled by default.
Thus, the prerequisite mechanism has been dropped from this version.
This is fine for now, and more accurate to hardware (bus clocks are
a prerequisite for the bus, not the peripheral clock). I had an idea
to connect bus clocks to buses using "simple-pm-bus" in DT, but
this is a task for another patchset.
Signed-off-by: Artur Weber <aweber.kernel@gmail.com>
---
Changes in v4:
- Rename moved CLOCK_COUNT defines to CLK_COUNT to avoid redefinition
- Squash BCM21664/BCM281xx bus clock DT bindings commits together
- Link to v3: https://lore.kernel.org/r/20250308-kona-bus-clock-v3-0-d6fb5bfc3b67@gmail.com
Changes in v3:
- Fix DT schema example in BCM281xx bus clock bindings
- Move CLOCK_COUNT defines from dt-bindings header to the driver
- Fix BCM21664 UARTBx_APB IDs being out of order compared to clock
driver
- Link to v2: https://lore.kernel.org/r/20250303-kona-bus-clock-v2-0-a363c6a6b798@gmail.com
Changes in v2:
- Drop prerequisite clock patch
- Move clock/bcm21664.h dt-bindings header change to dt-bindings patch
- Add BCM281xx bus clocks
- Link to v1: https://lore.kernel.org/r/20250216-kona-bus-clock-v1-0-e8779d77a6f2@gmail.com
---
Artur Weber (8):
clk: bcm: kona: Move CLOCK_COUNT defines into the driver
dt-bindings: clock: brcm,kona-ccu: Drop CLOCK_COUNT defines from DT headers
dt-bindings: clock: brcm,kona-ccu: Add BCM21664 and BCM281xx bus clocks
clk: bcm: kona: Add support for bus clocks
clk: bcm21664: Add corresponding bus clocks for peripheral clocks
clk: bcm281xx: Add corresponding bus clocks for peripheral clocks
ARM: dts: bcm2166x-common: Add matching bus clocks for peripheral clocks
ARM: dts: bcm11351: Add corresponding bus clocks for peripheral clocks
.../devicetree/bindings/clock/brcm,kona-ccu.yaml | 49 ++++++-
arch/arm/boot/dts/broadcom/bcm11351.dtsi | 33 +++--
arch/arm/boot/dts/broadcom/bcm2166x-common.dtsi | 28 ++--
drivers/clk/bcm/clk-bcm21664.c | 99 ++++++++++++++-
drivers/clk/bcm/clk-bcm281xx.c | 141 ++++++++++++++++++++-
drivers/clk/bcm/clk-kona-setup.c | 116 +++++++++++++++++
drivers/clk/bcm/clk-kona.c | 62 ++++++++-
drivers/clk/bcm/clk-kona.h | 12 +-
include/dt-bindings/clock/bcm21664.h | 17 ++-
include/dt-bindings/clock/bcm281xx.h | 24 +++-
10 files changed, 538 insertions(+), 43 deletions(-)
---
base-commit: ffd294d346d185b70e28b1a28abe367bbfe53c04
change-id: 20250212-kona-bus-clock-4297eefae940
Best regards,
--
Artur Weber <aweber.kernel@gmail.com>
next reply other threads:[~2025-03-18 8:13 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-18 8:13 Artur Weber [this message]
2025-03-18 8:13 ` [PATCH v4 1/8] clk: bcm: kona: Move CLOCK_COUNT defines into the driver Artur Weber
2025-03-18 8:13 ` [PATCH v4 2/8] dt-bindings: clock: brcm,kona-ccu: Drop CLOCK_COUNT defines from DT headers Artur Weber
2025-03-18 8:13 ` [PATCH v4 3/8] dt-bindings: clock: brcm,kona-ccu: Add BCM21664 and BCM281xx bus clocks Artur Weber
2025-03-19 8:39 ` Krzysztof Kozlowski
2025-03-18 8:13 ` [PATCH v4 4/8] clk: bcm: kona: Add support for " Artur Weber
2025-03-18 8:13 ` [PATCH v4 5/8] clk: bcm21664: Add corresponding bus clocks for peripheral clocks Artur Weber
2025-03-18 8:13 ` [PATCH v4 6/8] clk: bcm281xx: " Artur Weber
2025-03-18 8:13 ` [PATCH v4 7/8] ARM: dts: bcm2166x-common: Add matching " Artur Weber
2025-03-18 8:13 ` [PATCH v4 8/8] ARM: dts: bcm11351: Add corresponding " Artur Weber
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=20250318-kona-bus-clock-v4-0-f54416e8328f@gmail.com \
--to=aweber.kernel@gmail.com \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=elder@kernel.org \
--cc=elder@riscstar.com \
--cc=florian.fainelli@broadcom.com \
--cc=krzk+dt@kernel.org \
--cc=krzysztof.kozlowski@linaro.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mturquette@baylibre.com \
--cc=rjui@broadcom.com \
--cc=robh@kernel.org \
--cc=sboyd@kernel.org \
--cc=sbranden@broadcom.com \
--cc=stano.jakubek@gmail.com \
--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;
as well as URLs for NNTP newsgroup(s).