From: Lokesh Vutla <lokeshvutla@ti.com>
To: Tony Lindgren <tony@atomide.com>, Paul Walmsley <paul@pwsan.com>
Cc: Nishanth Menon <nm@ti.com>, Lokesh Vutla <lokeshvutla@ti.com>,
Sekhar Nori <nsekhar@ti.com>, Tero Kristo <t-kristo@ti.com>,
Linux OMAP Mailing List <linux-omap@vger.kernel.org>,
Linux ARM Mailing List <linux-arm-kernel@lists.infradead.org>
Subject: [PATCH v4 0/3] ARM: OMAP2+: hwmod: RTC: Add lock and unlock hooks
Date: Fri, 5 Feb 2016 11:12:29 +0530 [thread overview]
Message-ID: <1454650952-20154-1-git-send-email-lokeshvutla@ti.com> (raw)
This series implements lock and unlock functions for RTC and hooks
the same to DRA7 and AMx3xx hwmod.
Tested RTC functionality on:
DRA74-EVM: http://pastebin.ubuntu.com/14885542/
BeagleBoard-X15: http://pastebin.ubuntu.com/14885568/
AM437x-GP EVM: http://pastebin.ubuntu.com/14885589/
AM335x BeagleBoneBlack: http://pastebin.ubuntu.com/14885600/
Changes since v3:
- Rebased on top of latest Mainline.
Link to v3 series: https://www.mail-archive.com/linux-omap%40vger.kernel.org/msg118342.html
Lokesh Vutla (3):
ARM: hwmod: RTC: Add lock and unlock functions
ARM: DRA7: RTC: Add lock and unlock functions
ARM: AMx3xx: RTC: Add lock and unlock functions
arch/arm/mach-omap2/omap_hwmod.h | 2 +
.../mach-omap2/omap_hwmod_33xx_43xx_ipblock_data.c | 2 +
arch/arm/mach-omap2/omap_hwmod_7xx_data.c | 2 +
arch/arm/mach-omap2/omap_hwmod_reset.c | 65 ++++++++++++++++++++++
4 files changed, 71 insertions(+)
--
2.1.4
next reply other threads:[~2016-02-05 5:42 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-05 5:42 Lokesh Vutla [this message]
2016-02-05 5:42 ` [PATCH v4 1/3] ARM: hwmod: RTC: Add lock and unlock functions Lokesh Vutla
2016-02-07 22:24 ` Paul Walmsley
2016-02-18 6:27 ` Paul Walmsley
2016-02-18 9:19 ` Lokesh Vutla
2016-02-18 17:17 ` Paul Walmsley
2016-02-24 9:29 ` Lokesh Vutla
2016-02-24 18:07 ` Paul Walmsley
2016-02-05 5:42 ` [PATCH v4 2/3] ARM: DRA7: " Lokesh Vutla
2016-02-05 5:42 ` [PATCH v4 3/3] ARM: AMx3xx: " 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=1454650952-20154-1-git-send-email-lokeshvutla@ti.com \
--to=lokeshvutla@ti.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=nm@ti.com \
--cc=nsekhar@ti.com \
--cc=paul@pwsan.com \
--cc=t-kristo@ti.com \
--cc=tony@atomide.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