From: Krzysztof Kozlowski <krzk@kernel.org>
To: Wolfram Sang <wsa+renesas@sang-engineering.com>,
Kael D'Alcamo <dev@kael-k.io>
Cc: Andi Shyti <andi.shyti@kernel.org>, Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Wei Yan <sledge.yanwei@huawei.com>,
linux-i2c@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] dt-bindings: i2c: hisilicon,hix5hd2-i2c convert to DT schema
Date: Wed, 8 Oct 2025 17:41:17 +0900 [thread overview]
Message-ID: <c2e81faf-4d2c-40e7-bdf0-e0d41fc76d9c@kernel.org> (raw)
In-Reply-To: <aOYRLCGv9_k8i_Vn@shikoro>
On 08/10/2025 16:22, Wolfram Sang wrote:
> Hi,
>
> thanks for this conversion!
>
>> +properties:
>> + compatible:
>> + enum:
>> + - hisilicon,hix5hd2-i2c
>
> Question for DT maintainers: Is it preferred to start with 'enum' right
> away or to start with 'const' and convert to 'enum' once a second user
> appears?
I don't have preference except: I would suggest using enum if you
already think there will be second variant, because it would save one
re-indent/rewrite of the line.
But in this case of old schema this is unlikely, so really does not
matter for me.
>
>> + "#address-cells":
>> + const: 1
>> +
>> + "#size-cells":
>> + const: 0
>
> These should be left out because they come from i2c-controller.yaml?
Yeah, these are redundant.
>
>> +required:
>> + - compatible
>> + - reg
>> + - interrupts
>> + - clocks
>> + - "#address-cells"
>> + - "#size-cells"
>
> Same here for the last two?
i2c-controller.yaml does not require these I think for a reason - you
could have enabled empty I2C controller node for user space and having
these required without actual children causes dtc W=1 or W=2 warning.
so yeah, I would propose to drop these as well.
Best regards,
Krzysztof
next prev parent reply other threads:[~2025-10-08 8:41 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-04 15:48 [PATCH] dt-bindings: i2c: hisilicon,hix5hd2-i2c convert to DT schema Kael D'Alcamo
2025-10-07 20:49 ` Conor Dooley
2025-10-08 7:22 ` Wolfram Sang
2025-10-08 8:41 ` Krzysztof Kozlowski [this message]
2025-10-08 20:04 ` [PATCH v2 0/1] " Kael D'Alcamo
2025-10-08 20:04 ` [PATCH v2 1/1] " Kael D'Alcamo
2025-10-09 0:23 ` Krzysztof Kozlowski
2025-10-09 11:22 ` Wolfram Sang
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=c2e81faf-4d2c-40e7-bdf0-e0d41fc76d9c@kernel.org \
--to=krzk@kernel.org \
--cc=andi.shyti@kernel.org \
--cc=conor+dt@kernel.org \
--cc=dev@kael-k.io \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh@kernel.org \
--cc=sledge.yanwei@huawei.com \
--cc=wsa+renesas@sang-engineering.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.