[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <9ef37bd7-0bb5-d9ee-6643-47aac9870a67@roeck-us.net>
Date: Tue, 21 Dec 2021 07:06:37 -0800
From: Guenter Roeck <linux@...ck-us.net>
To: Luca Ceresoli <luca@...aceresoli.net>, linux-kernel@...r.kernel.org
Cc: linux-rtc@...r.kernel.org, linux-watchdog@...r.kernel.org,
devicetree@...r.kernel.org, Lee Jones <lee.jones@...aro.org>,
Rob Herring <robh+dt@...nel.org>,
Chanwoo Choi <cw00.choi@...sung.com>,
Krzysztof Kozlowski <krzysztof.kozlowski@...onical.com>,
Alessandro Zummo <a.zummo@...ertech.it>,
Alexandre Belloni <alexandre.belloni@...tlin.com>,
Wim Van Sebroeck <wim@...ux-watchdog.org>,
Chiwoong Byun <woong.byun@...sung.com>,
Laxman Dewangan <ldewangan@...dia.com>,
Randy Dunlap <rdunlap@...radead.org>
Subject: Re: [PATCH v5 8/9] watchdog: max77620: add comment to clarify
set_timeout procedure
On 12/11/21 12:34 PM, Luca Ceresoli wrote:
> Clarify why we need to ping the watchdog before changing the timeout by
> quoting the MAX77714 datasheet.
>
> Signed-off-by: Luca Ceresoli <luca@...aceresoli.net>
>
Reviewed-by: Guenter Roeck <linux@...ck-us.net>
Powered by blists - more mailing lists