[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <e93ef041-89d3-5718-4b1d-55bfd0c72797@linaro.org>
Date: Thu, 8 Sep 2022 14:35:09 +0200
From: Krzysztof Kozlowski <krzysztof.kozlowski@...aro.org>
To: Sergiu Moga <sergiu.moga@...rochip.com>, lee@...nel.org,
robh+dt@...nel.org, krzysztof.kozlowski+dt@...aro.org,
nicolas.ferre@...rochip.com, alexandre.belloni@...tlin.com,
claudiu.beznea@...rochip.com, richard.genoud@...il.com,
radu_nicolae.pirea@....ro, gregkh@...uxfoundation.org,
broonie@...nel.org, mturquette@...libre.com, sboyd@...nel.org,
jirislaby@...nel.org, admin@...iphile.com,
kavyasree.kotagiri@...rochip.com, tudor.ambarus@...rochip.com
Cc: devicetree@...r.kernel.org, linux-arm-kernel@...ts.infradead.org,
linux-kernel@...r.kernel.org, linux-spi@...r.kernel.org,
linux-serial@...r.kernel.org, linux-clk@...r.kernel.org
Subject: Re: [PATCH v2 13/13] dt-bindings: serial: atmel,at91-usart: Add gclk
as a possible USART clock
On 06/09/2022 15:55, Sergiu Moga wrote:
> The Devicetree nodes for FLEXCOM's USART can also have an alternative
> clock source for the baudrate generator (other than the peripheral
> clock), namely the Generick Clock. Thus make the binding aware of
> this potential clock that someone may place in the clock related
> properties of the USART node.
Last sentence is confusing - what is the potential? Just skip it.
>
> Signed-off-by: Sergiu Moga <sergiu.moga@...rochip.com>
> ---
>
>
>
> v1 -> v2:
> - Nothing, this patch was not here before
You have confusing order of patches. Bindings mixed with DTS mixed with
drivers. Keep things ordered.
1. DTS changes needed for aligning to schema.
2. all bindings
3. rest
Best regards,
Krzysztof
Powered by blists - more mailing lists