linux-mips.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Krzysztof Kozlowski <krzk@kernel.org>
To: Sergio Paracuellos <sergio.paracuellos@gmail.com>,
	linux-clk@vger.kernel.org
Cc: sboyd@kernel.org, mturquette@baylibre.com,
	tsbogend@alpha.franken.de, 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 1/6] dt-bindings: clock: add clock definitions for Ralink SoCs
Date: Mon, 20 Jan 2025 17:46:54 +0100	[thread overview]
Message-ID: <c49aa6ea-8be3-4cfb-a2f0-18c4e635527b@kernel.org> (raw)
In-Reply-To: <20250120092146.471951-2-sergio.paracuellos@gmail.com>

On 20/01/2025 10:21, Sergio Paracuellos wrote:
> Add clock missing definitions for RT2880, RT305X, RT3352, RT3383, RT5350,
> MT7620 and MT76X8 Ralink SoCs. Update bindings to clarify clock depending
> on these new introduced constants so consumer nodes can easily use the
> correct one in DTS files matching properly what is being used in driver
> code (clock IDs are implicitly used there).
> 
> Signed-off-by: Sergio Paracuellos <sergio.paracuellos@gmail.com>
> ---


Reviewed-by: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>

Best regards,
Krzysztof

  reply	other threads:[~2025-01-20 16:47 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 [this message]
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

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=c49aa6ea-8be3-4cfb-a2f0-18c4e635527b@kernel.org \
    --to=krzk@kernel.org \
    --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=tsbogend@alpha.franken.de \
    --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;
as well as URLs for NNTP newsgroup(s).