From: Rustam Adilov <adilov@disroot.org>
To: Wim Van Sebroeck <wim@linux-watchdog.org>,
Guenter Roeck <linux@roeck-us.net>,
Sander Vanheule <sander@svanheule.net>,
linux-watchdog@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 0/1] watchdog: realtek-otto: Make use of regmap API
Date: Fri, 10 Jul 2026 08:13:49 +0000 [thread overview]
Message-ID: <79ff8becf68dd80b8993a458ae7e3c44@disroot.org> (raw)
In-Reply-To: <20260710074316.46643-1-adilov@disroot.org>
On 2026-07-10 07:43, Rustam Adilov wrote:
> This patch series changes the driver to use regmap API for all of the
> register access stuff instead of the ioread32 and iowrite32 with __iomem.
> That makes the watchdog operable when SWAP_IO_SPACE config is enabled just
> by adding big-endian property to the device tree node.
>
> Also, there was a comment by sashiko which got addressed by Sander in [2]
> with possibility of it being false positive so i left it at that.
>
> ---
> Changelog in v3:
> - reworded the commit message to make the main reasoning clear.
> - rebased the branch.
> - Link v2: https://lore.kernel.org/linux-watchdog/20260519182329.24472-1-adilov@disroot.org/
>
> Changelog in v2:
> - removed patches 2 and 3 that add rtl9607c device.
> - included driver changes made by Sander in [1].
> - added disable_locking to regmap_config and set it to true.
> - Link to v1: https://lore.kernel.org/all/20260509163101.722793-1-adilov@disroot.org/
>
> [1] https://lore.kernel.org/all/20260515212351.752054-1-sander@svanheule.net/
> [2] https://lore.kernel.org/linux-watchdog/d0b159eefa6bc5abf0d1531acde568396f480500.camel@svanheule.net/
>
> Rustam Adilov (1):
> watchdog: realtek-otto: Change to use regmap API
>
> drivers/watchdog/Kconfig | 1 +
> drivers/watchdog/realtek_otto_wdt.c | 74 +++++++++++++++--------------
> 2 files changed, 39 insertions(+), 36 deletions(-)
Hmm, there is a real possibility that Guenter Roeck didn't receive
my patches because I've received a message "Undelivered Mail
Returned to Sender" indicating mail host roeck-us.net has rejected them.
I don't know if that's gonna be a problem but i hope not. At the very
least it is visible on linux-watchdog mailing list.
prev parent reply other threads:[~2026-07-10 8:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-10 7:43 [PATCH v3 0/1] watchdog: realtek-otto: Make use of regmap API Rustam Adilov
2026-07-10 7:43 ` [PATCH v3 1/1] watchdog: realtek-otto: Change to use " Rustam Adilov
2026-07-10 8:13 ` Rustam Adilov [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=79ff8becf68dd80b8993a458ae7e3c44@disroot.org \
--to=adilov@disroot.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-watchdog@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=sander@svanheule.net \
--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