All of lore.kernel.org
 help / color / mirror / Atom feed
From: sashiko-bot@kernel.org
To: "Xianwei Zhao" <xianwei.zhao@amlogic.com>
Cc: linux-amlogic@lists.infradead.org, conor+dt@kernel.org,
	robh@kernel.org, devicetree@vger.kernel.org,
	neil.armstrong@linaro.org
Subject: Re: [PATCH 1/3] dt-bindings: i2c: add Amlogic A9 I2C controller
Date: Thu, 24 Sep 2026 08:46:45 +0000	[thread overview]
Message-ID: <20260924084646.489AD1F00893@smtp.kernel.org> (raw)
In-Reply-To: <20260924-a9-i2c-v1-1-b8ad9b46f4a8@amlogic.com>

Thank you for your contribution! Sashiko AI review found 2 potential issue(s) to consider:
- [Low] dt-bindings: i2c: amlogic: misspelled maintainer email addresses
- [Low] dt-bindings: i2c: amlogic: invalid GIC interrupt type in example
--

commit 1ce7d70f157b5cc3e10c7e75c64287c2dbe2c1bb
Author: Xianwei Zhao <xianwei.zhao@amlogic.com>

dt-bindings: i2c: add Amlogic A9 I2C controller
    
Add a Device Tree binding for the I2C controller found on the
Amlogic A9 SoC.

> diff --git a/Documentation/devicetree/bindings/i2c/amlogic,a9-i2c.yaml b/Documentation/devicetree/bindings/i2c/amlogic,a9-i2c.yaml
> new file mode 100644
> index 0000000000000..681241a526806
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/i2c/amlogic,a9-i2c.yaml
> @@ -0,0 +1,61 @@
> +# SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause)
> +%YAML 1.2
> +---
> +$id: http://devicetree.org/schemas/i2c/amlogic,a9-i2c.yaml#
> +$schema: http://devicetree.org/meta-schemas/core.yaml#
> +
> +title: Amlogic A9 I2C Controller
> +
> +maintainers:
> +  - Xianwei Zhao <xianwei.zhaol@amlogic.com>
> +  - Junyi Zhao <junyi.zhaol@amlogic.com>

[Severity: Low]
This isn't a functional bug, but are these email addresses misspelled?

The trailing 'l' in 'zhaol' causes emails to bounce when contributors
use get_maintainer.pl to CC the maintainers on patches modifying this
binding.

[ ... ]

> +examples:
> +  - |
> +    i2c@3a4400 {
> +        compatible = "amlogic,a9-i2c";
> +        reg = <0x3a4400 0x3c>;
> +        interrupts = <1 164 1>;

[Severity: Low]
Is this GIC interrupt specifier in the examples block correct?

The first cell value of 1 designates a GIC_PPI (Per-Processor Interrupt),
which is limited to the range 0-15. A value of 164 is highly invalid for a
PPI.

Since I2C controllers are typically shared peripherals, should this be 0
(GIC_SPI) instead?

Developers copy-pasting the example will create invalid device trees that
fail at runtime or during dtc validation.

> +        clocks = <&clkc_periphs 11>;
> +        #address-cells = <1>;
> +        #size-cells = <0>;
> +
> +        eeprom@52 {
> +            compatible = "atmel,24c32";
> +            reg = <0x52>;
> +        };
> +    };

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/20260924-a9-i2c-v1-0-b8ad9b46f4a8@amlogic.com?part=1

WARNING: multiple messages have this Message-ID (diff)
From: sashiko-bot@kernel.org
To: "Xianwei Zhao" <xianwei.zhao@amlogic.com>
Cc: linux-amlogic@lists.infradead.org, conor+dt@kernel.org,
	robh@kernel.org, devicetree@vger.kernel.org,
	neil.armstrong@linaro.org
Subject: Re: [PATCH 1/3] dt-bindings: i2c: add Amlogic A9 I2C controller
Date: Thu, 24 Sep 2026 08:46:45 +0000	[thread overview]
Message-ID: <20260924084646.489AD1F00893@smtp.kernel.org> (raw)
In-Reply-To: <20260924-a9-i2c-v1-1-b8ad9b46f4a8@amlogic.com>

Thank you for your contribution! Sashiko AI review found 2 potential issue(s) to consider:
- [Low] dt-bindings: i2c: amlogic: misspelled maintainer email addresses
- [Low] dt-bindings: i2c: amlogic: invalid GIC interrupt type in example
--

commit 1ce7d70f157b5cc3e10c7e75c64287c2dbe2c1bb
Author: Xianwei Zhao <xianwei.zhao@amlogic.com>

