From: sashiko-bot@kernel.org
To: "Chaitanya Sabnis" <chaitanya.msabnis@gmail.com>
Cc: robh@kernel.org, devicetree@vger.kernel.org, conor+dt@kernel.org,
krzk+dt@kernel.org
Subject: Re: [PATCH v2] dt-bindings: i2c: convert davinci i2c to dt-schema
Date: Wed, 13 May 2026 03:23:01 +0000 [thread overview]
Message-ID: <20260513032302.34EDEC2BCB0@smtp.kernel.org> (raw)
In-Reply-To: <20260512024851.4792-1-chaitanya.msabnis@gmail.com>
Thank you for your contribution! Sashiko AI review found 2 potential issue(s) to consider:
- [Medium] The dt-schema conversion drops the mandatory requirement for the `power-domains` property on Keystone 2 66AK2G SoCs.
- [Medium] Typo in the maintainer's email address in the YAML schema.
--
commit 15717022cbf5ba5c5c00abf42db38f66896bb215
Author: Chaitanya Sabnis <chaitanya.msabnis@gmail.com>
Subject: dt-bindings: i2c: convert davinci i2c to dt-schema
This commit converts the Texas Instruments DaVinci and Keystone I2C controller
bindings from legacy text format to YAML. It makes the interrupts property
required and defines the ti,has-pfunc and power-domains properties.
Closes: https://lore.kernel.org/oe-kbuild-all/202605120133.lQ1F3qlY-lkp@intel.com/
> diff --git a/Documentation/devicetree/bindings/i2c/i2c-davinci.txt b/Documentation/devicetree/bindings/i2c/i2c-davinci.txt
> deleted file mode 100644
> --- a/Documentation/devicetree/bindings/i2c/i2c-davinci.txt
> +++ /dev/null
[ ... ]
> -SoC-specific Required Properties:
> -
> -The following are mandatory properties for Keystone 2 66AK2G SoCs only:
> -
> -- power-domains: Should contain a phandle to a PM domain provider node
[ ... ]
> diff --git a/Documentation/devicetree/bindings/i2c/ti,davinci-i2c.yaml b/Documentation/devicetree/bindings/i2c/ti,davinci-i2c.yaml
> new file mode 100644
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/i2c/ti,davinci-i2c.yaml
> @@ -0,0 +1,62 @@
> +# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
> +%YAML 1.2
> +---
> +$id: http://devicetree.org/schemas/i2c/ti,davinci-i2c.yaml#
> +$schema: http://devicetree.org/meta-schemas/core.yaml#
> +
> +title: Texas Instruments DaVinci/Keystone I2C
> +
> +maintainers:
> + - Chaitanya Sabnis <chaitanya.msabni@gmail.com>
This isn't a bug, but there's a typo in the email address. The address is
missing the trailing 's' compared to your author email.
[ ... ]
> +required:
> + - compatible
> + - reg
> + - interrupts
> + - clocks
> +
> +unevaluatedProperties: false
Does this conversion drop the mandatory requirement for the power-domains
property on Keystone 2 66AK2G SoCs?
The original text binding explicitly documented that power-domains is
mandatory for the ti,keystone-i2c compatible string. Should there be an allOf
conditional block added here to ensure incomplete device trees missing this
requirement do not silently pass schema validation?
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260512024851.4792-1-chaitanya.msabnis@gmail.com?part=1
prev parent reply other threads:[~2026-05-13 3:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-12 2:48 [PATCH v2] dt-bindings: i2c: convert davinci i2c to dt-schema Chaitanya Sabnis
2026-05-13 3:23 ` sashiko-bot [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=20260513032302.34EDEC2BCB0@smtp.kernel.org \
--to=sashiko-bot@kernel.org \
--cc=chaitanya.msabnis@gmail.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=robh@kernel.org \
--cc=sashiko-reviews@lists.linux.dev \
/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.