The Linux Kernel Mailing List
 help / color / mirror / Atom feed
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>, <linux-arm-kernel@lists.infradead.org>,
	<devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 0/4] arm64: dts: ti: add out-band-wakeup property to m_can devices
Date: Fri, 21 Aug 2026 11:09:02 -0500	[thread overview]
Message-ID: <20260821160902.dvg7semggxpuches@uda0506412> (raw)
In-Reply-To: <20260820-smth-v1-0-e1738a38d58e@ti.com>

On 17:08-20260820, Kendall Willis wrote:
> This series adds out-of-band wakeup support for the m_can devices in the
> device tree of AM62X-LP, AM62A, AM62D, and AM62P SoCs by integrating
> the out-band-wakeup property.
> 
> Dependency
> ----------
> This series depends on the "can: m_can: support out-of-band wakeup
> capability" series which implements the out-of-band wakeup support in
> the m_can driver and dt bindings.

Additional dependency on PR in dt-schema repository that defines the
"out-band-wakeup" property:
https://github.com/devicetree-org/dt-schema/pull/205

> 
> Testing
> -------
> Tested suspend/resume with CAN wakeup on AM62P SK EVM.
> 
> Signed-off-by: Kendall Willis <k-willis@ti.com>
> ---
> Kendall Willis (4):
>       arm64: dts: ti: k3-am62-lp-sk: add out-band-wakeup property to m_can devices
>       arm64: dts: ti: k3-am62a7-sk: add out-band-wakeup property to m_can devices
>       arm64: dts: ti: k3-am62p5-sk: add out-band-wakeup property to m_can devices
>       arm64: dts: ti: k3-am62d2-evm: add out-band-wakeup property to m_can devices
> 
>  arch/arm64/boot/dts/ti/k3-am62-lp-sk.dts | 2 ++
>  arch/arm64/boot/dts/ti/k3-am62a7-sk.dts  | 2 ++
>  arch/arm64/boot/dts/ti/k3-am62d2-evm.dts | 2 ++
>  arch/arm64/boot/dts/ti/k3-am62p5-sk.dts  | 2 ++
>  4 files changed, 8 insertions(+)
> ---
> base-commit: 8d3ae59288f1e7d58d76558a6ee96d533bc5019f
> change-id: 20260819-smth-6fb189fc148f
> 
> Best regards,
> -- 
> Kendall Willis <k-willis@ti.com>
> 

      parent reply	other threads:[~2026-08-21 16:09 UTC|newest]

Thread overview: 6+ 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:08 ` [PATCH 2/4] arm64: dts: ti: k3-am62a7-sk: " Kendall Willis
2026-08-20 22:08 ` [PATCH 3/4] arm64: dts: ti: k3-am62p5-sk: " Kendall Willis
2026-08-20 22:08 ` [PATCH 4/4] arm64: dts: ti: k3-am62d2-evm: " Kendall Willis
2026-08-21 16:09 ` Kendall Willis [this message]

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=20260821160902.dvg7semggxpuches@uda0506412 \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox