linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Santosh Shilimkar <santosh.shilimkar@ti.com>
To: Ivan Khoronzhuk <ivan.khoronzhuk@ti.com>, <dbaryshkov@gmail.com>,
	<dwmw2@infradead.org>, <arnd@arndb.de>, <robh+dt@kernel.org>,
	<pawel.moll@arm.com>, <mark.rutland@arm.com>,
	<ijc+devicetree@hellion.org.uk>, <galak@codeaurora.org>,
	<grant.likely@linaro.org>
Cc: <rdunlap@infradead.org>, <linux@arm.linux.org.uk>,
	<grygorii.strashko@ti.com>, <olof@lixom.net>, <w-kwok2@ti.com>,
	<sboyd@codeaurora.org>, <devicetree@vger.kernel.org>,
	<linux-doc@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
	<linux-arm-kernel@lists.infradead.org>, <m-karicheri2@ti.com>,
	<sergei.shtylyov@cogentembedded.com>
Subject: Re: [Patch v5 0/7] Introduce keystone reset driver
Date: Thu, 22 May 2014 09:52:27 -0400	[thread overview]
Message-ID: <537E011B.9090902@ti.com> (raw)
In-Reply-To: <1400766516-14537-1-git-send-email-ivan.khoronzhuk@ti.com>

Ivan,

On Thursday 22 May 2014 09:48 AM, Ivan Khoronzhuk wrote:
> These patches introduce keystone reset driver.
> 
> The keystone SoC can be rebooted in several ways. By external reset
> pin, by soft and by watchdogs. This driver allows software reset and reset
> by one of the watchdogs. Also added opportunity to set soft/hard reset type.
> 
> Based on linux-next/master
> 
> v5..v4
>   power: reset: keystone-reset: introduce keystone reset driver
>   	- changed to get rsmux and rspll offsets from DT
>   clock: keystone-pllctrl: add bindings for keystone pll controller
>   	- new patch
>   mfd: ti-keystone-devctrl: add bindings for device state control
>   	- new patch
>   power: reset: add bindings for keystone reset driver
>   	- corrected description of "ti,syscon-pll", "ti,syscon-dev" properties
> 	- corrected examples
>   ARM: dts: keystone: update reset node to work with reset driver
>   	- added nodes for pll-controller and device-state-controll
> 	- added offsets to "ti,syscon-pll", "ti,syscon-dev" properties
>
Looks like you haven't collected Arnd's Reviewed-by tag on the patches.
Can be added later as well while applying.


 
> v4..v3
>   Power: reset: keystone-reset: introduce keystone reset driver
>   	- changed to use syscon framework
>   	- changed to use regmap to access registers
>   Power: reset: add bindings for keystone reset driver
>   	- deleted properties "reg", "reg-names"
> 	- added properties "ti,syscon-pll", "ti,syscon-dev"
>   ARM: dts: keystone: update reset node to work with reset driver
>   	- deleted properties "reg", "reg-names"
> 	- added properties "ti,syscon-pll", "ti,syscon-dev"
> 
> v2..v3
>   Power: reset: keystone-reset: introduce keystone reset driver
> 	- no functional changes, only sanity
>   Power: reset: add bindings for keystone reset driver
>   	- corrected WDT numeration in examples
> 	- extended description of wdt_list property
> 
> v1..v2
> 	- re based on v3.15-rc1 without changes
> 
> Ivan Khoronzhuk (7):
>   power: reset: keystone-reset: introduce keystone reset driver
>   clock: keystone-pllctrl: add bindings for keystone pll controller
>   mfd: ti-keystone-devctrl: add bindings for device state control
>   power: reset: add bindings for keystone reset driver
>   ARM: keystone: remove redundant reset stuff
>   ARM: dts: keystone: update reset node to work with reset driver
>   ARM: keystone: enable reset driver support
> 
>  .../bindings/clock/ti-keystone-pllctrl.txt         |  20 +++
>  .../bindings/mfd/ti-keystone-devctrl.txt           |  19 +++
>  .../bindings/power/reset/keystone-reset.txt        |  67 +++++++++
>  arch/arm/boot/dts/keystone.dtsi                    |  14 +-
>  arch/arm/configs/keystone_defconfig                |   3 +
>  arch/arm/mach-keystone/keystone.c                  |  34 -----
>  drivers/power/reset/Kconfig                        |   8 +
>  drivers/power/reset/Makefile                       |   1 +
>  drivers/power/reset/keystone-reset.c               | 166 +++++++++++++++++++++
>  9 files changed, 297 insertions(+), 35 deletions(-)
>  create mode 100644 Documentation/devicetree/bindings/clock/ti-keystone-pllctrl.txt
>  create mode 100644 Documentation/devicetree/bindings/mfd/ti-keystone-devctrl.txt
>  create mode 100644 Documentation/devicetree/bindings/power/reset/keystone-reset.txt
>  create mode 100644 drivers/power/reset/keystone-reset.c
> 


  parent reply	other threads:[~2014-05-22 13:53 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-22 13:48 [Patch v5 0/7] Introduce keystone reset driver Ivan Khoronzhuk
2014-05-22 13:48 ` [Patch v5 1/7] power: reset: keystone-reset: introduce " Ivan Khoronzhuk
2014-05-22 13:48 ` [Patch v5 2/7] clock: keystone-pllctrl: add bindings for keystone pll controller Ivan Khoronzhuk
2014-05-22 13:48 ` [Patch v5 3/7] mfd: ti-keystone-devctrl: add bindings for device state control Ivan Khoronzhuk
2014-05-22 14:14   ` Lee Jones
2014-05-22 14:32     ` Ivan Khoronzhuk
2014-05-22 15:33       ` Lee Jones
2014-05-22 16:14         ` Ivan Khoronzhuk
2014-05-22 16:30           ` Ivan Khoronzhuk
2014-05-22 13:48 ` [Patch v5 4/7] power: reset: add bindings for keystone reset driver Ivan Khoronzhuk
2014-05-22 13:48 ` [Patch v5 5/7] ARM: keystone: remove redundant reset stuff Ivan Khoronzhuk
2014-05-22 13:48 ` [Patch v5 6/7] ARM: dts: keystone: update reset node to work with reset driver Ivan Khoronzhuk
2014-05-22 13:48 ` [Patch v5 7/7] ARM: keystone: enable reset driver support Ivan Khoronzhuk
2014-05-22 13:52 ` Santosh Shilimkar [this message]
2014-05-22 13:54   ` [Patch v5 0/7] Introduce keystone reset driver Arnd Bergmann
2014-05-22 13:58     ` Ivan Khoronzhuk
2014-05-22 14:02     ` Santosh Shilimkar

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=537E011B.9090902@ti.com \
    --to=santosh.shilimkar@ti.com \
    --cc=arnd@arndb.de \
    --cc=dbaryshkov@gmail.com \
    --cc=devicetree@vger.kernel.org \
    --cc=dwmw2@infradead.org \
    --cc=galak@codeaurora.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-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@arm.linux.org.uk \
    --cc=m-karicheri2@ti.com \
    --cc=mark.rutland@arm.com \
    --cc=olof@lixom.net \
    --cc=pawel.moll@arm.com \
    --cc=rdunlap@infradead.org \
    --cc=robh+dt@kernel.org \
    --cc=sboyd@codeaurora.org \
    --cc=sergei.shtylyov@cogentembedded.com \
    --cc=w-kwok2@ti.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;
as well as URLs for NNTP newsgroup(s).