The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Krzysztof Kozlowski <krzk@kernel.org>
To: SP_ISW1_AT@novatek.com.tw, andi.shyti@kernel.org,
	robh@kernel.org, krzk+dt@kernel.org, conor+dt@kernel.org,
	linux-i2c@vger.kernel.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org
Cc: ben_huang@novatek.com.tw, toby_chui@novatek.com.tw,
	shihpei_hsu@novatek.com.tw
Subject: Re: [PATCH 2/3] dt-bindings: i2c: add Novatek NT726xx SoC i2c controller
Date: Fri, 5 Jun 2026 12:40:15 +0200	[thread overview]
Message-ID: <61c140d0-e7c3-4f81-b282-d158a2d37113@kernel.org> (raw)
In-Reply-To: <ffb9c16e-5a5a-45c4-8d4b-369b0a4fe314@kernel.org>

On 05/06/2026 12:37, Krzysztof Kozlowski wrote:
>> +title: Novatek NT726xx SoC I2C master controller
>> +
>> +allOf:
>> +  - $ref: /schemas/i2c/i2c-controller.yaml#
>> +
>> +properties:
>> +  compatible:
>> +    const: novatek,nt726xx-i2c

One more thing - you must have specific compatibles. This is EXPLICITLY
requested in writing bindings. Please carefully read entire file.

>> +
>> +  reg:
>> +    maxItems: 4
> 
> You need to list the items instead.
> 
>> +
>> +  interrupts:
>> +    maxItems: 3
> 
> You need to list the items instead.
> 
>> +
>> +  clock-frequency:
>> +    description: Operation clock frequency of i2c in Hz.
> 
> Drop
> 
>> +    default: 100000
>> +    enum: [ 100000, 400000 ]
>> +
>> +  novatek,hwmods:
>> +    $ref: /schemas/types.yaml#/definitions/string
>> +    description: Name of each i2c pin, must be named with "i2cX". (X is
>> +                 an integer starting from 0)
>> +    minItems: 1
> 
> There is no such syntax. Please do not invent own style.
> 
> Anyway, I don't understand the property - drop.
> 
>> +
>> +  novatek,stbc:
>> +    $ref: /schemas/types.yaml#/definitions/uint32
>> +    description: Set if this i2c master controlled by stbc.
> 
> No clue what does that mean. What is stbc? Acronym of something? Why
> would that be a property of a board?
> 
>> +    minItems: 1
> 
> Please open existing code. Do you see anywhere uint32 with minItems?
> Like anywhere? I really wonder what process lead to such code...


Heh, and now I see you never tested it even before sending it.

Best regards,
Krzysztof

  reply	other threads:[~2026-06-05 10:40 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-05  3:55 [PATCH 1/3] MAINTAINERS: Add entry for Novatek NT726xx SoC i2c driver SP_ISW1_AT
2026-06-05  3:56 ` [PATCH 2/3] dt-bindings: i2c: add Novatek NT726xx SoC i2c controller SP_ISW1_AT
2026-06-05  3:56   ` [PATCH 3/3] i2c: Add i2c-nt726xx.c i2c driver for Novatek NT726xx SoCs SP_ISW1_AT
2026-06-05  5:25   ` [PATCH 2/3] dt-bindings: i2c: add Novatek NT726xx SoC i2c controller Rob Herring (Arm)
2026-06-05 10:37   ` Krzysztof Kozlowski
2026-06-05 10:40     ` Krzysztof Kozlowski [this message]
2026-06-05 10:38 ` [PATCH 1/3] MAINTAINERS: Add entry for Novatek NT726xx SoC i2c driver Krzysztof Kozlowski
  -- strict thread matches above, loose matches on Subject: below --
2026-06-04  6:04 SP_ISW1_AT
2026-06-04  6:04 ` [PATCH 2/3] dt-bindings: i2c: add Novatek NT726xx SoC i2c controller SP_ISW1_AT
2026-06-04 14:37   ` Rob Herring (Arm)

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=61c140d0-e7c3-4f81-b282-d158a2d37113@kernel.org \
    --to=krzk@kernel.org \
    --cc=SP_ISW1_AT@novatek.com.tw \
    --cc=andi.shyti@kernel.org \
    --cc=ben_huang@novatek.com.tw \
    --cc=conor+dt@kernel.org \
    --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=shihpei_hsu@novatek.com.tw \
    --cc=toby_chui@novatek.com.tw \
    /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