linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: andrew@lunn.ch (Andrew Lunn)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCHv2 04/15] [kirkwood] Add support for RTC interrupts which allows RTC alarms.
Date: Sun, 15 May 2011 13:32:43 +0200	[thread overview]
Message-ID: <1305459174-25517-5-git-send-email-andrew@lunn.ch> (raw)
In-Reply-To: <1305459174-25517-1-git-send-email-andrew@lunn.ch>

Tested using the test program in Documentation/rtc.txt

Signed-off-by: Andrew Lunn <andrew@lunn.ch>
---
 arch/arm/mach-kirkwood/common.c            |    2 +-
 arch/arm/mach-kirkwood/include/mach/irqs.h |    1 +
 2 files changed, 2 insertions(+), 1 deletions(-)

diff --git a/arch/arm/mach-kirkwood/common.c b/arch/arm/mach-kirkwood/common.c
index b77050e..f6868fc 100644
--- a/arch/arm/mach-kirkwood/common.c
+++ b/arch/arm/mach-kirkwood/common.c
@@ -328,7 +328,7 @@ void __init kirkwood_nand_init_rnb(struct mtd_partition *parts, int nr_parts,
  ****************************************************************************/
 static void __init kirkwood_rtc_init(void)
 {
-	orion_rtc_init(RTC_PHYS_BASE, NO_IRQ);
+	orion_rtc_init(RTC_PHYS_BASE, IRQ_KIRKWOOD_RTC);
 }
 
 
diff --git a/arch/arm/mach-kirkwood/include/mach/irqs.h b/arch/arm/mach-kirkwood/include/mach/irqs.h
index 9da2eb5..2bf8161 100644
--- a/arch/arm/mach-kirkwood/include/mach/irqs.h
+++ b/arch/arm/mach-kirkwood/include/mach/irqs.h
@@ -51,6 +51,7 @@
 #define IRQ_KIRKWOOD_GPIO_HIGH_16_23	41
 #define IRQ_KIRKWOOD_GE00_ERR	46
 #define IRQ_KIRKWOOD_GE01_ERR	47
+#define IRQ_KIRKWOOD_RTC        53
 
 /*
  * KIRKWOOD General Purpose Pins
-- 
1.7.4.4

  parent reply	other threads:[~2011-05-15 11:32 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-15 11:32 [PATCHv2 00/15] Consolidate Orion platform information setup Andrew Lunn
2011-05-15 11:32 ` [PATCHv2 01/15] [Orion] Rename some constants to macros to make code more identical Andrew Lunn
2011-05-15 11:32 ` [PATCHv2 02/15] [orion] Consolidate the creation of the uart platform data Andrew Lunn
2011-05-15 11:32 ` [PATCHv2 03/15] [orion] Consolidate the creation of the RTC " Andrew Lunn
2011-05-15 11:32 ` Andrew Lunn [this message]
2011-05-15 11:32 ` [PATCHv2 05/15] [orion] Consolidate ethernet " Andrew Lunn
2011-05-15 11:32 ` [PATCHv2 06/15] [orion] Consolidate I2C initialization Andrew Lunn
2011-05-15 11:32 ` [PATCHv2 07/15] [orion] Consolidate SPI initialization Andrew Lunn
2011-05-15 11:32 ` [PATCHv2 08/15] [orion] Consolidate the platform data setup for the watchdog Andrew Lunn
2011-05-15 11:32 ` [PATCHv2 09/15] [orion] Consolidate the XOR platform setup code Andrew Lunn
2011-05-15 11:32 ` [PATCHv2 10/15] [orion] Consolidate USB " Andrew Lunn
2011-05-15 11:32 ` [PATCHv2 11/15] [orion] Consolidate SATA platform setup Andrew Lunn
2011-05-15 11:32 ` [PATCHv2 12/15] [orion] Consolidate setup of the crypto engine Andrew Lunn
2011-05-15 11:32 ` [PATCHv2 13/15] [orion] Refactor the MPP code. Common code in the orion platform Andrew Lunn
2011-05-15 11:32 ` [PATCHv2 14/15] [orion5x] Refactor mpp code to use common orion platform mpp Andrew Lunn
2011-05-15 11:32 ` [PATCHv2 15/15] [dove] Consolidate mpp code with " Andrew Lunn
2011-05-16 20:31 ` [PATCHv2 00/15] Consolidate Orion platform information setup Nicolas Pitre

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=1305459174-25517-5-git-send-email-andrew@lunn.ch \
    --to=andrew@lunn.ch \
    --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).