From: Russell King - ARM Linux <linux@armlinux.org.uk>
To: Alessandro Zummo <a.zummo@towertech.it>
Cc: linux-rtc@vger.kernel.org,
Linus Walleij <linus.walleij@linaro.org>,
Alexandre Belloni <alexandre.belloni@free-electrons.com>,
linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 0/4] Make PL031 interrupt optional
Date: Fri, 29 Sep 2017 11:21:16 +0100 [thread overview]
Message-ID: <20170929102116.GX20805@n2100.armlinux.org.uk> (raw)
There are some boards out there which have a PL031 RTC, but its
interrupt is not wired up. To support these, we need the PL031
to support the primecell without interrupts.
When no interrupt is present, there's little point exposing the
RTC's alarm capabilities, so we omit the alarm-related function
calls - the RTC merely becomes a source of time-of-day.
This patch series cleans up the pl031 driver a little, and adds
support for this configuration.
drivers/rtc/rtc-pl031.c | 48 +++++++++++++++++++++++++++---------------------
1 file changed, 27 insertions(+), 21 deletions(-)
v2: update patch 2 & 3 for review comment on v1.
--
RMK's Patch system: http://www.armlinux.org.uk/developer/patches/
FTTC broadband for 0.8mile line in suburbia: sync at 8.8Mbps down 630kbps up
According to speedtest.net: 8.21Mbps down 510kbps up
next reply other threads:[~2017-09-29 10:21 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-29 10:21 Russell King - ARM Linux [this message]
2017-09-29 10:22 ` [PATCH v2 1/4] rtc: pl031: constify amba_ids Russell King
2017-09-29 10:22 ` [PATCH v2 2/4] rtc: pl031: use devm_* for allocating memory and mapping resource Russell King
2017-09-29 10:22 ` [PATCH v2 3/4] rtc: pl031: avoid exposing alarm if no interrupt Russell King
2017-09-29 10:22 ` [PATCH v2 4/4] rtc: pl031: make interrupt optional Russell King
2017-10-01 15:03 ` [PATCH v2 0/4] Make PL031 " Linus Walleij
2017-10-12 15:07 ` 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=20170929102116.GX20805@n2100.armlinux.org.uk \
--to=linux@armlinux.org.uk \
--cc=a.zummo@towertech.it \
--cc=alexandre.belloni@free-electrons.com \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-rtc@vger.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