From: Russell King - ARM Linux <linux@armlinux.org.uk>
To: Alessandro Zummo <a.zummo@towertech.it>
Cc: Alexandre Belloni <alexandre.belloni@free-electrons.com>,
Linus Walleij <linus.walleij@linaro.org>,
linux-arm-kernel@lists.infradead.org, linux-rtc@vger.kernel.org
Subject: [PATCH 0/4] Make PL031 interrupt optional
Date: Fri, 21 Jul 2017 00:17:45 +0100 [thread overview]
Message-ID: <20170720231745.GE31807@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 pu the pl031 driver a little, and adds
support for this configuration.
drivers/rtc/rtc-pl031.c | 48 +++++++++++++++++++++++++++---------------------
1 file changed, 27 insertions(+), 21 deletions(-)
--
RMK's Patch system: http://www.armlinux.org.uk/developer/patches/
FTTC broadband for 0.8mile line: currently at 9.6Mbps down 400kbps up
according to speedtest.net.
WARNING: multiple messages have this Message-ID (diff)
From: linux@armlinux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/4] Make PL031 interrupt optional
Date: Fri, 21 Jul 2017 00:17:45 +0100 [thread overview]
Message-ID: <20170720231745.GE31807@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 pu the pl031 driver a little, and adds
support for this configuration.
drivers/rtc/rtc-pl031.c | 48 +++++++++++++++++++++++++++---------------------
1 file changed, 27 insertions(+), 21 deletions(-)
--
RMK's Patch system: http://www.armlinux.org.uk/developer/patches/
FTTC broadband for 0.8mile line: currently at 9.6Mbps down 400kbps up
according to speedtest.net.
next reply other threads:[~2017-07-20 23:17 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-20 23:17 Russell King - ARM Linux [this message]
2017-07-20 23:17 ` [PATCH 0/4] Make PL031 interrupt optional Russell King - ARM Linux
2017-07-20 23:18 ` [PATCH 1/4] rtc: pl031: constify amba_ids Russell King
2017-07-20 23:18 ` Russell King
2017-08-02 12:30 ` Linus Walleij
2017-08-02 12:30 ` Linus Walleij
2017-07-20 23:18 ` [PATCH 2/4] rtc: pl031: use devm_* for allocating memory and mapping resource Russell King
2017-07-20 23:18 ` Russell King
2017-08-02 12:31 ` Linus Walleij
2017-08-02 12:31 ` Linus Walleij
2017-08-10 21:05 ` Alexandre Belloni
2017-08-10 21:05 ` Alexandre Belloni
2017-07-20 23:18 ` [PATCH 3/4] rtc: pl031: avoid exposing alarm if no interrupt Russell King
2017-07-20 23:18 ` Russell King
2017-08-02 12:32 ` Linus Walleij
2017-08-02 12:32 ` Linus Walleij
2017-07-20 23:18 ` [PATCH 4/4] rtc: pl031: make interrupt optional Russell King
2017-07-20 23:18 ` Russell King
2017-08-02 12:33 ` Linus Walleij
2017-08-02 12:33 ` Linus Walleij
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=20170720231745.GE31807@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 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.