[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20240627210738.GB501440-robh@kernel.org>
Date: Thu, 27 Jun 2024 15:07:38 -0600
From: Rob Herring <robh@...nel.org>
To: Tomer Maimon <tmaimon77@...il.com>
Cc: mturquette@...libre.com, sboyd@...nel.org, p.zabel@...gutronix.de,
krzysztof.kozlowski+dt@...aro.org, tali.perry1@...il.com,
joel@....id.au, venture@...gle.com, yuenn@...gle.com,
benjaminfair@...gle.com, openbmc@...ts.ozlabs.org,
linux-clk@...r.kernel.org, linux-kernel@...r.kernel.org,
devicetree@...r.kernel.org
Subject: Re: [PATCH v25 1/3] dt-bindings: reset: npcm: add clock properties
On Tue, Jun 18, 2024 at 09:58:17PM +0300, Tomer Maimon wrote:
> This commit adds a 25MHz reference clock and clock-cell properties to
> the NPCM reset document. The addition is necessitated by the integration
> of the NPCM8xx clock auxiliary bus device into the NPCM reset driver.
>
> The inclusion of the NPCM8xx clock properties in the reset document is
> crucial as the reset block also serves as a clock provider for the
> NPCM8xx clock. This enhancement is intended to facilitate the use of the
> NPCM8xx clock driver.
Still not really much of an explanation of why an ABI break is okay.
Reasons are generally no one has the h/w yet, or the platform support is
incomplete and really doesn't work without DT updates.
> Signed-off-by: Tomer Maimon <tmaimon77@...il.com>
> ---
> .../bindings/reset/nuvoton,npcm750-reset.yaml | 18 ++++++++++++++++++
> 1 file changed, 18 insertions(+)
It's ultimately the platform's maintainers problem to care, so:
Reviewed-by: Rob Herring <robh@...nel.org>
Powered by blists - more mailing lists