From: Santosh Shilimkar <santosh.shilimkar@ti.com>
To: Grygorii Strashko <grygorii.strashko@ti.com>, <wim@iguana.be>,
<nsekhar@ti.com>
Cc: Ivan Khoronzhuk <ivan.khoronzhuk@ti.com>,
<linux-arm-kernel@lists.infradead.org>, <mark.rutland@arm.com>,
<linux-watchdog@vger.kernel.org>, <devicetree@vger.kernel.org>,
<Pawel.Moll@arm.com>, <swarren@wwwdotorg.org>,
<ijc+devicetree@hellion.org.uk>, <galak@kernel.crashing.org>,
<rob.herring@calxeda.com>, <linux-kernel@vger.kernel.org>,
<grant.likely@linaro.org>
Subject: Re: [PATCH v4 0/5] Update Davinci watchdog driver
Date: Fri, 29 Nov 2013 09:57:29 -0500 [thread overview]
Message-ID: <5298AB59.7020506@ti.com> (raw)
In-Reply-To: <5298943D.8010608@ti.com>
On Friday 29 November 2013 08:18 AM, Grygorii Strashko wrote:
> Hi Sekhar,
>
> On 11/27/2013 02:48 PM, Ivan Khoronzhuk wrote:
>> These patches are intended to update Davinci watchdog to use WDT core
>> and reuse driver for keystone arch, because Keystone uses the similar
>> IP like Davinci.
>>
>> See Documentation:
>> Davinci DM646x - http://www.ti.com/lit/ug/spruer5b/spruer5b.pdf
>> Keystone - http://www.ti.com/lit/ug/sprugv5a/sprugv5a.pdf
>>
>> Also:
>> - improved to support GET_TIMELEFT option.
>> - added "clocks" and "timeout-sec" properties to DT.
>
> Do you have any additional comments to this series?
>
> By the way patch "[PATCH] watchdog: davinci: rename platform driver to davinci-wdt"
> https://lkml.org/lkml/2013/11/27/201 can be applied as before as after this series
> without conflicts.
>
Thats good then and probably the series can go via watchdog tree.
In either way, it will be good to know who is queuing up the series for 3.14
Regards,
Santosh
next prev parent reply other threads:[~2013-11-29 14:58 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-27 12:48 [PATCH v4 0/5] Update Davinci watchdog driver Ivan Khoronzhuk
2013-11-27 12:48 ` [PATCH v4 1/5] watchdog: davinci: change driver to use WDT core Ivan Khoronzhuk
2013-12-04 18:04 ` Sekhar Nori
2013-12-04 18:28 ` Guenter Roeck
2013-12-04 18:42 ` ivan.khoronzhuk
2013-12-04 18:58 ` Guenter Roeck
2013-12-04 19:06 ` ivan.khoronzhuk
2013-11-27 12:48 ` [PATCH v4 2/5] watchdog: davinci: use davinci_wdt_device structure to hold device data Ivan Khoronzhuk
2013-11-27 12:48 ` [PATCH v4 3/5] watchdog: davinci: add GET_TIMELEFT option support Ivan Khoronzhuk
2013-11-27 12:48 ` [PATCH v4 4/5] watchdog: davinci: add "timeout-sec" property Ivan Khoronzhuk
2013-11-27 12:48 ` [PATCH v4 5/5] watchdog: davinci: reuse driver for keystone arch Ivan Khoronzhuk
2013-11-29 13:18 ` [PATCH v4 0/5] Update Davinci watchdog driver Grygorii Strashko
2013-11-29 14:57 ` Santosh Shilimkar [this message]
2013-12-04 18:10 ` Sekhar Nori
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=5298AB59.7020506@ti.com \
--to=santosh.shilimkar@ti.com \
--cc=Pawel.Moll@arm.com \
--cc=devicetree@vger.kernel.org \
--cc=galak@kernel.crashing.org \
--cc=grant.likely@linaro.org \
--cc=grygorii.strashko@ti.com \
--cc=ijc+devicetree@hellion.org.uk \
--cc=ivan.khoronzhuk@ti.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-watchdog@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=nsekhar@ti.com \
--cc=rob.herring@calxeda.com \
--cc=swarren@wwwdotorg.org \
--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).