From: Doug Berger <opendmb@gmail.com>
To: Alessandro Zummo <a.zummo@towertech.it>,
Alexandre Belloni <alexandre.belloni@bootlin.com>
Cc: Brian Norris <computersforpeace@gmail.com>,
Markus Mayer <mmayer@broadcom.com>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Florian Fainelli <f.fainelli@gmail.com>,
Broadcom internal kernel review list
<bcm-kernel-feedback-list@broadcom.com>,
linux-rtc@vger.kernel.org, devicetree@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, Doug Berger <opendmb@gmail.com>
Subject: [PATCH v2 0/2] rtc: brcmstb-waketimer: add RTC alarm irq
Date: Tue, 24 Jan 2023 12:14:28 -0800 [thread overview]
Message-ID: <20230124201430.2502371-1-opendmb@gmail.com> (raw)
Support is added for an interrupt that can be triggered from the
brcmstb-waketimer hardware while the system is awake.
This interrupt allows the driver to pass the rtctest selftest.
Changes in v2:
- Squashed examples in the bindings document.
- Added Ack from Florian
Doug Berger (2):
dt-bindings: rtc: brcm,brcmstb-waketimer: add alarm interrupt
rtc: brcmstb-waketimer: allow use as non-wake alarm
.../bindings/rtc/brcm,brcmstb-waketimer.yaml | 21 ++++---
drivers/rtc/rtc-brcmstb-waketimer.c | 55 ++++++++++++++++++-
2 files changed, 66 insertions(+), 10 deletions(-)
--
2.25.1
next reply other threads:[~2023-01-24 20:15 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-24 20:14 Doug Berger [this message]
2023-01-24 20:14 ` [PATCH v2 1/2] dt-bindings: rtc: brcm,brcmstb-waketimer: add alarm interrupt Doug Berger
2023-01-25 7:37 ` Krzysztof Kozlowski
2023-01-25 17:33 ` Florian Fainelli
2023-01-24 20:14 ` [PATCH v2 2/2] rtc: brcmstb-waketimer: allow use as non-wake alarm Doug Berger
2023-01-25 17:55 ` [PATCH v2 0/2] rtc: brcmstb-waketimer: add RTC alarm irq Alexandre Belloni
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=20230124201430.2502371-1-opendmb@gmail.com \
--to=opendmb@gmail.com \
--cc=a.zummo@towertech.it \
--cc=alexandre.belloni@bootlin.com \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=computersforpeace@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=f.fainelli@gmail.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rtc@vger.kernel.org \
--cc=mmayer@broadcom.com \
--cc=robh+dt@kernel.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;
as well as URLs for NNTP newsgroup(s).