From: a0131933@ti.com (Lokesh Vutla)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v3 0/3] ARM: OMAP2+: hwmod: RTC: Add lock and unlock hooks
Date: Thu, 24 Sep 2015 10:15:30 +0530 [thread overview]
Message-ID: <56037FEA.5070807@ti.com> (raw)
In-Reply-To: <55DE9055.4090701@ti.com>
Hi Paul,
On Thursday 27 August 2015 09:51 AM, Lokesh Vutla wrote:
> Hi Paul,
>
> On Thursday 23 July 2015 06:55 PM, Lokesh Vutla wrote:
>> This series implements lock and unlock functions for RTC and hooks
>> the same to DRA7 and AMx3xx hwmod.
>> This is dependent on the patch https://patchwork.kernel.org/patch/6578281/,
>> which is queued recently by Paul.
> Gentle ping on this series.
Do you have any comments on this series?
Thanks and regards,
Lokesh
>
> Thanks and regards,
> Lokesh
>>
>> Changes since v2:
>> - Add kerneldoc for omap_hwmod_rtc_lock() function.
>>
>> 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(+)
>>
next prev parent reply other threads:[~2015-09-24 4:45 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 ` [PATCH v3 3/3] ARM: AMx3xx: " Lokesh Vutla
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 [this message]
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=56037FEA.5070807@ti.com \
--to=a0131933@ti.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).