From: Kevin Hilman <khilman@deeprootsystems.com>
To: Tony Lindgren <tony@atomide.com>
Cc: "Varadarajan, Charulatha" <charu@ti.com>,
wim@iguana.be, linux-watchdog@vger.kernel.org, paul@pwsan.com,
b-cousson@ti.com, rnayak@ti.com, p-basak2@ti.com,
linux-omap@vger.kernel.org
Subject: Re: [PATCH v6 0/7] OMAP: WDT: Implement WDT in hwmod way
Date: Fri, 17 Sep 2010 15:34:36 -0700 [thread overview]
Message-ID: <87mxrguhhf.fsf@deeprootsystems.com> (raw)
In-Reply-To: <20100917172215.GE29610@atomide.com> (Tony Lindgren's message of "Fri, 17 Sep 2010 10:22:15 -0700")
Tony Lindgren <tony@atomide.com> writes:
> * Varadarajan, Charulatha <charu@ti.com> [100917 07:11]:
>> Series of patches to port watchdog module to use hwmod APIs
>> for OMAP2PLUS chips and use runtime APIs for all OMAP chips.
>> For this hwmod database for OMAP2PLUS watchdog instances are
>> populated. This patch series also implements watchdog
>> module to use PM runtime APIs.
>>
>> This patch series is created on "origin/pm-core" and is
>> tested on OMAP2430, OMAP44430, OMAP3430 SDP boards and zoom3 board.
>> Also verified that this patch series does not break the OMAP1 build.
>>
>> This series is tested on OMAP4430 ES2 using the below series
>> http://www.spinics.net/lists/linux-omap/msg36023.html
>
> Can you please list the exact dependencies to other patches
> for the mainline kernel? Are they the same as for the
> omap serial driver just posted?
Hi Tony,
This series is based on my pm-core branch which is basically the the
stuff I have submitted upstream (my pm-next series, the runtime PM core)
and a collection of hwmod fixes that Paul/Benoit have lined up
for 2.6.37.
I will gladly queue these hwmod conversion patches in my tree if you
prefer since I am already managing all the dependencies.
Kevin
next prev parent reply other threads:[~2010-09-17 22:34 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-17 14:18 [PATCH v6 0/7] OMAP: WDT: Implement WDT in hwmod way Varadarajan, Charulatha
2010-09-17 14:18 ` [PATCH v6 1/7] OMAP2PLUS: WDT: Add ICLKEN, FCLKEN, WKEN shared bits for WDT Varadarajan, Charulatha
2010-09-17 14:18 ` [PATCH v6 2/7] OMAP3: hwmod data: Add watchdog timer Varadarajan, Charulatha
2010-09-17 14:18 ` [PATCH v6 3/7] OMAP2420: " Varadarajan, Charulatha
2010-09-17 14:18 ` [PATCH v6 4/7] OMAP2430: " Varadarajan, Charulatha
2010-09-17 14:18 ` [PATCH v6 5/7] OMAP4: " Varadarajan, Charulatha
2010-09-17 14:18 ` [PATCH v6 6/7] OMAP2PLUS: WDT: use omap_device_build for device registration Varadarajan, Charulatha
2010-09-17 14:18 ` [PATCH v6 7/7] OMAP: WDT: Use PM runtime APIs instead of clk FW APIs Varadarajan, Charulatha
2010-09-17 17:22 ` [PATCH v6 0/7] OMAP: WDT: Implement WDT in hwmod way Tony Lindgren
2010-09-17 22:34 ` Kevin Hilman [this message]
2010-09-20 17:16 ` Tony Lindgren
2010-09-20 20:48 ` Kevin Hilman
2010-09-20 20:56 ` Tony Lindgren
2010-09-22 0:35 ` Paul Walmsley
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=87mxrguhhf.fsf@deeprootsystems.com \
--to=khilman@deeprootsystems.com \
--cc=b-cousson@ti.com \
--cc=charu@ti.com \
--cc=linux-omap@vger.kernel.org \
--cc=linux-watchdog@vger.kernel.org \
--cc=p-basak2@ti.com \
--cc=paul@pwsan.com \
--cc=rnayak@ti.com \
--cc=tony@atomide.com \
--cc=wim@iguana.be \
/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).