From: Kendall Willis <k-willis@ti.com>
To: Nishanth Menon <nm@ti.com>, Vignesh Raghavendra <vigneshr@ti.com>,
"Tero Kristo" <kristo@kernel.org>, Rob Herring <robh@kernel.org>,
"Krzysztof Kozlowski" <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>
Cc: <s-kochidanadu@ti.com>, <a-kaur@ti.com>, <s-tripathi1@ti.com>,
<vishalm@ti.com>, <k-willis@ti.com>,
<linux-arm-kernel@lists.infradead.org>,
<devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: [PATCH v3 1/3] arm64: dts: ti: k3-am62: use ti,am62-mcan compatible for m_can devices
Date: Sat, 12 Sep 2026 16:32:13 -0500 [thread overview]
Message-ID: <20260912-smth-v3-1-6fa661ae5a4c@ti.com> (raw)
In-Reply-To: <20260912-smth-v3-0-6fa661ae5a4c@ti.com>
Prepend "ti,am62-mcan" to the m_can device compatible property since
this compatible adds out-of-band wakeup functionality. The m_can pins
can be a wakeup source in the deepest low power states, despite being
in power domains which are OFF during deeper low power states since
it has the out-of-band wakeup capability.
Signed-off-by: Kendall Willis <k-willis@ti.com>
---
arch/arm64/boot/dts/ti/k3-am62-main.dtsi | 2 +-
arch/arm64/boot/dts/ti/k3-am62-mcu.dtsi | 4 ++--
2 files changed, 3 insertions(+), 3 deletions(-)
diff --git a/arch/arm64/boot/dts/ti/k3-am62-main.dtsi b/arch/arm64/boot/dts/ti/k3-am62-main.dtsi
index c5ee263d34a62ef46b416ffa45bc2ec5c28d010a..4c7e793d84a0e0f2ad3084ae41ae7ba97e8e2b62 100644
--- a/arch/arm64/boot/dts/ti/k3-am62-main.dtsi
+++ b/arch/arm64/boot/dts/ti/k3-am62-main.dtsi
@@ -933,7 +933,7 @@ eqep2: counter@23220000 {
};
main_mcan0: can@20701000 {
- compatible = "bosch,m_can";
+ compatible = "ti,am62-mcan", "bosch,m_can";
reg = <0x00 0x20701000 0x00 0x200>,
<0x00 0x20708000 0x00 0x8000>;
reg-names = "m_can", "message_ram";
diff --git a/arch/arm64/boot/dts/ti/k3-am62-mcu.dtsi b/arch/arm64/boot/dts/ti/k3-am62-mcu.dtsi
index 68e906796aefebc5eaaa5a231e56105a9cdd13e5..a21e3b889159b2ed8ea05af8543a589e96ff143d 100644
--- a/arch/arm64/boot/dts/ti/k3-am62-mcu.dtsi
+++ b/arch/arm64/boot/dts/ti/k3-am62-mcu.dtsi
@@ -152,7 +152,7 @@ mcu_rti0: watchdog@4880000 {
};
mcu_mcan0: can@4e08000 {
- compatible = "bosch,m_can";
+ compatible = "ti,am62-mcan", "bosch,m_can";
reg = <0x00 0x4e08000 0x00 0x200>,
<0x00 0x4e00000 0x00 0x8000>;
reg-names = "m_can", "message_ram";
@@ -164,7 +164,7 @@ mcu_mcan0: can@4e08000 {
};
mcu_mcan1: can@4e18000 {
- compatible = "bosch,m_can";
+ compatible = "ti,am62-mcan", "bosch,m_can";
reg = <0x00 0x4e18000 0x00 0x200>,
<0x00 0x4e10000 0x00 0x8000>;
reg-names = "m_can", "message_ram";
--
2.34.1
next prev parent reply other threads:[~2026-09-12 21:32 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-12 21:32 [PATCH v3 0/3] arm64: dts: ti: use ti,am62-mcan compatible for m_can devices Kendall Willis
2026-09-12 21:32 ` Kendall Willis [this message]
2026-09-12 21:40 ` [PATCH v3 1/3] arm64: dts: ti: k3-am62: " sashiko-bot
2026-09-12 21:32 ` [PATCH v3 2/3] arm64: dts: ti: k3-am62a: " Kendall Willis
2026-09-12 21:40 ` sashiko-bot
2026-09-12 21:32 ` [PATCH v3 3/3] arm64: dts: ti: k3-am62p: " Kendall Willis
2026-09-12 21:41 ` 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=20260912-smth-v3-1-6fa661ae5a4c@ti.com \
--to=k-willis@ti.com \
--cc=a-kaur@ti.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=kristo@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nm@ti.com \
--cc=robh@kernel.org \
--cc=s-kochidanadu@ti.com \
--cc=s-tripathi1@ti.com \
--cc=vigneshr@ti.com \
--cc=vishalm@ti.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.