dt-bindings: i2c: add Amlogic A9 I2C controller
    
Add a Device Tree binding for the I2C controller found on the
Amlogic A9 SoC.

> diff --git a/Documentation/devicetree/bindings/i2c/amlogic,a9-i2c.yaml b/Documentation/devicetree/bindings/i2c/amlogic,a9-i2c.yaml
> new file mode 100644
> index 0000000000000..681241a526806
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/i2c/amlogic,a9-i2c.yaml
> @@ -0,0 +1,61 @@
> +# SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause)
> +%YAML 1.2
> +---
> +$id: http://devicetree.org/schemas/i2c/amlogic,a9-i2c.yaml#
> +$schema: http://devicetree.org/meta-schemas/core.yaml#
> +
> +title: Amlogic A9 I2C Controller
> +
> +maintainers:
> +  - Xianwei Zhao <xianwei.zhaol@amlogic.com>
> +  - Junyi Zhao <junyi.zhaol@amlogic.com>

[Severity: Low]
This isn't a functional bug, but are these email addresses misspelled?

The trailing 'l' in 'zhaol' causes emails to bounce when contributors
use get_maintainer.pl to CC the maintainers on patches modifying this
binding.

[ ... ]

> +examples:
> +  - |
> +    i2c@3a4400 {
> +        compatible = "amlogic,a9-i2c";
> +        reg = <0x3a4400 0x3c>;
> +        interrupts = <1 164 1>;

[Severity: Low]
Is this GIC interrupt specifier in the examples block correct?

The first cell value of 1 designates a GIC_PPI (Per-Processor Interrupt),
which is limited to the range 0-15. A value of 164 is highly invalid for a
PPI.

Since I2C controllers are typically shared peripherals, should this be 0
(GIC_SPI) instead?

Developers copy-pasting the example will create invalid device trees that
fail at runtime or during dtc validation.

> +        clocks = <&clkc_periphs 11>;
> +        #address-cells = <1>;
> +        #size-cells = <0>;
> +
> +        eeprom@52 {
> +            compatible = "atmel,24c32";
> +            reg = <0x52>;
> +        };
> +    };

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/20260924-a9-i2c-v1-0-b8ad9b46f4a8@amlogic.com?part=1

_______________________________________________
linux-amlogic mailing list
linux-amlogic@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-amlogic

  reply	other threads:[~2026-09-24  8:46 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-24  8:39 [PATCH 0/3] i2c: Add driver support Amlogic A9 I2C Xianwei Zhao via B4 Relay
2026-09-24  8:39 ` Xianwei Zhao via B4 Relay
2026-09-24  8:39 ` Xianwei Zhao
2026-09-24  8:39 ` [PATCH 1/3] dt-bindings: i2c: add Amlogic A9 I2C controller Xianwei Zhao via B4 Relay
2026-09-24  8:39   ` Xianwei Zhao via B4 Relay
2026-09-24  8:39   ` Xianwei Zhao
2026-09-24  8:46   ` sashiko-bot [this message]
2026-09-24  8:46     ` sashiko-bot
2026-09-24 17:01   ` Conor Dooley
2026-09-24 17:01     ` Conor Dooley
2026-09-29  3:11     ` Xianwei Zhao
2026-09-29  3:11       ` Xianwei Zhao
2026-09-24  8:39 ` [PATCH 2/3] i2c: amlogic: Add Amlogic A9 I2C controller driver Xianwei Zhao via B4 Relay
2026-09-24  8:39   ` Xianwei Zhao via B4 Relay
2026-09-24  8:39   ` Xianwei Zhao
2026-09-24  8:57   ` sashiko-bot
2026-09-24  8:57     ` sashiko-bot
2026-09-27 12:08   ` Andi Shyti
2026-09-27 12:08     ` Andi Shyti
2026-09-29  5:53     ` Xianwei Zhao
2026-09-29  5:53       ` Xianwei Zhao
2026-09-24  8:39 ` [PATCH 3/3] MAINTAINERS: Add an entry for Amlogic I2C driver Xianwei Zhao via B4 Relay
2026-09-24  8:39   ` Xianwei Zhao via B4 Relay
2026-09-24  8:39   ` Xianwei Zhao

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=20260924084646.489AD1F00893@smtp.kernel.org \
    --to=sashiko-bot@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=linux-amlogic@lists.infradead.org \
    --cc=neil.armstrong@linaro.org \
    --cc=robh@kernel.org \
    --cc=sashiko-reviews@lists.linux.dev \
    --cc=xianwei.zhao@amlogic.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.