[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <20240930215001.1999212-1-heiko@sntech.de>
Date: Mon, 30 Sep 2024 23:49:58 +0200
From: Heiko Stuebner <heiko@...ech.de>
To: heiko@...ech.de
Cc: mturquette@...libre.com,
sboyd@...nel.org,
robh@...nel.org,
krzk+dt@...nel.org,
conor+dt@...nel.org,
jbx6244@...il.com,
linux-clk@...r.kernel.org,
devicetree@...r.kernel.org,
linux-arm-kernel@...ts.infradead.org,
linux-rockchip@...ts.infradead.org,
linux-kernel@...r.kernel.org
Subject: [PATCH v2 0/3] rk3328 cru dt-binding conversion
Johan already did the heavy lifting of converting the binding in [0].
The binding conversion itself already got a Reviewed-by from dt-people
only dropping the superfluous compatibles needed a bit more investigation.
So I did go through the mainline kernel and also the vendor kernel,
looking for any obscure usage.
The cru should really only be accessed by the defined clock and reset
subsystems of the kernel and thankfully there no users of the cru-dt-node
as syscon and also no syscon-get-from-compatible instances for either
the rockchip,rk3328-cru nor the strange rockchip,cru in either kernel
sources.
[0] https://lore.kernel.org/all/20220329163016.27458-1-jbx6244@gmail.com/
changes in v2:
- explain that the superfluous compatibles are not used at all
Johan Jonker (3):
dt-bindings: clock: convert rockchip,rk3328-cru.txt to YAML
arm64: dts: rockchip: fix compatible string rk3328 cru node
arm64: rockchip: add clocks property to cru node rk3328
.../bindings/clock/rockchip,rk3328-cru.txt | 58 ---------------
.../bindings/clock/rockchip,rk3328-cru.yaml | 74 +++++++++++++++++++
arch/arm64/boot/dts/rockchip/rk3328.dtsi | 4 +-
3 files changed, 77 insertions(+), 59 deletions(-)
delete mode 100644 Documentation/devicetree/bindings/clock/rockchip,rk3328-cru.txt
create mode 100644 Documentation/devicetree/bindings/clock/rockchip,rk3328-cru.yaml
--
2.43.0
Powered by blists - more mailing lists