All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tom Rini <trini@konsulko.com>
To: Stefan Roese <sr@denx.de>
Cc: u-boot@lists.denx.de, sjg@chromium.org, rasmus.villemoes@prevas.dk
Subject: Re: [PATCH v2 0/6] Migrate watchdog reset to cyclic infrastructure
Date: Sat, 17 Sep 2022 10:08:03 -0400	[thread overview]
Message-ID: <20220917140803.GA420627@bill-the-cat> (raw)
In-Reply-To: <20220917081450.21549-1-sr@denx.de>

[-- Attachment #1: Type: text/plain, Size: 1039 bytes --]

On Sat, Sep 17, 2022 at 10:14:44AM +0200, Stefan Roese wrote:

> This patchset migrates the watchdog triggering (WATCHDOG_RESET calls)
> to the newly introduced cyclic execution framework. For this, the
> watchdog driver now registers a cyclic execution function for each
> WDT device that needs to get serviced. Additionally the cyclic IF is
> a bit extended to also support the CONFIG_HW_WATCHDOG users. It might
> make sense to deprecate this HW_WATCHDOG usage at some point.
> 
> Please note that this migration work is based on the cyclic execution
> infrastructure, which I posted in the last few weeks. So these cyclic
> patches need to be applied for this migration to work.
> 
> Some further cleanup and improvements are possible after this patch.
> E.g. Heinrich mentioned that the WATCHDOG_RESET call locations need to
> get improved / changed in some places.

For the series:
Tested-by: Tom Rini <trini@konsulko.com> [am335x_evm, mx6cuboxi, rpi_3,
dra7xx_evm, pine64_plus, am65x_evm, j721e_evm]

-- 
Tom

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 659 bytes --]

      parent reply	other threads:[~2022-09-17 14:08 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-17  8:14 [PATCH v2 0/6] Migrate watchdog reset to cyclic infrastructure Stefan Roese
2022-09-17  8:14 ` [PATCH v2 1/6] watchdog: Integrate watchdog triggering into the cyclic framework Stefan Roese
2022-09-17  8:14 ` [PATCH v2 2/6] cyclic: Introduce schedule() function Stefan Roese
2022-09-17  8:14 ` [PATCH v2 3/6] cyclic: Use schedule() instead of WATCHDOG_RESET() Stefan Roese
2022-09-17  8:14 ` [PATCH v2 4/6] watchdog: Get rid of ASSEMBLY hacks Stefan Roese
2022-09-17  8:14 ` [PATCH v2 5/6] watchdog: Remove WATCHDOG_RESET macro Stefan Roese
2022-09-17  8:14 ` [PATCH v2 6/6] watchdog: Further cleanup Stefan Roese
2022-09-17 14:08 ` Tom Rini [this message]

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=20220917140803.GA420627@bill-the-cat \
    --to=trini@konsulko.com \
    --cc=rasmus.villemoes@prevas.dk \
    --cc=sjg@chromium.org \
    --cc=sr@denx.de \
    --cc=u-boot@lists.denx.de \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.