devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Kartik <kkartik@nvidia.com>
To: <daniel.lezcano@linaro.org>, <tglx@linutronix.de>,
	<robh+dt@kernel.org>, <krzk+dt@kernel.org>,
	<thierry.reding@gmail.com>, <jonathanh@nvidia.com>,
	<spujar@nvidia.com>, <akhilrajeev@nvidia.com>,
	<rgumasta@nvidia.com>, <pshete@nvidia.com>, <vidyas@nvidia.com>,
	<mperttunen@nvidia.com>, <mkumard@nvidia.com>,
	<linux-kernel@vger.kernel.org>, <devicetree@vger.kernel.org>,
	<linux-tegra@vger.kernel.org>, <kkartik@nvidia.com>
Subject: [PATCH 0/6] Add watchdog timer support for Tegra186/194/234 SoCs
Date: Thu, 14 Apr 2022 13:55:32 +0530	[thread overview]
Message-ID: <1649924738-17990-1-git-send-email-kkartik@nvidia.com> (raw)

The native timers IP block found on Tegra SoCs implements a watchdog
timer that can be used to recover from system hangs. This series of
patches adds support for watchdog timers available on Tegra186,
Tegra194 and Tegra234 SOC's.

To keep the history intact, I added Tegra234 driver change as separate.
The original patchset is an old one authored by Thierry.

Kartik (4):
  dt-bindings: timer: Add Tegra186 & Tegra234 Timer
  clocksource/drivers/timer-tegra186: Add support for Tegra234 SoC
  arm64: tegra: Enable native timers on Tegra186
  arm64: tegra: Enable native timers on Tegra234

Thierry Reding (2):
  clocksource: Add Tegra186 timers support
  arm64: tegra: Enable native timers on Tegra194

 .../bindings/timer/nvidia,tegra186-timer.yaml | 116 ++++
 arch/arm64/boot/dts/nvidia/tegra186.dtsi      |   2 +-
 arch/arm64/boot/dts/nvidia/tegra194.dtsi      |  16 +
 arch/arm64/boot/dts/nvidia/tegra234.dtsi      |  22 +
 drivers/clocksource/Kconfig                   |   8 +
 drivers/clocksource/Makefile                  |   1 +
 drivers/clocksource/timer-tegra186.c          | 514 ++++++++++++++++++
 7 files changed, 678 insertions(+), 1 deletion(-)
 create mode 100644 Documentation/devicetree/bindings/timer/nvidia,tegra186-timer.yaml
 create mode 100644 drivers/clocksource/timer-tegra186.c

-- 
2.17.1


             reply	other threads:[~2022-04-14  8:25 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-14  8:25 Kartik [this message]
2022-04-14  8:25 ` [PATCH 1/6] dt-bindings: timer: Add Tegra186 & Tegra234 Timer Kartik
2022-04-14 18:20   ` Rob Herring
2022-04-20 13:14     ` Kartik
2022-04-14  8:25 ` [PATCH 2/6] clocksource: Add Tegra186 timers support Kartik
2022-04-14  8:25 ` [PATCH 3/6] clocksource/drivers/timer-tegra186: Add support for Tegra234 SoC Kartik
2022-04-14  8:25 ` [PATCH 4/6] arm64: tegra: Enable native timers on Tegra186 Kartik
2022-04-14  8:25 ` [PATCH 5/6] arm64: tegra: Enable native timers on Tegra194 Kartik
2022-04-14  8:25 ` [PATCH 6/6] arm64: tegra: Enable native timers on Tegra234 Kartik
2022-06-20 15:45 ` [PATCH 0/6] Add watchdog timer support for Tegra186/194/234 SoCs 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=1649924738-17990-1-git-send-email-kkartik@nvidia.com \
    --to=kkartik@nvidia.com \
    --cc=akhilrajeev@nvidia.com \
    --cc=daniel.lezcano@linaro.org \
    --cc=devicetree@vger.kernel.org \
    --cc=jonathanh@nvidia.com \
    --cc=krzk+dt@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-tegra@vger.kernel.org \
    --cc=mkumard@nvidia.com \
    --cc=mperttunen@nvidia.com \
    --cc=pshete@nvidia.com \
    --cc=rgumasta@nvidia.com \
    --cc=robh+dt@kernel.org \
    --cc=spujar@nvidia.com \
    --cc=tglx@linutronix.de \
    --cc=thierry.reding@gmail.com \
    --cc=vidyas@nvidia.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;
as well as URLs for NNTP newsgroup(s).