From: Alexander Holler <holler@ahsoftware.de>
To: linux-arm-kernel@lists.infradead.org
Cc: linux-omap@vger.kernel.org, Alexander Holler <holler@ahsoftware.de>
Subject: [PATCH] arm: omap3: beagle: Ensure msecure is mux'd to be able to set the RTC
Date: Tue, 5 Apr 2011 15:40:08 +0200 [thread overview]
Message-ID: <1302010808-3065-1-git-send-email-holler@ahsoftware.de> (raw)
In-Reply-To: <4D9AEB76.2060509@ahsoftware.de>
Without msecure beeing high it isn't possible to set (or start)
the RTC.
Tested with a BeagleBoard C4.
Signed-off-by: Alexander Holler <holler@ahsoftware.de>
---
arch/arm/mach-omap2/board-omap3beagle.c | 3 +++
1 files changed, 3 insertions(+), 0 deletions(-)
diff --git a/arch/arm/mach-omap2/board-omap3beagle.c b/arch/arm/mach-omap2/board-omap3beagle.c
index 46d814a..ebe3a7e 100644
--- a/arch/arm/mach-omap2/board-omap3beagle.c
+++ b/arch/arm/mach-omap2/board-omap3beagle.c
@@ -628,6 +628,9 @@ static void __init omap3_beagle_init(void)
usb_ehci_init(&ehci_pdata);
omap3beagle_flash_init();
+ /* Ensure msecure is mux'd to be able to set the RTC. */
+ omap_mux_init_signal("sys_drm_msecure", OMAP_PIN_OFF_OUTPUT_HIGH);
+
/* Ensure SDRC pins are mux'd for self-refresh */
omap_mux_init_signal("sdrc_cke0", OMAP_PIN_OUTPUT);
omap_mux_init_signal("sdrc_cke1", OMAP_PIN_OUTPUT);
--
1.7.3.4
next prev parent reply other threads:[~2011-04-05 13:41 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-04 14:29 rtc-twl: catch22 in 2.6.37 and 2.6.38 when clock was never set Alexander Holler
2011-04-05 10:14 ` Alexander Holler
2011-04-05 13:40 ` Alexander Holler [this message]
2011-05-31 10:29 ` [PATCH] arm: omap3: beagle: Ensure msecure is mux'd to be able to set the RTC Tony Lindgren
2011-06-07 8:01 ` Alexander Holler
2011-06-07 9:50 ` Igor Grinberg
2011-06-07 11:15 ` Alexander Holler
2011-06-08 21:57 ` Igor Grinberg
2011-06-09 0:21 ` Alexander Holler
2011-06-09 7:40 ` Igor Grinberg
2011-06-09 9:23 ` Alexander Holler
2011-05-31 10:28 ` rtc-twl: catch22 in 2.6.37 and 2.6.38 when clock was never set Tony Lindgren
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=1302010808-3065-1-git-send-email-holler@ahsoftware.de \
--to=holler@ahsoftware.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@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;
as well as URLs for NNTP newsgroup(s).