On Mon, 16 Oct 2023 08:09:56 +0200
Krzysztof Kozlowski <krzysztof.kozlowski@xxxxxxxxxx> wrote:
> On 13/10/2023 16:19, Hugo Villeneuve wrote:
> > From: Hugo Villeneuve <hvilleneuve@xxxxxxxxxxxx>
> >
> > The 'clock-frequency' property is supported but mainly in ACPI-based
> > configurations, for example.
> >
> > This property has therefore no place in the sc16is7xx YAML binding.
>
> Please reference commit which you question - 0d447e927. I don't
> understand why do you remove it. The property was in the original binding.
Hi,
in the max310x YAML conversion review (last week), you told me to
drop the clock-frequency from the binding, even
if it is supported by the driver, since it is related to ACPI
configuration, not DT.
The sc16is7xx driver (IC) is very similar to the max310x, and it also
supports the clock-frequency property, and I just assumed that its
presence in the original text binding was some kind of error or legacy
leftover, and would need to be removed based on your comments.
Just as a reference, here are the original commits in both drivers that
added support for the clock-frequency property:
-----------------------
commit d4d6f03c4fb3a91dadfe147b47edd40e4d7e4d36
Author: Andy Shevchenko <andriy.shevchenko@xxxxxxxxxxxxxxx>
Date: Mon May 17 20:29:30 2021 +0300
serial: max310x: Try to get crystal clock rate from property
In some configurations, mainly ACPI-based, the clock frequency of
the device is supplied by very well established 'clock-frequency'
property. Hence, try to get it from the property at last if no other
providers are available.
commit 24bc6e68efa00f95034dbef0ba91661dd80bd37d
Author: Andy Shevchenko <andriy.shevchenko@xxxxxxxxxxxxxxx>
Date: Mon Mar 18 12:29:15 2019 +0200
serial: sc16is7xx: Respect clock-frequency property
If the property is provided and there are no other possibilities to
detect UART clock frequency, use it as a fallback.
-----------------------
Hugo.
