From: Chen-Yu Tsai <wens@csie.org>
To: Maxime Ripard <maxime.ripard@bootlin.com>
Cc: devicetree <devicetree@vger.kernel.org>,
linux-kernel <linux-kernel@vger.kernel.org>,
"Rob Herring" <robh+dt@kernel.org>,
"Clément Péron" <peron.clem@gmail.com>,
"Jagan Teki" <jagan@amarulasolutions.com>,
linux-arm-kernel <linux-arm-kernel@lists.infradead.org>,
"Icenowy Zheng" <icenowy@aosc.io>
Subject: Re: [PATCH 2/2] arm64: dts: h6: Add watchdog node
Date: Fri, 5 Apr 2019 22:35:08 +0800 [thread overview]
Message-ID: <CAGb2v65wcEAUTwRhC42iRkPaWXLGX1CJeq+TSzHVTOrT+L=8vA@mail.gmail.com> (raw)
In-Reply-To: <20190405090236.e7vnyjzxmzfke3d6@flea>
On Fri, Apr 5, 2019 at 5:02 PM Maxime Ripard <maxime.ripard@bootlin.com> wrote:
>
> On Thu, Apr 04, 2019 at 03:57:36PM +0200, Clément Péron wrote:
> > Allwinner H6 has a watchog compatible with A31.
> >
> > Declare it in the device tree.
> >
> > Signed-off-by: Clément Péron <peron.clem@gmail.com>
>
> Applied both, thanks!
> Maxime
IIRC there are 3 watchdogs on the H6. One is the trusted watchdog,
which should be reserved for underlying firmware.
The other two are the normal and R-block watchdog. Although they
look the same, the "normal" one can't reset the system. :(
That one is actually the one ATF currently uses. So reboot doesn't
work on the H6.
ChenYu
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2019-04-05 14:35 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-04 13:57 [PATCH 1/2] dt-bindings: watchdog: sunxi: Add H6 compatible Clément Péron
2019-04-04 13:57 ` [PATCH 2/2] arm64: dts: h6: Add watchdog node Clément Péron
2019-04-05 9:02 ` Maxime Ripard
2019-04-05 14:35 ` Chen-Yu Tsai [this message]
2019-04-05 14:50 ` Maxime Ripard
2019-04-05 14:59 ` Chen-Yu Tsai
2019-04-05 15:08 ` Maxime Ripard
2019-04-05 16:24 ` Clément Péron
2019-04-07 14:27 ` Clément Péron
2019-04-08 8:16 ` Maxime Ripard
2019-04-08 21:23 ` Clément Péron
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='CAGb2v65wcEAUTwRhC42iRkPaWXLGX1CJeq+TSzHVTOrT+L=8vA@mail.gmail.com' \
--to=wens@csie.org \
--cc=devicetree@vger.kernel.org \
--cc=icenowy@aosc.io \
--cc=jagan@amarulasolutions.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maxime.ripard@bootlin.com \
--cc=peron.clem@gmail.com \
--cc=robh+dt@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).