From: "ivan.khoronzhuk" <ivan.khoronzhuk@ti.com>
To: Santosh Shilimkar <santosh.shilimkar@ti.com>, <wim@iguana.be>,
<nsekhar@ti.com>, <linux-watchdog@vger.kernel.org>,
<devicetree@vger.kernel.org>
Cc: <grant.likely@linaro.org>, <rob.herring@calxeda.com>,
<pawel.moll@arm.com>, <mark.rutland@arm.com>,
<swarren@wwwdotorg.org>, <galak@kernel.crashing.org>,
<ijc+devicetree@hellion.org.uk>, <linux-kernel@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>
Subject: Fwd: [PATCH 0/8] Update Davinci watchdog driver
Date: Wed, 6 Nov 2013 13:30:18 +0200 [thread overview]
Message-ID: <527A284A.8000901@ti.com> (raw)
In-Reply-To: <1383680783-12114-1-git-send-email-ivan.khoronzhuk@ti.com>
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 and GET_STATUS options.
- added "clocks" and "timeout-sec" properties to DT.
Based on
git://git.kernel.org/pub/scm/linux/kernel/git/ssantosh/linux-keystone.git
keystone/master
TO:
Santosh Shilimkar <santosh.shilimkar@ti.com> (maintainer: TI KEYSTONE MACHIN...)
Wim Van Sebroeck <wim@iguana.be> (maintainer:WATCHDOG DEVICE D...)
Sekhar Nori <nsekhar@ti.com> (supporter:TI DAVINCI MACHIN...)
linux-watchdog@vger.kernel.org (open list:WATCHDOG DEVICE D...)
devicetree@vger.kernel.org (open list:OPEN FIRMWARE AND...)
CC:
Grant Likely <grant.likely@linaro.org> (maintainer:OPEN FIRMWARE AND...)
Rob Herring <rob.herring@calxeda.com> (maintainer:OPEN FIRMWARE AND...)
Pawel Moll <pawel.moll@arm.com> (maintainer:OPEN FIRMWARE AND...)
Mark Rutland <mark.rutland@arm.com> (maintainer:OPEN FIRMWARE AND...)
Stephen Warren <swarren@wwwdotorg.org> (maintainer:OPEN FIRMWARE AND...)
Kumar Gala <galak@kernel.crashing.org>
Ian Campbell <ijc+devicetree@hellion.org.uk> (maintainer:OPEN FIRMWARE AND...)
linux-kernel@vger.kernel.org (open list)
linux-arm-kernel@lists.infradead.org (moderated list:ARM SUB-ARCHITECT...)
Ivan Khoronzhuk (8):
watchdog: davinci: change driver to use WDT core
watchdog: davinci: use davinci_wdt_device structure to hold device
data
watchdog: davinci: add GET_TIMELEFT option support
watchdog: davinci: add GET_STATUS option support
watchdog: davinci: add "timeout-sec" property
watchdog: davinci: reuse driver for keystone arch
watchdog: davinci: add "clocks" property
arm: dts: keystone: add watchdog entry
.../devicetree/bindings/watchdog/davinci-wdt.txt | 21 +-
arch/arm/boot/dts/keystone.dts | 6 +
drivers/watchdog/Kconfig | 5 +-
drivers/watchdog/davinci_wdt.c | 234 ++++++++++----------
4 files changed, 139 insertions(+), 127 deletions(-)
--
1.7.9.5
parent reply other threads:[~2013-11-06 11:31 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <1383680783-12114-1-git-send-email-ivan.khoronzhuk@ti.com>]
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=527A284A.8000901@ti.com \
--to=ivan.khoronzhuk@ti.com \
--cc=devicetree@vger.kernel.org \
--cc=galak@kernel.crashing.org \
--cc=grant.likely@linaro.org \
--cc=ijc+devicetree@hellion.org.uk \
--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=pawel.moll@arm.com \
--cc=rob.herring@calxeda.com \
--cc=santosh.shilimkar@ti.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