public inbox for devicetree@vger.kernel.org
 help / color / mirror / Atom feed
From: Krzysztof Kozlowski <krzk@kernel.org>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Kuninori Morimoto <kuninori.morimoto.gx@renesas.com>,
	Conor Dooley <conor+dt@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Rob Herring <robh@kernel.org>,
	devicetree@vger.kernel.org, linux-renesas-soc@vger.kernel.org
Subject: Re: [PATCH 3/4] arm64: dts: renesas: Add R8A78000 X5H DTs
Date: Tue, 9 Sep 2025 10:55:37 +0200	[thread overview]
Message-ID: <bad82c16-8629-4f60-8c8b-36a5d1c171d6@kernel.org> (raw)
In-Reply-To: <CAMuHMdVM64FD_ObmkUpzWrr3eerM1w9hBZpsVde6Jf27xjuHOA@mail.gmail.com>

On 09/09/2025 10:50, Geert Uytterhoeven wrote:
> Hi Krzysztof,
> 
> On Tue, 9 Sept 2025 at 10:38, Krzysztof Kozlowski <krzk@kernel.org> wrote:
>> On 09/09/2025 09:51, Geert Uytterhoeven wrote:
>>> On Tue, 9 Sept 2025 at 09:46, Krzysztof Kozlowski <krzk@kernel.org> wrote:
>>>> On Tue, Sep 09, 2025 at 01:45:09AM +0000, Kuninori Morimoto wrote:
>>>
>>>>> +     extal_clk: extal {
>>>>
>>>> Use some sane prefix.
>>>>
>>>> https://web.git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/Documentation/devicetree/bindings/clock/fixed-clock.yaml
>>>>
>>>>> +             compatible = "fixed-clock";
>>>>> +             #clock-cells = <0>;
>>>>> +             /* This value must be overridden by the board */
>>>>> +             clock-frequency = <0>;
>>>>
>>>> Drop instead
>>>
>>> clock-frequency is a required property?
>>
>> And it should be provided by the board or fail the DTS. I think now it
>> hides the dtbs_check warnings for no real gain/reason.
> 
> In this particular case, the clock-frequency could indeed be omitted
> n the .dtsi, as the extal clock is mandatory, thus must always be
> augmented in board .dts.
> In case of optional clocks (e.g. serial, PCIe, or CAN external clock
> oscillators may not be populated on all boards), it is different.

1. That is not such clock.
2. So putting invalid value is correct? No, devices which do not exist
should not be in DTSI or should be disabled. Having wrong values is
never correct.

Best regards,
Krzysztof

  reply	other threads:[~2025-09-09  8:55 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-09  1:44 [PATCH 0/4] arm64: add R8A78000 support Kuninori Morimoto
2025-09-09  1:44 ` [PATCH 1/4] dt-bindings: soc: renesas: Document R-Car X5H Ironhide Kuninori Morimoto
2025-09-09  7:48   ` Krzysztof Kozlowski
2025-09-09  1:45 ` [PATCH 2/4] soc: renesas: Identify R-Car X5H Kuninori Morimoto
2025-09-09  1:45 ` [PATCH 3/4] arm64: dts: renesas: Add R8A78000 X5H DTs Kuninori Morimoto
2025-09-09  7:46   ` Krzysztof Kozlowski
2025-09-09  7:51     ` Geert Uytterhoeven
2025-09-09  8:38       ` Krzysztof Kozlowski
2025-09-09  8:50         ` Geert Uytterhoeven
2025-09-09  8:55           ` Krzysztof Kozlowski [this message]
2025-09-09  1:45 ` [PATCH 4/4] arm64: renesas: Add R8A78000 Ironhide board code Kuninori Morimoto
2025-09-09  7:47   ` Krzysztof Kozlowski
2025-09-09 23:39     ` Kuninori Morimoto
2025-09-10  7:11       ` Krzysztof Kozlowski
2025-09-10 12:45         ` Geert Uytterhoeven
2025-09-11  7:16           ` Krzysztof Kozlowski
2025-09-11  7:24             ` Geert Uytterhoeven
2025-09-11  8:45               ` Krzysztof Kozlowski

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=bad82c16-8629-4f60-8c8b-36a5d1c171d6@kernel.org \
    --to=krzk@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=geert@linux-m68k.org \
    --cc=krzk+dt@kernel.org \
    --cc=kuninori.morimoto.gx@renesas.com \
    --cc=linux-renesas-soc@vger.kernel.org \
    --cc=robh@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