[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <77b2cb61-2a31-39aa-69fe-a323a5e91b8d@linaro.org>
Date: Thu, 20 Oct 2022 08:04:13 -0400
From: Krzysztof Kozlowski <krzysztof.kozlowski@...aro.org>
To: Andrej Picej <andrej.picej@...ik.com>,
linux-watchdog@...r.kernel.org
Cc: shawnguo@...nel.org, linux@...ck-us.net,
linux-kernel@...r.kernel.org, linux-arm-kernel@...ts.infradead.org,
devicetree@...r.kernel.org, linux-imx@....com, festevam@...il.com,
kernel@...gutronix.de, s.hauer@...gutronix.de,
wim@...ux-watchdog.org, robh+dt@...nel.org
Subject: Re: [PATCH 0/3] Suspending i.MX watchdog in WAIT mode
On 20/10/2022 01:49, Andrej Picej wrote:
> Hi Krzysztof,
>
> On 19. 10. 22 17:46, Krzysztof Kozlowski wrote:
>> On 19/10/2022 07:17, Andrej Picej wrote:
>>> The i.MX6 watchdog can't be stopped once started. This means that
>>> special hardware suspend needs to be configured when the device enters
>>> low-power modes.
>>> Usually i.MX devices have two bits which deal with this:
>>> - WDZST bit disables the timer in "deeper" low power modes and
>>> - WDW bit disables the timer in "WAIT" mode which corresponds with
>>> Linux's "freeze" low-power mode.
>>>
>>> WDZST bit support is already in place since 1a9c5efa576e ("watchdog: imx2_wdt: disable watchdog timer during low power mode").
>>> WDW bit is not common for all imx2-wdt supported devices, therefore use
>>> a new device-tree property "fsl,suspend-in-wait" which suspends the
>>> watchdog in "WAIT" mode.
>>>
>>> Andrej Picej (3):
>>> watchdog: imx2_wdg: suspend watchdog in WAIT mode
>>> dt-bindings: watchdog: fsl-imx: document suspend in wait mode
>>> ARM: dts: imx6ul/ull: suspend i.MX6UL watchdog in wait mode
>>>
>>> .../devicetree/bindings/watchdog/fsl-imx-wdt.yaml | 5 +++++
>>
>> Please use scripts/get_maintainers.pl to get a list of necessary people
>> and lists to CC. It might happen, that command when run on an older
>> kernel, gives you outdated entries. Therefore please be sure you base
>> your patches on recent Linux kernel.
>
> I thought I did. I run that script on linux-watchdog.git, master branch.
> I thought I should base my patches meant for watchdog subsystem there?
Maintainer's tree should be fine, but then the issue is somewhere else,
because your CC list was not complete.
Best regards,
Krzysztof
Powered by blists - more mailing lists