linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: dgilbert@interlog.com (Douglas Gilbert)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] rtc: rtc-at91sam9.c add DT support
Date: Wed, 03 Apr 2013 23:54:45 -0400	[thread overview]
Message-ID: <515CF985.6050009@interlog.com> (raw)

Some members of the at91 SoCs use the Real Time Timer (RTT)
and the General Purpose Backup Registers (GPBR) to implement
a real time clock (RTC). The AT91SAM9G20 is one example.

Attached is a patch to add DT support to rtc-at91sam9.c .
The patch is against lk 3.9.0-rc5 .

Below is a snippet of DT code for the 'G20 that was observed
to work with this patch:

ahb {
	apb {

		rtc {
			compatible = "atmel,at91sam9-rtc";
                          /* RTTC followed by GPBR (backup registers) */
                          reg = <0xfffffd20 0x10>, <0xfffffd50 0x10>;
                          interrupts = <1 4 7>;
                          status = "okay";
		};
	}
};

Signed-off-by: Douglas Gilbert <dgilbert@interlog.com>

-------------- next part --------------
A non-text attachment was scrubbed...
Name: fg20_rtc_at91sam9.patch
Type: text/x-patch
Size: 1015 bytes
Desc: not available
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20130403/2c30a653/attachment.bin>

             reply	other threads:[~2013-04-04  3:54 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-04  3:54 Douglas Gilbert [this message]
2013-04-04  8:11 ` [PATCH] rtc: rtc-at91sam9.c add DT support Nicolas Ferre
2013-04-04 13:25   ` Douglas Gilbert
2013-04-04 14:08     ` Nicolas Ferre
2013-04-04 19:14       ` Douglas Gilbert
2013-04-07 15:09       ` Johan Hovold
     [not found]         ` <1365347572-14972-1-git-send-email-jhovold@gmail.com>
2013-04-08  7:33           ` [RFC 1/5] ARM: at91: add general purpose backup register (GPBR) support Jean-Christophe PLAGNIOL-VILLARD
2013-04-08  8:46             ` Johan Hovold
2013-04-08 10:04               ` Jean-Christophe PLAGNIOL-VILLARD
2013-04-11 12:39                 ` Johan Hovold
2013-04-11 14:53                   ` Jean-Christophe PLAGNIOL-VILLARD
     [not found]           ` <1365347572-14972-2-git-send-email-jhovold@gmail.com>
2013-04-08  7:35             ` [RFC 2/5] ARM: at91/dts: " Jean-Christophe PLAGNIOL-VILLARD
     [not found]           ` <1365347572-14972-4-git-send-email-jhovold@gmail.com>
2013-04-08  7:38             ` [RFC 4/5] RTC: rtc-at91sam9: add device-tree support Jean-Christophe PLAGNIOL-VILLARD
2013-04-08  9:00               ` Johan Hovold
2013-04-08  9:57                 ` Nicolas Ferre
2013-04-08 10:03                   ` Jean-Christophe PLAGNIOL-VILLARD
2013-04-08 10:42                     ` Nicolas Ferre
2013-04-08 11:02                       ` Jean-Christophe PLAGNIOL-VILLARD
2013-04-08 10:48                     ` Johan Hovold
2013-04-08 11:08                       ` Jean-Christophe PLAGNIOL-VILLARD
2013-04-08 10:38                   ` Johan Hovold
2013-04-08 11:11                     ` Jean-Christophe PLAGNIOL-VILLARD
2013-04-11 12:57                       ` Johan Hovold
2013-04-04  8:16 ` [PATCH] rtc: rtc-at91sam9.c add DT support 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=515CF985.6050009@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).