[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <170869798755.1908267.1779690942757984843.robh@kernel.org>
Date: Fri, 23 Feb 2024 07:19:48 -0700
From: Rob Herring <robh@...nel.org>
To: Jerome Brunet <jbrunet@...libre.com>
Cc: Conor Dooley <conor+dt@...nel.org>, linux-pwm@...r.kernel.org,
devicetree@...r.kernel.org,
Neil Armstrong <neil.armstrong@...aro.org>,
JunYi Zhao <junyi.zhao@...ogic.com>,
Kevin Hilman <khilman@...libre.com>, linux-kernel@...r.kernel.org,
linux-amlogic@...ts.infradead.org,
Uwe Kleine-König <u.kleine-koenig@...gutronix.de>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@...aro.org>,
Rob Herring <robh+dt@...nel.org>
Subject: Re: [PATCH v5 2/5] dt-bindings: pwm: amlogic: Add a new binding for
meson8 pwm types
On Wed, 21 Feb 2024 16:11:48 +0100, Jerome Brunet wrote:
> The binding that is used up to now describe which input the PWM
> channel multiplexer should pick among its possible parents,
> which are hardcoded in the driver. This isn't a good binding in
> the sense that it should describe hardware but not usage.
>
> Add a new binding deprecating the old one that uses clocks in a
> better way and how clocks are usually used today: The list of
> clocks describe the inputs of the PWM block as they are realised
> in hardware.
>
> So deprecate the old bindings and introduce a compatible per SoC
> family to replace these.
>
> Signed-off-by: Jerome Brunet <jbrunet@...libre.com>
> ---
> .../devicetree/bindings/pwm/pwm-amlogic.yaml | 50 +++++++++++++++++--
> 1 file changed, 47 insertions(+), 3 deletions(-)
>
Reviewed-by: Rob Herring <robh@...nel.org>
Powered by blists - more mailing lists