[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <7695cae2-33a3-4879-b8e5-d296d81ffece@amd.com>
Date: Wed, 2 Oct 2024 12:31:46 +0200
From: Michal Simek <michal.simek@....com>
To: Krzysztof Kozlowski <krzk@...nel.org>, linux-kernel@...r.kernel.org,
monstr@...str.eu, michal.simek@...inx.com, git@...inx.com
Cc: Alvin Šipraga <alsi@...g-olufsen.dk>,
Conor Dooley <conor+dt@...nel.org>, Krzysztof Kozlowski
<krzk+dt@...nel.org>, Michael Turquette <mturquette@...libre.com>,
Rob Herring <robh@...nel.org>, Stephen Boyd <sboyd@...nel.org>,
"open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS"
<devicetree@...r.kernel.org>,
"open list:COMMON CLK FRAMEWORK" <linux-clk@...r.kernel.org>
Subject: Re: [PATCH] dt-bindings: clock: si5351: Make compatible string
required property
On 10/2/24 10:24, Michal Simek wrote:
>
>
> On 10/2/24 10:19, Krzysztof Kozlowski wrote:
>> On 02/10/2024 09:51, Michal Simek wrote:
>>> Compatible property is likely also required property.
>>>
>>> Signed-off-by: Michal Simek <michal.simek@....com>
>>> ---
>>
>> That's a convention but not necessary, a no-op.
>
> But how do you identify device then?
> Or are you saying that device description is valid even if there is no
> compatible string?
One more thing
commit 524dfbc4e9fc ("dt-bindings: clock: si5351: convert to yaml") is showing
that compatible property was required in txt file.
-Required properties:
-- compatible: shall be one of the following:
- "silabs,si5351a" - Si5351a, QFN20 package
- "silabs,si5351a-msop" - Si5351a, MSOP10 package
I can update commit message to describe it too.
M
Powered by blists - more mailing lists