From: Krzysztof Kozlowski <krzk@kernel.org>
To: Conor Dooley <conor@kernel.org>
Cc: Kendall Willis <k-willis@ti.com>,
Markus Schneider-Pargmann <msp@baylibre.com>,
Marc Kleine-Budde <mkl@pengutronix.de>,
Vincent Mailhol <mailhol@kernel.org>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Chandrasekar Ramakrishnan <rcsekar@samsung.com>,
s-kochidanadu@ti.com, a-kaur@ti.com, s-tripathi1@ti.com,
vishalm@ti.com, linux-can@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 1/2] dt-bindings: can: m_can: add out-band-wakeup property
Date: Fri, 28 Aug 2026 11:07:29 +0200 [thread overview]
Message-ID: <20260828-antique-lumpy-donkey-51ff42@quoll> (raw)
In-Reply-To: <20260824-public-mashing-252473f928c3@spud>
On Mon, Aug 24, 2026 at 05:50:20PM +0100, Conor Dooley wrote:
> On Fri, Aug 21, 2026 at 02:05:11PM -0500, Kendall Willis wrote:
> > On 17:45-20260821, Conor Dooley wrote:
> > > On Fri, Aug 21, 2026 at 11:07:00AM -0500, Kendall Willis wrote:
> > > > Add the out-band-wakeup property as a possible property. The property
> > > > indicates that the device can wakeup the system even when its power
> > > > domain is off.
> > > >
> > > > Signed-off-by: Kendall Willis <k-willis@ti.com>
> > > > ---
> > > > Documentation/devicetree/bindings/net/can/bosch,m_can.yaml | 2 ++
> > > > 1 file changed, 2 insertions(+)
> > > >
> > > > diff --git a/Documentation/devicetree/bindings/net/can/bosch,m_can.yaml b/Documentation/devicetree/bindings/net/can/bosch,m_can.yaml
> > > > index 2c9d37975bedd652b3060ab11ba75c37565edaad..0663beaa532bcc4a71cd6ad01520a4dfea294d0c 100644
> > > > --- a/Documentation/devicetree/bindings/net/can/bosch,m_can.yaml
> > > > +++ b/Documentation/devicetree/bindings/net/can/bosch,m_can.yaml
> > > > @@ -150,6 +150,8 @@ properties:
> > > > description:
> > > > List of phandles to system idle states in which mcan can wakeup the system.
> > > >
> > > > + out-band-wakeup: true
> > >
> > > Where is "-wakeup" defined genericly, or out-band-wakeup defined that
> > > you're getting the property definition from?
> >
> > I sent a PR to define out-band-wakeup in the wakeup-source.yaml binding
> > in dt-schema repo. I figured it made more sense to be defined in the
> > wakeup-source.yaml binding to allow other drivers the option to use it.
> >
> > dt-schema PR:
> > https://github.com/devicetree-org/dt-schema/pull/205
>
> This sounds like something you should be able to determine from
> device specific compatibles for these platforms. Not sure why they are
> not used for this particular device, but this is an indication to me
> that that is a mistake.
Yeah, it looks a bit too much replicating Linux PM detail. I can imagine
that some devices on some board are capable of waking up the system even
when power domain is off, but this does not look like a capability of
the actual device, but power domain. Device does not have different
wakeups. (by device I mean this individual schema - Bosch CAN)
Happy to see some bigger picture through DTS or board layouts. Actually
DTS, showing same Bosch CAN devices which are different on a board -
some are wakeups and some out of band wakeups - would illustrate it
better.
Best regards,
Krzysztof
next prev parent reply other threads:[~2026-08-28 9:07 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-21 16:06 [PATCH v3 0/2] can: m_can: support out-of-band wakeup capability Kendall Willis
2026-08-21 16:07 ` [PATCH v3 1/2] dt-bindings: can: m_can: add out-band-wakeup property Kendall Willis
2026-08-21 16:16 ` sashiko-bot
2026-08-21 16:45 ` Conor Dooley
2026-08-21 19:05 ` Kendall Willis
2026-08-24 16:50 ` Conor Dooley
2026-08-28 9:07 ` Krzysztof Kozlowski [this message]
2026-08-28 15:46 ` Conor Dooley
2026-08-28 18:43 ` Markus Schneider-Pargmann
2026-08-31 15:13 ` Conor Dooley
2026-08-31 16:22 ` Kendall Willis
2026-08-21 16:07 ` [PATCH v3 2/2] can: m_can: set out-of-band wakeup if wakeup pinctrl exists Kendall Willis
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=20260828-antique-lumpy-donkey-51ff42@quoll \
--to=krzk@kernel.org \
--cc=a-kaur@ti.com \
--cc=conor+dt@kernel.org \
--cc=conor@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=k-willis@ti.com \
--cc=krzk+dt@kernel.org \
--cc=linux-can@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mailhol@kernel.org \
--cc=mkl@pengutronix.de \
--cc=msp@baylibre.com \
--cc=rcsekar@samsung.com \
--cc=robh@kernel.org \
--cc=s-kochidanadu@ti.com \
--cc=s-tripathi1@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.