From: Lokesh Vutla <lokeshvutla@ti.com>
To: paul@pwsan.com, linux-omap@vger.kernel.org
Cc: t-kristo@ti.com, lokeshvutla@ti.com, nsekhar@ti.com,
linux-arm-kernel@lists.infradead.org
Subject: [PATCH v3 3/3] ARM: AMx3xx: RTC: Add lock and unlock functions
Date: Thu, 23 Jul 2015 18:55:46 +0530 [thread overview]
Message-ID: <1437657946-10733-4-git-send-email-lokeshvutla@ti.com> (raw)
In-Reply-To: <1437657946-10733-1-git-send-email-lokeshvutla@ti.com>
Hook omap_hwmod_rtc_unlock/lock functions into RTC hwmod,
so that SYSCONFIG register is updated properly.
Signed-off-by: Lokesh Vutla <lokeshvutla@ti.com>
---
arch/arm/mach-omap2/omap_hwmod_33xx_43xx_ipblock_data.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/arch/arm/mach-omap2/omap_hwmod_33xx_43xx_ipblock_data.c b/arch/arm/mach-omap2/omap_hwmod_33xx_43xx_ipblock_data.c
index 907a452b..aed3362 100644
--- a/arch/arm/mach-omap2/omap_hwmod_33xx_43xx_ipblock_data.c
+++ b/arch/arm/mach-omap2/omap_hwmod_33xx_43xx_ipblock_data.c
@@ -918,6 +918,8 @@ static struct omap_hwmod_class_sysconfig am33xx_rtc_sysc = {
static struct omap_hwmod_class am33xx_rtc_hwmod_class = {
.name = "rtc",
.sysc = &am33xx_rtc_sysc,
+ .unlock = &omap_hwmod_rtc_unlock,
+ .lock = &omap_hwmod_rtc_lock,
};
struct omap_hwmod am33xx_rtc_hwmod = {
--
2.1.4
next prev parent reply other threads:[~2015-07-23 13:25 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-23 13:25 [PATCH v3 0/3] ARM: OMAP2+: hwmod: RTC: Add lock and unlock hooks Lokesh Vutla
2015-07-23 13:25 ` [PATCH v3 1/3] ARM: hwmod: RTC: Add lock and unlock functions Lokesh Vutla
2015-07-23 13:25 ` [PATCH v3 2/3] ARM: DRA7: " Lokesh Vutla
2015-07-23 13:25 ` Lokesh Vutla [this message]
2015-08-27 4:21 ` [PATCH v3 0/3] ARM: OMAP2+: hwmod: RTC: Add lock and unlock hooks Lokesh Vutla
2015-09-24 4:45 ` Lokesh Vutla
2015-09-28 16:35 ` Paul Walmsley
2015-09-29 3:53 ` Lokesh Vutla
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=1437657946-10733-4-git-send-email-lokeshvutla@ti.com \
--to=lokeshvutla@ti.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=nsekhar@ti.com \
--cc=paul@pwsan.com \
--cc=t-kristo@ti.com \
/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