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 2/6] mips: dts: ralink: rt2880: update system controller node and its consumers
Date: Thu, 16 Jan 2025 10:18:57 +0100 [thread overview]
Message-ID: <1d6833ba-3bf5-44a6-a5e3-6bef76fd640b@kernel.org> (raw)
In-Reply-To: <20250115153019.407646-3-sergio.paracuellos@gmail.com>
On 15/01/2025 16:30, Sergio Paracuellos wrote:
> Current RT2880 device tree file is out of date and must be merged with real
> device tree file used in openWRT project [0]. As a first iteration for this
No, that's not the reason. Whatever forks have, is their problem. The
reason is that you are improving or adding here missing bits but each
bit must be justified. Again: whatever is in OpenWRT is not
justification. Justification is that device is like this, SoC is like
that or DTS is written not according to bindings.
> changes, align the current file with the needed changes for system controller
Please wrap commit message according to Linux coding style / submission
process (neither too early nor over the limit):
https://elixir.bootlin.com/linux/v6.4-rc1/source/Documentation/process/submitting-patches.rst#L597
> from '6f3b15586eef ("clk: ralink: add clock and reset driver for MTMIPS SoCs")'.
Use proper commit syntax. '' are wrong, missing commit word.
>
> [0]: https://github.com/openwrt/openwrt/blob/main/target/linux/ramips/dts/rt2880.dtsi
>
> Signed-off-by: Sergio Paracuellos <sergio.paracuellos@gmail.com>
> ---
> arch/mips/boot/dts/ralink/rt2880.dtsi | 10 ++++++++--
> 1 file changed, 8 insertions(+), 2 deletions(-)
>
> diff --git a/arch/mips/boot/dts/ralink/rt2880.dtsi b/arch/mips/boot/dts/ralink/rt2880.dtsi
> index 8fc1987d9063..1f2ea3434324 100644
> --- a/arch/mips/boot/dts/ralink/rt2880.dtsi
> +++ b/arch/mips/boot/dts/ralink/rt2880.dtsi
> @@ -1,4 +1,6 @@
> // SPDX-License-Identifier: GPL-2.0
> +#include <dt-bindings/clock/mediatek,mtmips-sysc.h>
> +
> / {
> #address-cells = <1>;
> #size-cells = <1>;
> @@ -25,9 +27,11 @@ palmbus@300000 {
> #address-cells = <1>;
> #size-cells = <1>;
>
> - sysc@0 {
> - compatible = "ralink,rt2880-sysc";
> + sysc: syscon@0 {
> + compatible = "ralink,rt2880-sysc", "syscon";
> reg = <0x0 0x100>;
> + #clock-cells = <1>;
> + #reset-cells = <1>;
Nothing from here is explained in commit msg. Why this is suddenly clock
and reset controller?
> };
>
Best regards,
Krzysztof
next prev parent reply other threads:[~2025-01-16 9:19 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-15 15:30 [PATCH 0/6] mips: dts: ralink: update system controller nodes and its consumers Sergio Paracuellos
2025-01-15 15:30 ` [PATCH 1/6] dt-bindings: clock: add clock and reset definitions for Ralink SoCs Sergio Paracuellos
2025-01-16 9:15 ` Krzysztof Kozlowski
2025-01-16 9:53 ` Sergio Paracuellos
2025-01-18 9:11 ` Krzysztof Kozlowski
2025-01-15 15:30 ` [PATCH 2/6] mips: dts: ralink: rt2880: update system controller node and its consumers Sergio Paracuellos
2025-01-16 9:18 ` Krzysztof Kozlowski [this message]
2025-01-16 10:00 ` Sergio Paracuellos
2025-01-15 15:30 ` [PATCH 3/6] mips: dts: ralink: rt3050: " Sergio Paracuellos
2025-01-15 15:30 ` [PATCH 4/6] mips: dts: ralink: rt3883: " Sergio Paracuellos
2025-01-15 15:30 ` [PATCH 5/6] mips: dts: ralink: mt7620a: " Sergio Paracuellos
2025-01-15 15:30 ` [PATCH 6/6] mips: dts: ralink: mt7628a: " Sergio Paracuellos
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=1d6833ba-3bf5-44a6-a5e3-6bef76fd640b@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