public inbox for linux-clk@vger.kernel.org
 help / color / mirror / Atom feed
From: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
To: Sergio Paracuellos <sergio.paracuellos@gmail.com>
Cc: linux-clk@vger.kernel.org, sboyd@kernel.org,
	mturquette@baylibre.com, robh@kernel.org, krzk+dt@kernel.org,
	conor+dt@kernel.org, matthias.bgg@gmail.com,
	angelogioacchino.delregno@collabora.com, p.zabel@pengutronix.de,
	linux-mips@vger.kernel.org, devicetree@vger.kernel.org,
	yangshiji66@outlook.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 0/6] mips: dts: ralink: update system controller nodes and its consumers
Date: Fri, 21 Feb 2025 18:18:57 +0100	[thread overview]
Message-ID: <Z7i1gV3tlcR22u-W@alpha.franken.de> (raw)
In-Reply-To: <20250120092146.471951-1-sergio.paracuellos@gmail.com>

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 ]

      parent reply	other threads:[~2025-02-21 17:19 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-20  9:21 [PATCH v3 0/6] mips: dts: ralink: update system controller nodes and its consumers Sergio Paracuellos
2025-01-20  9:21 ` [PATCH v3 1/6] dt-bindings: clock: add clock definitions for Ralink SoCs Sergio Paracuellos
2025-01-20 16:46   ` Krzysztof Kozlowski
2025-01-21 20:35   ` Stephen Boyd
2025-01-20  9:21 ` [PATCH v3 2/6] mips: dts: ralink: rt2880: update system controller node and its consumers Sergio Paracuellos
2025-01-20  9:21 ` [PATCH v3 3/6] mips: dts: ralink: rt3050: " Sergio Paracuellos
2025-01-20  9:21 ` [PATCH v3 4/6] mips: dts: ralink: rt3883: " Sergio Paracuellos
2025-01-20  9:21 ` [PATCH v3 5/6] mips: dts: ralink: mt7620a: " Sergio Paracuellos
2025-01-20  9:21 ` [PATCH v3 6/6] mips: dts: ralink: mt7628a: " Sergio Paracuellos
2025-02-21 17:18   ` Thomas Bogendoerfer
2025-02-21 17:31     ` Sergio Paracuellos
     [not found] ` <CAMhs-H-VevC+_=HxhMU6-at0bKut_JqdgO7j2detuB4s8R_QFQ@mail.gmail.com>
2025-02-21 14:03   ` [PATCH v3 0/6] mips: dts: ralink: update system controller nodes " Thomas Bogendoerfer
2025-02-21 14:50     ` Sergio Paracuellos
2025-02-21 15:36       ` Thomas Bogendoerfer
2025-02-21 16:40         ` Sergio Paracuellos
2025-02-21 17:01           ` Thomas Bogendoerfer
2025-02-21 17:18 ` Thomas Bogendoerfer [this message]

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=Z7i1gV3tlcR22u-W@alpha.franken.de \
    --to=tsbogend@alpha.franken.de \
    --cc=angelogioacchino.delregno@collabora.com \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=krzk+dt@kernel.org \
    --cc=linux-clk@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mips@vger.kernel.org \
    --cc=matthias.bgg@gmail.com \
    --cc=mturquette@baylibre.com \
    --cc=p.zabel@pengutronix.de \
    --cc=robh@kernel.org \
    --cc=sboyd@kernel.org \
    --cc=sergio.paracuellos@gmail.com \
    --cc=yangshiji66@outlook.com \
    /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