From: dgilbert@interlog.com (Douglas Gilbert)
To: linux-arm-kernel@lists.infradead.org
Subject: [RFC 5/5] rtc-at91rm9200: add support for at91sam9x5
Date: Fri, 29 Mar 2013 12:39:02 -0400 [thread overview]
Message-ID: <5155C3A6.4060109@interlog.com> (raw)
In-Reply-To: <1364573029-19346-5-git-send-email-jhovold@gmail.com>
On 13-03-29 12:03 PM, Johan Hovold wrote:
> Add support for the at91sam9x5-family which must use the shadow
> interrupt mask due to a hardware issue.
> ---
> drivers/rtc/rtc-at91rm9200.c | 8 ++++++++
> 1 file changed, 8 insertions(+)
>
> diff --git a/drivers/rtc/rtc-at91rm9200.c b/drivers/rtc/rtc-at91rm9200.c
> index 2921866..f3e351f 100644
> --- a/drivers/rtc/rtc-at91rm9200.c
> +++ b/drivers/rtc/rtc-at91rm9200.c
> @@ -318,12 +318,20 @@ static irqreturn_t at91_rtc_interrupt(int irq, void *dev_id)
> static const struct at91_rtc_config at91rm9200_config = {
> };
>
> +static const struct at91_rtc_config at91sam9x5_config = {
> + .use_shadow_imr = true,
> +};
> +
> #if defined(CONFIG_OF)
> static const struct of_device_id at91_rtc_dt_ids[] = {
> {
> .compatible = "atmel,at91rm9200-rtc",
> .data = &at91rm9200_config,
> },
> + {
> + .compatible = "atmel,at91sam9x5-rtc",
> + .data = &at91sam9x5_config,
> + },
> /* terminator */
> }
> };
>
Johan,
Looks good.
Plus add something like this to at91sam9x5.dtsi after the
i2c at 2 entry (at the end):
rtc {
compatible = "atmel,at91sam9x5-rtc";
reg = <0xfffffeb0 0x40>;
interrupts = <1 4 7>;
status = "disabled";
};
and an "enabler" in ariag25.dts (and perhaps other members
of the 9x5 sub-family), also at the end:
rtc {
status = "okay";
};
My patches are in Robert Nelson's tree at:
http://www.eewiki.net/display/linuxonarm/AT91SAM9x5
in the Linux kernel section. My RTC code amounts to the same
thing as you are proposing, without the safety code around
the IMR shadow.
I provide binaries based on that work to Aria G25 users
via a google group. No-one has complained about RTC not
working. SPI and I2C problems are on-going but gradually
being sorted. Hence I know people are using and testing
this code, other than me.
Doug Gilbert
next prev parent reply other threads:[~2013-03-29 16:39 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-29 16:03 [RFC 1/5] rtc-at91rm9200: add configuration support Johan Hovold
[not found] ` <1364573029-19346-2-git-send-email-jhovold@gmail.com>
2013-03-29 16:12 ` [RFC 2/5] rtc-at91rm9200: add device-tree support Johan Hovold
[not found] ` <1364573029-19346-5-git-send-email-jhovold@gmail.com>
2013-03-29 16:39 ` Douglas Gilbert [this message]
2013-04-02 13:06 ` [RFC PATCH] rtc: rtc-at91rm9200: manage IMR depending on revision Nicolas Ferre
2013-04-02 15:32 ` Douglas Gilbert
2013-04-02 16:28 ` Nicolas Ferre
2013-04-02 16:36 ` [RFC PATCH v2] " Nicolas Ferre
2013-04-03 9:51 ` Johan Hovold
2013-04-03 9:54 ` [PATCH] Revert "drivers/rtc/rtc-at91rm9200.c: use a variable for storing IMR" Johan Hovold
2013-04-03 10:18 ` Nicolas Ferre
2013-04-05 14:14 ` Nicolas Ferre
2013-04-05 15:35 ` Greg KH
2013-04-05 16:16 ` Nicolas Ferre
2013-04-03 10:37 ` [RFC PATCH v2] rtc: rtc-at91rm9200: manage IMR depending on revision Nicolas Ferre
2013-04-03 13:46 ` Johan Hovold
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=5155C3A6.4060109@interlog.com \
--to=dgilbert@interlog.com \
--cc=linux-arm-kernel@lists.infradead.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).