[PATCH v4 0/2] can: m_can: introduce ti,am62-m_can compatible for out-of-band wakeup

From: Kendall Willis

Date: Wed Sep 02 2026 - 17:15:08 EST


This series introduces the "ti,am62-m_can" compatible which adds support
for out-of-band wakeup capability in m_can devices.

A corresponding DTS series enabling this feature on TI K3 AM62 family
of devices has been submitted separately:
"arm64: dts: ti: use ti,am62-m_can compatible for m_can devices"

Testing
-------
Tested suspend/resume with CAN wakeup on AM62P SK EVM.

Signed-off-by: Kendall Willis <k-willis@xxxxxx>
---
Changes in v4:
- Remove patch for "out-band-wakeup" property in dt binding.
- Create "ti,am62-m_can" compatible in the dt binding and m_can driver.
- Add "struct m_can_pdata" for compatible-specific data which keeps track
of "out_band_wakeup" flag.
- Replace check "out-band-wakeup" dt property in the device driver upon
suspend with check for "out_band_wakeup" variable from the
"m_can_pdata".
- Link to v3: https://lore.kernel.org/r/20260821-temp-v3-0-9ac1f8806929@xxxxxx

Changes in v3:
- Remove definition of "out-band-wakeup" property in dt binding.
- Allow "out-band-wakeup" property in dt binding.
- Link to v2: https://lore.kernel.org/r/20260820-temp-v2-0-dd3f8cacc15e@xxxxxx

Changes in v2:
- Create "out-band-wakeup" property in dt bindings.
- Use "out-band-wakeup" property to set the out_band_wakeup flag upon
suspend.
- Rebase to v7.2
- Link to v1: https://lore.kernel.org/r/20260213-mcan-out-of-band-v1-1-af68d4c570b3@xxxxxx

---
Kendall Willis (2):
dt-bindings: can: m_can: add ti,am62-m_can compatible
can: m_can: add ti,am62-m_can compatible with out-of-band wakeup support

Documentation/devicetree/bindings/net/can/bosch,m_can.yaml | 4 +++-
drivers/net/can/m_can/m_can.c | 7 ++++++-
drivers/net/can/m_can/m_can.h | 4 ++++
drivers/net/can/m_can/m_can_platform.c | 5 +++++
4 files changed, 18 insertions(+), 2 deletions(-)
---
base-commit: cee9395acd8043be0644b25c34bfa86623f2b935
change-id: 20260819-temp-93299bee27b7

Best regards,
--
Kendall Willis <k-willis@xxxxxx>