[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <Z7i1gV3tlcR22u-W@alpha.franken.de>
Date: Fri, 21 Feb 2025 18:18:57 +0100
From: Thomas Bogendoerfer <tsbogend@...ha.franken.de>
To: Sergio Paracuellos <sergio.paracuellos@...il.com>
Cc: linux-clk@...r.kernel.org, sboyd@...nel.org, mturquette@...libre.com,
robh@...nel.org, krzk+dt@...nel.org, conor+dt@...nel.org,
matthias.bgg@...il.com, angelogioacchino.delregno@...labora.com,
p.zabel@...gutronix.de, linux-mips@...r.kernel.org,
devicetree@...r.kernel.org, yangshiji66@...look.com,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH v3 0/6] mips: dts: ralink: update system controller nodes
and its consumers
On Mon, Jan 20, 2025 at 10:21:40AM +0100, Sergio Paracuellos wrote:
> Hi all!
>
> Ralinks SoCs have a system controller node which serves as clock and reset
> providers for the rest of the world. This patch series introduces clock
> definitions for these SoCs. The clocks are registered in the driver using
> a bunch of arrays in specific order so these definitions represent the assigned
> identifier that is used when this happens so client nodes can easily use it
> to specify the clock which they consume without the need of checking driver code.
>
> DTS files which are currently on tree are not matching system controller
> bindings. So all of them are updated to properly match them.
>
> I'd like this series to go through kernel mips git tree if possible.
>
> Thanks in advance for your time.
>
> Changes in v3:
> - Address Krzysztof comments in v2 (Thanks!):
> + Drop reset include file since what it was defined there were hardware
> constants and no binding related indexes at all.
> + Update patches for not referring to this reset removed file.
>
> Changes in v2:
> - Redo commit messages in all the patches in the series to clarify why the changes
> are needed asked by Krzysztof in v1.
>
> v2 of this series:
> - https://lore.kernel.org/linux-clk/20250119154447.462857-1-sergio.paracuellos@gmail.com/T/#t
>
> v1 of this series:
> - https://lore.kernel.org/linux-clk/20250115153019.407646-1-sergio.paracuellos@gmail.com/T/#t
>
> Best regards,
> Sergio Paracuellos
>
> Sergio Paracuellos (6):
> dt-bindings: clock: add clock definitions for Ralink SoCs
> mips: dts: ralink: rt2880: update system controller node and its
> consumers
> mips: dts: ralink: rt3050: update system controller node and its
> consumers
> mips: dts: ralink: rt3883: update system controller node and its
> consumers
> mips: dts: ralink: mt7620a: update system controller node and its
> consumers
> mips: dts: ralink: mt7628a: update system controller node and its
> consumers
>
> .../bindings/clock/mediatek,mtmips-sysc.yaml | 11 +-
> arch/mips/boot/dts/ralink/mt7620a.dtsi | 10 +-
> arch/mips/boot/dts/ralink/mt7628a.dtsi | 38 +++--
> arch/mips/boot/dts/ralink/rt2880.dtsi | 10 +-
> arch/mips/boot/dts/ralink/rt3050.dtsi | 10 +-
> arch/mips/boot/dts/ralink/rt3883.dtsi | 10 +-
> .../dt-bindings/clock/mediatek,mtmips-sysc.h | 130 ++++++++++++++++++
> 7 files changed, 196 insertions(+), 23 deletions(-)
> create mode 100644 include/dt-bindings/clock/mediatek,mtmips-sysc.h
applied patches 1-5 to mips-next
Thomas.
--
Crap can work. Given enough thrust pigs will fly, but it's not necessarily a
good idea. [ RFC1925, 2.3 ]
Powered by blists - more mailing lists