[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <962762c7-6baf-4116-d9d3-32b5ebe6b3c9@linux.vnet.ibm.com>
Date: Mon, 26 Jun 2017 21:16:22 -0500
From: Christopher Bostic <cbostic@...ux.vnet.ibm.com>
To: Guenter Roeck <linux@...ck-us.net>
Cc: wim@...ana.be, joel@....id.au, linux-kernel@...r.kernel.org,
linux-watchdog@...r.kernel.org, andrew@...id.au
Subject: Re: [1/2] drivers/watchdog: Document new aspeed optional dev tree
properties.
On 6/24/17 5:07 PM, Guenter Roeck wrote:
> On Tue, Jun 13, 2017 at 03:38:17PM -0500, Christopher Bostic 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@...ux.vnet.ibm.com>
> This requires DT maintainer approval, but DT maintainers were not copied.
> Please resend and use scripts/get_maintainer.pl to determine who to send
> it to.
>
> Guenter
Hi Guenter,
Will resend with maintainers copied.
Thanks
-Chris
>> ---
>> 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.
>> +
>> Example:
>>
>> wdt1: watchdog@...85000 {
>> compatible = "aspeed,ast2400-wdt";
>> reg = <0x1e785000 0x1c>;
>> + external-signal;
>> + no-system-reset;
>> };
Powered by blists - more mailing lists