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 1/6] dt-bindings: clock: add clock and reset definitions for Ralink SoCs
Date: Thu, 16 Jan 2025 10:15:59 +0100 [thread overview]
Message-ID: <228a0b1b-68ec-40d2-b379-e9894a34cb57@kernel.org> (raw)
In-Reply-To: <20250115153019.407646-2-sergio.paracuellos@gmail.com>
On 15/01/2025 16:30, Sergio Paracuellos wrote:
> Add clock and reset missing definitions for RT2880, RT305X, RT3352, RT3383,
> RT5350, MT7620 and MT76X8 Ralink SoCs. Update bindings to clarify clock and
> reset cells depending on these new introduced constants so consumer nodes
> can easily use the correct one in DTS files.
I asked to explain why these should be in the bindings. Usage by DTS
alone, if driver does not use them, is not the reason as I explained
last time. The reason is that your driver actually depends on these
specific numbers because how it is written.
Or I understood it wrong and this is purely for DTS?
Best regards,
Krzysztof
next prev parent reply other threads:[~2025-01-16 9:16 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 [this message]
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
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=228a0b1b-68ec-40d2-b379-e9894a34cb57@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