From: Alexandre Belloni <alexandre.belloni@bootlin.com>
To: Krzysztof Kozlowski <krzk@kernel.org>
Cc: "Markus Probst" <markus.probst@posteo.de>,
"Rob Herring" <robh@kernel.org>,
"Krzysztof Kozlowski" <krzk+dt@kernel.org>,
"Conor Dooley" <conor+dt@kernel.org>,
"Uwe Kleine-König" <uwe@kleine-koenig.org>,
"Andrew Lunn" <andrew@lunn.ch>,
"Gregory Clement" <gregory.clement@bootlin.com>,
"Sebastian Hesselbarth" <sebastian.hesselbarth@gmail.com>,
linux-arm-kernel@lists.infradead.org, linux-rtc@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/3] dt-bindings: rtc: Add sii,wakealarm-output-pin property for S35390A
Date: Thu, 2 Jul 2026 10:17:01 +0200 [thread overview]
Message-ID: <202607020817017cde494f@mail.local> (raw)
In-Reply-To: <187099d0-5e09-49c2-b67d-8bd4366ff1a0@kernel.org>
On 02/07/2026 08:09:55+0200, Krzysztof Kozlowski wrote:
> >> Then you need proper wakeup-source support
> > Wouldn't that break existing devicetrees?
>
> How?
>
> >
> > The current driver allows to wake up the system, even without
> > having wakeup-source set.
>
> Anyway, wakeup-source is already there in rtc, so this would be done. I
> don't get though, why there is no benefit of routing it to interrupt
> controller (interrupt controllers do wake up the system). Additionally,
> if you do not connect it to any interrupt, then how does it wake up the
> system?
>
Some systems are routing the interrupt output of the RTC directly to the
PMIC and the PMIC is the one responsible for waking the rest of the
system, including the SoC.
--
Alexandre Belloni, co-owner and COO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2026-07-02 8:17 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-30 19:22 [PATCH 0/3] rtc: s35390a: Allow use of output pin for interrupt signal 1 for wakealarm Markus Probst
2026-06-30 19:22 ` [PATCH 1/3] dt-bindings: rtc: Add sii,wakealarm-output-pin property for S35390A Markus Probst
2026-07-01 7:35 ` Krzysztof Kozlowski
2026-07-01 13:25 ` Markus Probst
2026-07-01 15:11 ` Alexandre Belloni
2026-07-01 15:14 ` Krzysztof Kozlowski
2026-07-01 16:43 ` Markus Probst
2026-07-01 16:48 ` Alexandre Belloni
2026-07-01 17:08 ` Markus Probst
2026-07-02 6:09 ` Krzysztof Kozlowski
2026-07-02 8:17 ` Alexandre Belloni [this message]
2026-07-02 8:20 ` Krzysztof Kozlowski
2026-07-02 8:35 ` Alexandre Belloni
2026-07-01 15:06 ` Alexandre Belloni
2026-07-01 17:34 ` Markus Probst
2026-06-30 19:22 ` [PATCH 2/3] rtc: s35390a: Add missing newline to dev_err Markus Probst
2026-06-30 19:22 ` [PATCH 3/3] rtc: s35390a: make use of interrupt signal 1 Markus Probst
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=202607020817017cde494f@mail.local \
--to=alexandre.belloni@bootlin.com \
--cc=andrew@lunn.ch \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=gregory.clement@bootlin.com \
--cc=krzk+dt@kernel.org \
--cc=krzk@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rtc@vger.kernel.org \
--cc=markus.probst@posteo.de \
--cc=robh@kernel.org \
--cc=sebastian.hesselbarth@gmail.com \
--cc=uwe@kleine-koenig.org \
/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