From: Shawn Guo <shawnguo@kernel.org>
To: Lucas Stach <l.stach@pengutronix.de>
Cc: Fabio Estevam <festevam@gmail.com>,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
kernel@pengutronix.de, patchwork-lst@pengutronix.de
Subject: Re: [PATCH 01/10] ARM: dts: imx6: rdu2: enable WDOG1
Date: Sat, 30 Jan 2021 21:55:33 +0800 [thread overview]
Message-ID: <20210130135532.GK907@dragon> (raw)
In-Reply-To: <20210125184736.1226435-1-l.stach@pengutronix.de>
On Mon, Jan 25, 2021 at 07:47:27PM +0100, Lucas Stach wrote:
> From: Philipp Zabel <p.zabel@pengutronix.de>
>
> Enable the i.MX6 WDOG1 internal watchdog for warm reboots. This allows
> to issue emergency restarts without clearing the RAM, so collecting oops
> logs from ramoops pstore in barebox becomes feasible.
>
> Signed-off-by: Philipp Zabel <p.zabel@pengutronix.de>
> Signed-off-by: Lucas Stach <l.stach@pengutronix.de>
Applied all, thanks.
prev parent reply other threads:[~2021-01-30 13:56 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-25 18:47 [PATCH 01/10] ARM: dts: imx6: rdu2: enable WDOG1 Lucas Stach
2021-01-25 18:47 ` [PATCH 02/10] ARM: dts: imx6: RDU2: reduce i2c drive-strength Lucas Stach
2021-01-25 18:47 ` [PATCH 03/10] ARM: dts: imx6: RDU2: enable RMI4 reduced reporting Lucas Stach
2021-01-25 18:47 ` [PATCH 04/10] ARM: dts: imx6: RDU2: only trigger IRQ on falling edge ucs1002 ALERT pin Lucas Stach
2021-01-25 18:47 ` [PATCH 05/10] ARM: dts: imx6: RDU2: adjust audio devices nomenclature Lucas Stach
2021-01-25 18:47 ` [PATCH 06/10] arm64: dts: zii-ultra: add sound support Lucas Stach
2021-01-25 18:47 ` [PATCH 07/10] arm64: dts: zii-ultra: fix i2c pin configuration Lucas Stach
2021-01-25 18:47 ` [PATCH 08/10] arm64: dts: zii-ultra: limit USB ports to USB2 speed Lucas Stach
2021-01-25 18:47 ` [PATCH 09/10] arm64: dts: zii-ultra: only trigger IRQ on falling edge ucs1002 ALERT pin Lucas Stach
2021-01-25 18:47 ` [PATCH 10/10] arm64: dts: zii-rmb3: enable RMI4 reduced reporting Lucas Stach
2021-01-30 13:55 ` Shawn Guo [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=20210130135532.GK907@dragon \
--to=shawnguo@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=festevam@gmail.com \
--cc=kernel@pengutronix.de \
--cc=l.stach@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=patchwork-lst@pengutronix.de \
/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).