From: Robert Lin <robelin@nvidia.com>
To: <thierry.reding@gmail.com>, <daniel.lezcano@linaro.org>,
<jonathanh@nvidia.com>, <tglx@linutronix.de>,
<pohsuns@nvidia.com>
Cc: <linux-kernel@vger.kernel.org>, <linux-tegra@vger.kernel.org>,
<sumitg@nvidia.com>, robelin <robelin@nvidia.com>
Subject: [PATCH v3 0/3] clocksource: fix Tegra234 SoC Watchdog Timer.
Date: Mon, 7 Apr 2025 18:23:20 +0800 [thread overview]
Message-ID: <20250407102323.2690911-1-robelin@nvidia.com> (raw)
From: robelin <robelin@nvidia.com>
This set of patches includes a fix for watchdog for it may not bark
due to self-pinging and adds WDIOC_GETTIMELEFT support.
--
V3:
- Improve comment description
- Refactor to fit codeline within 80 columns
- Remove unused if(0) blocks
V2:
- Fix a compilation error, a warning and updates copyright
--
Pohsun Su (2):
clocksource/drivers/timer-tegra186: add WDIOC_GETTIMELEFT support
clocksource/drivers/timer-tegra186: fix watchdog self-pinging
robelin (1):
clocksource/drivers/timer-tegra186: Remove unused bits
drivers/clocksource/timer-tegra186.c | 86 +++++++++++++++++-----------
1 file changed, 52 insertions(+), 34 deletions(-)
--
2.34.1
next reply other threads:[~2025-04-07 10:23 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-07 10:23 Robert Lin [this message]
2025-04-07 10:23 ` [PATCH v3 1/3] clocksource/drivers/timer-tegra186: add WDIOC_GETTIMELEFT support Robert Lin
2025-04-10 10:09 ` Thierry Reding
2025-04-15 2:57 ` Robert Lin
2025-04-07 10:23 ` [PATCH v3 2/3] clocksource/drivers/timer-tegra186: fix watchdog self-pinging Robert Lin
2025-04-08 8:54 ` kernel test robot
2025-04-10 10:15 ` Thierry Reding
2025-04-07 10:23 ` [PATCH v3 3/3] clocksource/drivers/timer-tegra186: Remove unused bits Robert Lin
2025-04-10 10:16 ` Thierry Reding
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=20250407102323.2690911-1-robelin@nvidia.com \
--to=robelin@nvidia.com \
--cc=daniel.lezcano@linaro.org \
--cc=jonathanh@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=pohsuns@nvidia.com \
--cc=sumitg@nvidia.com \
--cc=tglx@linutronix.de \
--cc=thierry.reding@gmail.com \
/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