From: Nandor Han <nandor.han@gehealthcare.com>
To: Krzysztof Kozlowski <krzk@kernel.org>
Cc: wim@linux-watchdog.org, linux@roeck-us.net, robh@kernel.org,
krzk+dt@kernel.org, conor+dt@kernel.org, shawnguo@kernel.org,
s.hauer@pengutronix.de, kernel@pengutronix.de,
festevam@gmail.com, linux-watchdog@vger.kernel.org,
devicetree@vger.kernel.org, imx@lists.linux.dev,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] watchdog: imx2_wdt: Allow to continue in low power mode
Date: Wed, 7 Jan 2026 11:04:40 +0200 [thread overview]
Message-ID: <0c3ebcfe-dc45-4e52-a86e-cc776b3bcae2@gehealthcare.com> (raw)
In-Reply-To: <20251230-pastoral-enigmatic-chamois-b65343@quoll>
On 12/30/25 14:35, Krzysztof Kozlowski wrote:
> CAUTION: This email originated from outside of GE HealthCare. Only open links or attachments if you trust the sender. Report suspicious emails using Outlook’s “Report” button.
>
> On Mon, Dec 29, 2025 at 04:49:59PM +0200, Nandor Han wrote:
>> By default, the driver suspends the watchdog in low power modes (STOP
>> and DOZE). In some situations this is not desired.
>>
>> Add the possibility to configure the continuation of the watchdog timer
>> in the above mentioned low power modes.
>>
>> Note:
>> Please be advised that the difference between the variable name and the
>> device tree option has been intentionally selected to uphold the
>> prevailing driver functionality. This ensures that the watchdog remains
>> suspended by default in low power mode, while also facilitating a clear
>> and intelligible device tree option name.
>>
> Please organize the patch documenting the compatible (DT bindings)
> before the patch using that compatible.
> See also: https://elixir.bootlin.com/linux/v6.14-rc6/source/Documentation/devicetree/bindings/submitting-patches.rst#L46
>
> Best regards,
> Krzysztof
Thanks Krzysztof for the suggestion, I will take a look over the doc.
Regards,
Nandor
next prev parent reply other threads:[~2026-01-07 9:05 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-29 14:49 [PATCH 0/2] watchdog: imx2_wdt: Allow to run " Nandor Han
2025-12-29 14:49 ` [PATCH 1/2] watchdog: imx2_wdt: Allow to continue " Nandor Han
2025-12-30 12:35 ` Krzysztof Kozlowski
2026-01-07 9:04 ` Nandor Han [this message]
2026-01-12 13:08 ` [PATCH v2 0/2] watchdog: imx2_wdt: Allow to run " Nandor Han
2026-01-12 13:08 ` [PATCH v2 1/2] dt-bindings: watchdog: fsl-imx: document continue " Nandor Han
2026-01-12 13:55 ` Krzysztof Kozlowski
2026-01-14 13:22 ` Nandor Han
2026-01-14 15:58 ` Krzysztof Kozlowski
2026-01-12 13:08 ` [PATCH v2 2/2] watchdog: imx2_wdt: Allow to " Nandor Han
2025-12-31 23:41 ` [PATCH 1/2] " Guenter Roeck
2025-12-29 14:50 ` [PATCH 2/2] dt-bindings: watchdog: fsl-imx: document " Nandor Han
2025-12-30 12:34 ` Krzysztof Kozlowski
2026-01-07 9:12 ` Nandor Han
2026-01-07 10:48 ` Krzysztof Kozlowski
2026-01-08 7:58 ` Nandor Han
2026-01-12 13:56 ` Krzysztof Kozlowski
2026-01-06 11:51 ` Peng Fan
2026-01-07 10:29 ` Nandor Han
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=0c3ebcfe-dc45-4e52-a86e-cc776b3bcae2@gehealthcare.com \
--to=nandor.han@gehealthcare.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=festevam@gmail.com \
--cc=imx@lists.linux.dev \
--cc=kernel@pengutronix.de \
--cc=krzk+dt@kernel.org \
--cc=krzk@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-watchdog@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=robh@kernel.org \
--cc=s.hauer@pengutronix.de \
--cc=shawnguo@kernel.org \
--cc=wim@linux-watchdog.org \
/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
all inboxes | Powered by JetHome®