linux-watchdog.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Christopher Bostic <cbostic@linux.vnet.ibm.com>
To: Joel Stanley <joel@jms.id.au>
Cc: Wim Van Sebroeck <wim@iguana.be>,
	Guenter Roeck <linux@roeck-us.net>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	linux-watchdog@vger.kernel.org, Andrew Jeffery <andrew@aj.id.au>
Subject: Re: [PATCH 1/2] drivers/watchdog: Document new aspeed optional dev tree properties.
Date: Tue, 27 Jun 2017 14:44:18 -0500	[thread overview]
Message-ID: <fdbaf3ce-061b-d639-89ac-fed221d60f45@linux.vnet.ibm.com> (raw)
In-Reply-To: <CACPK8Xe4kWoZKhwRWD+p-zFz-EQDn_3Q5=U4tUX-n6paKMYy1A@mail.gmail.com>



On 6/26/17 9:59 PM, Joel Stanley wrote:
> On Wed, Jun 14, 2017 at 6:08 AM, Christopher Bostic
> <cbostic@linux.vnet.ibm.com> wrote:
>> Describe new optional property 'external-signal'.  When present in the
>> system device tree an exernal signal is generated on watchdog timeout.
>>
>> Describe new optional property 'no-system-reset'.  When present in the
>> system device tree no system reset is to occur on watchdog timeout.
>> System reset in this case is managed by one of the other watchogs
>> available.
>>
>> Signed-off-by: Christopher Bostic <cbostic@linux.vnet.ibm.com>
>> ---
>>   Documentation/devicetree/bindings/watchdog/aspeed-wdt.txt | 11 +++++++++++
>>   1 file changed, 11 insertions(+)
>>
>> diff --git a/Documentation/devicetree/bindings/watchdog/aspeed-wdt.txt b/Documentation/devicetree/bindings/watchdog/aspeed-wdt.txt
>> index c5e74d7..4099ea5 100644
>> --- a/Documentation/devicetree/bindings/watchdog/aspeed-wdt.txt
>> +++ b/Documentation/devicetree/bindings/watchdog/aspeed-wdt.txt
>> @@ -8,9 +8,20 @@ Required properties:
>>    - reg: physical base address of the controller and length of memory mapped
>>      region
>>
>> +Optional properties:
>> + - external-signal: If the property is present then an external signal is to
>> +   be generated on watchdog timeout.  If absent, external signal is not
>> +   generated.
>> +
>> + - no-system-reset: If the property is present then system will not be reset
>> +   on watchdog timeout. In this case one of the other watchdogs will handle
>> +   reset.  If absent then the watchdog resets the system on timeout.
> I'm not sure that this describes the hardware. The datasheet says:
>
> Whenever timeout ocurs, WDT can program to generate 6 types of signals:
>
>   * ARM reset signal: to reset ARM CPU only
>   * SOC reset signal: to reset SOC part function
>   * System reset signal: to reset full chip
>   * Interrupt signal: to interrupt CPU
>   * Eternal signal: to external reset counter (only WDT1 and WDT2)
>   * Alternate boot signal: to boot from alternate block
>
> I think your bindings should describe these modes where possible.

I'll add the modes you describe.

Thanks,
Chris
>
> Cheers,
>
> Joel
>
>
>> +
>>   Example:
>>
>>          wdt1: watchdog@1e785000 {
>>                  compatible = "aspeed,ast2400-wdt";
>>                  reg = <0x1e785000 0x1c>;
>> +               external-signal;
>> +               no-system-reset;
>>          };
>> --
>> 1.8.2.2
>>

  reply	other threads:[~2017-06-27 19:44 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-13 20:38 [PATCH 0/2] drivers/watchdog ASPEED: Add optional dev tree configs Christopher Bostic
2017-06-13 20:38 ` [PATCH 1/2] drivers/watchdog: Document new aspeed optional dev tree properties Christopher Bostic
2017-06-24 22:07   ` [1/2] " Guenter Roeck
2017-06-27  2:16     ` Christopher Bostic
2017-06-27  2:59   ` [PATCH 1/2] " Joel Stanley
2017-06-27 19:44     ` Christopher Bostic [this message]
2017-06-13 20:38 ` [PATCH 2/2] drivers/watchdog: ASPEED reference dev tree properties for config Christopher Bostic
2017-06-24 22:17   ` [2/2] " Guenter Roeck
2017-06-27  2:17     ` Christopher Bostic

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=fdbaf3ce-061b-d639-89ac-fed221d60f45@linux.vnet.ibm.com \
    --to=cbostic@linux.vnet.ibm.com \
    --cc=andrew@aj.id.au \
    --cc=joel@jms.id.au \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-watchdog@vger.kernel.org \
    --cc=linux@roeck-us.net \
    --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).