All of lore.kernel.org
 help / color / mirror / Atom feed
From: sashiko-bot@kernel.org
To: "Kendall Willis" <k-willis@ti.com>
Cc: robh@kernel.org, conor+dt@kernel.org, devicetree@vger.kernel.org
Subject: Re: [PATCH 1/4] arm64: dts: ti: k3-am62-lp-sk: add out-band-wakeup property to m_can devices
Date: Thu, 20 Aug 2026 22:15:30 +0000	[thread overview]
Message-ID: <20260820221531.5773E1F000E9@smtp.kernel.org> (raw)
In-Reply-To: <20260820-smth-v1-1-e1738a38d58e@ti.com>

Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Medium] The `out-band-wakeup` property is added to the device tree but is completely ignored by the kernel because no driver or core code parses it.
--

--- Patch [1]: [PATCH 1/4] arm64: dts: ti: k3-am62-lp-sk: add out-band-wakeup property to m_can devices ---
commit 74f82c5ded5daaf7cf6527a753badc1049e2cd79
Author: Kendall Willis <k-willis@ti.com>

arm64: dts: ti: k3-am62-lp-sk: add out-band-wakeup property to m_can devices

This commit adds the out-band-wakeup property to the mcu_mcan0 and
mcu_mcan1 nodes in the k3-am62-lp-sk device tree. The commit message states
this allows the out_band_wakeup flag to be enabled during suspend for m_can
devices.

> diff --git a/arch/arm64/boot/dts/ti/k3-am62-lp-sk.dts b/arch/arm64/boot/dts/ti/k3-am62-lp-sk.dts
> index dfd65c00f5b95..011f2f3703755 100644
> --- a/arch/arm64/boot/dts/ti/k3-am62-lp-sk.dts
> +++ b/arch/arm64/boot/dts/ti/k3-am62-lp-sk.dts
> @@ -283,6 +283,7 @@ &gpmc0 {
>  };
>  
>  &mcu_mcan0 {
> +	out-band-wakeup;

[Severity: Medium]
Is this property parsed anywhere in the kernel?

Looking at the kernel code, there doesn't appear to be any driver or core
code that reads the out-band-wakeup property, nor does it seem to be defined
in any device tree bindings.

Without a driver (such as m_can) parsing this property and setting the flag,
the intended wakeup functionality from deep low power states will fail to
operate.

Are there missing driver changes that should accompany this device tree
modification to actually enable this feature?

>  	pinctrl-names = "default", "wakeup";
>  	pinctrl-0 = <&mcu_mcan0_tx_pins_default>, <&mcu_mcan0_rx_pins_default>;
>  	pinctrl-1 = <&mcu_mcan0_tx_pins_default>, <&mcu_mcan0_rx_pins_wakeup>;
> @@ -294,6 +295,7 @@ &mcu_mcan0 {
>  };
>  
>  &mcu_mcan1 {
> +	out-band-wakeup;
>  	pinctrl-names = "default", "wakeup";
>  	pinctrl-0 = <&mcu_mcan1_tx_pins_default>, <&mcu_mcan1_rx_pins_default>;

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/20260820-smth-v1-0-e1738a38d58e@ti.com?part=1

  reply	other threads:[~2026-08-20 22:15 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-20 22:08 [PATCH 0/4] arm64: dts: ti: add out-band-wakeup property to m_can devices Kendall Willis
2026-08-20 22:08 ` [PATCH 1/4] arm64: dts: ti: k3-am62-lp-sk: " Kendall Willis
2026-08-20 22:15   ` sashiko-bot [this message]
2026-08-20 22:08 ` [PATCH 2/4] arm64: dts: ti: k3-am62a7-sk: " Kendall Willis
2026-08-20 22:17   ` sashiko-bot
2026-08-20 22:08 ` [PATCH 3/4] arm64: dts: ti: k3-am62p5-sk: " Kendall Willis
2026-08-20 22:18   ` sashiko-bot
2026-08-20 22:08 ` [PATCH 4/4] arm64: dts: ti: k3-am62d2-evm: " Kendall Willis
2026-08-20 22:16   ` sashiko-bot

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=20260820221531.5773E1F000E9@smtp.kernel.org \
    --to=sashiko-bot@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=k-willis@ti.com \
    --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.