From: Boris Lysov <arzamas-16@mail.ee>
To: linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
linux-watchdog@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Missing ARM TWD Watchdog driver?
Date: Mon, 17 Jan 2022 19:01:12 +0300 [thread overview]
Message-ID: <20220117190112.2b2c2f53@pc> (raw)
Hello everyone,
I stumbled upon the ARM TWD Watchdog driver which seems to be missing (or I'm
just blind).
As per commit a33f5c380c4bd3fa5278d690421b72052456d9fe ("Merge tag
'xfs-5.17-merge-3' of git://git.kernel.org/pub/scm/fs/xfs/xfs-linux"), multiple
device trees declare usage of arm-twd:
arch/arm/boot/dts/arm-realview-eb-mp.dtsi
arch/arm/boot/dts/arm-realview-pb11mp.dts
arch/arm/boot/dts/arm-realview-pbx-a9.dts
arch/arm/boot/dts/bcm5301x.dtsi
arch/arm/boot/dts/bcm63138.dtsi
arch/arm/boot/dts/bcm-hr2.dtsi
arch/arm/boot/dts/bcm-nsp.dtsi
arch/arm/boot/dts/berlin2cd.dtsi
arch/arm/boot/dts/highbank.dts
arch/arm/boot/dts/mmp3.dtsi
arch/arm/boot/dts/owl-s500.dtsi
arch/arm/boot/dts/spear13xx.dtsi
arch/arm/boot/dts/ste-dbx5x0.dtsi
arch/arm/boot/dts/vexpress-v2p-ca5s.dts
arch/arm/boot/dts/vexpress-v2p-ca9.dts
and it is documented in
Documentation/devicetree/bindings/watchdog/arm,twd-wdt.yaml
However I could not find the driver itself. I tried running case-insensitive
grep and ripgrep to no avail. Does this driver actually exist? Is it gone?
I'm not well experienced with LKML yet and I apologize for if I asked
the question on the inappropriate mailing list. As per 3.3 of [1], I'm kindly
asking to CC me with answers.
Thanks!
[1] The linux-kernel mailing list FAQ http://vger.kernel.org/lkml/
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next reply other threads:[~2022-01-17 16:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-17 16:01 Boris Lysov [this message]
2022-01-17 16:34 ` Missing ARM TWD Watchdog driver? Guenter Roeck
2022-01-17 17:02 ` Mark Rutland
2022-01-18 1:25 ` Boris Lysov
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=20220117190112.2b2c2f53@pc \
--to=arzamas-16@mail.ee \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-watchdog@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).