devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: Hugo Villeneuve <hugo@hugovil.com>
Cc: gregkh@linuxfoundation.org, jirislaby@kernel.org,
	robh+dt@kernel.org, krzysztof.kozlowski+dt@linaro.org,
	conor+dt@kernel.org, hvilleneuve@dimonoff.com,
	linux-kernel@vger.kernel.org, linux-serial@vger.kernel.org,
	devicetree@vger.kernel.org
Subject: Re: [PATCH 2/2] dt-bindings: serial: sc16is7xx: remove 'clock-frequency' property
Date: Mon, 16 Oct 2023 16:18:41 +0200	[thread overview]
Message-ID: <2c1b47aa-ad4f-4a7b-901c-e0e44cdc31f2@linaro.org> (raw)
In-Reply-To: <20231016095848.ba76e14c41bb7ceae8217e04@hugovil.com>

On 16/10/2023 15:58, Hugo Villeneuve wrote:
> On Mon, 16 Oct 2023 08:09:56 +0200
> Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org> wrote:
> 
>> On 13/10/2023 16:19, Hugo Villeneuve wrote:
>>> From: Hugo Villeneuve <hvilleneuve@dimonoff.com>
>>>
>>> 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.

Yes, when we talked about max310x.

> 
> 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.

But that is not the same and not accurate. clock-frequency was described
by the binding.

> 
> 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@linux.intel.com>
> 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@linux.intel.com>
> 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.
> -----------------------

These are driver changes.

Best regards,
Krzysztof


      reply	other threads:[~2023-10-16 14:18 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-13 14:19 [PATCH 0/2] serial: sc16is7xx: device tree improvements Hugo Villeneuve
2023-10-13 14:19 ` [PATCH 1/2] dt-bindings: serial: sc16is7xx: move 'allOf' block after 'required' Hugo Villeneuve
2023-10-16  6:11   ` Krzysztof Kozlowski
2023-10-13 14:19 ` [PATCH 2/2] dt-bindings: serial: sc16is7xx: remove 'clock-frequency' property Hugo Villeneuve
2023-10-16  6:09   ` Krzysztof Kozlowski
2023-10-16 13:58     ` Hugo Villeneuve
2023-10-16 14:18       ` Krzysztof Kozlowski [this message]

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=2c1b47aa-ad4f-4a7b-901c-e0e44cdc31f2@linaro.org \
    --to=krzysztof.kozlowski@linaro.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=hugo@hugovil.com \
    --cc=hvilleneuve@dimonoff.com \
    --cc=jirislaby@kernel.org \
    --cc=krzysztof.kozlowski+dt@linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-serial@vger.kernel.org \
    --cc=robh+dt@kernel.org \
    /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;
as well as URLs for NNTP newsgroup(s).