devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>
To: Ivan Khoronzhuk <ivan.khoronzhuk@ti.com>,
	dbaryshkov@gmail.com, dwmw2@infradead.org, lee.jones@linaro.org,
	santosh.shilimkar@ti.com, 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
Subject: Re: [Patch v6 4/7] power: reset: add bindings for keystone reset driver
Date: Thu, 22 May 2014 22:03:09 +0400	[thread overview]
Message-ID: <537E3BDD.40106@cogentembedded.com> (raw)
In-Reply-To: <1400777062-19276-5-git-send-email-ivan.khoronzhuk@ti.com>

Hello.

On 05/22/2014 08:44 PM, Ivan Khoronzhuk wrote:

> This node is intended to allow SoC reset in case of software reset
> or appropriate watchdogs.

> The Keystone SoCs can contain up to 4 watchdog timers to reset
> SoC. Each watchdog timer event input is connected to the Reset Mux
> block. The Reset Mux block can be configured to cause reset or not.

> Additionally soft or hard reset can be configured.

> Reviewed-by: Arnd Bergmann <arnd@arndb.de>
> Signed-off-by: Ivan Khoronzhuk <ivan.khoronzhuk@ti.com>
> ---
>   .../bindings/power/reset/keystone-reset.txt        | 67 ++++++++++++++++++++++
>   1 file changed, 67 insertions(+)
>   create mode 100644 Documentation/devicetree/bindings/power/reset/keystone-reset.txt

> diff --git a/Documentation/devicetree/bindings/power/reset/keystone-reset.txt b/Documentation/devicetree/bindings/power/reset/keystone-reset.txt
> new file mode 100644
> index 0000000..a8a0c31
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/power/reset/keystone-reset.txt
> @@ -0,0 +1,67 @@
> +* Device tree bindings for Texas Instruments keystone reset
> +
> +This node is intended to allow SoC reset in case of software reset
> +of selected watchdogs.
> +
> +The Keystone SoCs can contain up to 4 watchdog timers to reset
> +SoC. Each watchdog timer event input is connected to the Reset Mux
> +block. The Reset Mux block can be configured to cause reset or not.
> +
> +Additionally soft or hard reset can be configured.
> +
> +Required properties:
> +
> +- compatible:		ti,keystone-reset
> +
> +- ti,syscon-pll:	phandle/offset pair. The phandle to syscon used to
> +			access pll controller registers and the offset to use
> +			reset control registers.
> +
> +- ti,syscon-dev:	phandle/offset pair. The phandle to syscon used to
> +			access device state control registers and the offset
> +			in order to use mux block registers for all watchdogs.
> +
> +Optional properties:
> +
> +- ti,soft-reset:	Boolean option indicating soft reset.
> +			By default hard reset is used.
> +
> +- ti,wdt_list:		WDT list that can cause SoC reset. It's not related

    Hm, why underscore in this property while hyphens are used in the others? 
Hyphen is generally preferrable in the device tree names...

> +			to WDT driver, it's just needed to enable a SoC related
> +			reset that's triggered by one of WDTs. The list is
> +			in format: <0>, <2>; It can be in random order and
> +			begins from 0 to 3, as keystone can contain up to 4 SoC
> +			reset watchdogs and can be in random order.

WBR, Sergei


  reply	other threads:[~2014-05-22 18:03 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-22 16:44 [Patch v6 0/7] Introduce keystone reset driver Ivan Khoronzhuk
2014-05-22 16:44 ` [Patch v6 1/7] power: reset: keystone-reset: introduce " Ivan Khoronzhuk
2014-05-22 16:44 ` [Patch v6 2/7] clock: keystone-pllctrl: add bindings for keystone pll controller Ivan Khoronzhuk
2014-05-22 16:44 ` [Patch v6 3/7] mfd: ti-keystone-devctrl: add bindings for device state control Ivan Khoronzhuk
2014-05-22 17:11   ` Lee Jones
2014-05-22 17:16     ` Ivan Khoronzhuk
2014-05-22 16:44 ` [Patch v6 4/7] power: reset: add bindings for keystone reset driver Ivan Khoronzhuk
2014-05-22 18:03   ` Sergei Shtylyov [this message]
2014-05-22 18:19     ` Ivan Khoronzhuk
2014-05-22 16:44 ` [Patch v6 5/7] ARM: keystone: remove redundant reset stuff Ivan Khoronzhuk
2014-05-22 16:44 ` [Patch v6 6/7] ARM: dts: keystone: update reset node to work with reset driver Ivan Khoronzhuk
2014-05-22 16:44 ` [Patch v6 7/7] ARM: keystone: enable reset driver support Ivan Khoronzhuk

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=537E3BDD.40106@cogentembedded.com \
    --to=sergei.shtylyov@cogentembedded.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=lee.jones@linaro.org \
    --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=santosh.shilimkar@ti.com \
    --cc=sboyd@codeaurora.org \
    --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).