From: sashiko-bot@kernel.org
To: "Andreas Kemnade" <andreas@kemnade.info>
Cc: devicetree@vger.kernel.org, robh@kernel.org, conor+dt@kernel.org
Subject: Re: [PATCH 2/3] ARM: dts: ti/omap: describe omap3 i2c via ti-sysc
Date: Tue, 10 Nov 2026 11:02:24 +0000 [thread overview]
Message-ID: <sashiko-outbox-206915@kernel.org> (raw)
In-Reply-To: <20261110-i2c-sysc-v1-2-8945eb1d38f0@kemnade.info>
Thank you for your contribution! Sashiko AI review found 1 potential
issue to consider:
- [High] ARM: dts: ti/omap: typo ti-sysc-sidle in omap3.dtsi breaks I2C
idle modes
--
commit 7b585c63ba05ca384163221aab8d44c23e10bcd7
Author: Andreas Kemnade <andreas@kemnade.info>
ARM: dts: ti/omap: describe omap3 i2c via ti-sysc
This commit converts the OMAP3 I2C controller device tree nodes from the
deprecated ti,hwmods binding to ti-sysc target-module nodes.
> diff --git a/arch/arm/boot/dts/ti/omap/omap3.dtsi b/arch/arm/boot/dts/ti/omap/omap3.dtsi
> index 447736d2e53ca..42d80c7a0a854 100644
> --- a/arch/arm/boot/dts/ti/omap/omap3.dtsi
> +++ b/arch/arm/boot/dts/ti/omap/omap3.dtsi
> @@ -396,31 +396,91 @@ uart3: serial@49020000 {
> clock-frequency = <48000000>;
> };
>
> - i2c1: i2c@48070000 {
> - compatible = "ti,omap3-i2c";
> - reg = <0x48070000 0x80>;
> - interrupts = <56>;
> + i2c1_target: target-module@48070000 {
> + compatible = "ti,sysc-omap2", "ti,sysc";
> + reg = <0x48070000 0x4>,
> + <0x48070020 0x4>,
> + <0x48070010 0x4>;
> + reg-names = "rev", "sysc", "syss";
> + ti,sysc-mask = <(SYSC_OMAP2_CLOCKACTIVITY |
> + SYSC_OMAP2_ENAWAKEUP |
> + SYSC_OMAP2_SOFTRESET |
> + SYSC_OMAP2_AUTOIDLE)>;
> + ti-sysc-sidle = <SYSC_IDLE_FORCE>,
> + <SYSC_IDLE_NO>,
> + <SYSC_IDLE_SMART>;
[Severity: High]
Should ti-sysc-sidle be ti,sysc-sidle here and in i2c2_target and
i2c3_target below?
sysc_init_idlemodes() looks up "ti,sysc-sidle", so this property is
ignored and ddata->cfg.sidlemodes remains 0 for all three I2C target
modules. As a result, sysc_enable_module() and sysc_disable_module()
skip programming SIDLEMODE and ENAWAKEUP in the I2C_SYSC register,
breaking I2C idle mode and wakeup configuration on OMAP3 (as well as
failing dtbs_check).
--
Sashiko AI review · https://sashiko.dev/#/patchset/20261110-i2c-sysc-v1-0-8945eb1d38f0@kemnade.info?part=2
next prev parent reply other threads:[~2026-11-10 11:02 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-10 10:46 [PATCH 0/3] ARM: OMAP2+: Convert OMAP3 I2C to ti-sysc Andreas Kemnade
2026-11-10 10:46 ` [PATCH 1/3] bus: ti-sysc: fix I2C quirk for OMAP3 variants Andreas Kemnade
2026-11-10 11:12 ` sashiko-bot
2026-11-10 20:18 ` kernel test robot
2026-11-10 10:46 ` [PATCH 2/3] ARM: dts: ti/omap: describe omap3 i2c via ti-sysc Andreas Kemnade
2026-11-10 11:02 ` sashiko-bot [this message]
2026-11-10 10:46 ` [PATCH 3/3] ARM: OMAP2+: remove i2c from OMAP3 hwmods list Andreas Kemnade
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=sashiko-outbox-206915@kernel.org \
--to=sashiko-bot@kernel.org \
--cc=andreas@kemnade.info \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.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.