From: Shawn Guo <shawnguo@kernel.org>
To: Andrej Picej <andrej.picej@norik.com>
Cc: robh+dt@kernel.org, krzysztof.kozlowski+dt@linaro.org,
conor+dt@kernel.org, s.hauer@pengutronix.de,
kernel@pengutronix.de, festevam@gmail.com, linux-imx@nxp.com,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, S.Riedmueller@phytec.de,
S.Mueller-Klieser@phytec.de, upstream@phytec.de
Subject: Re: [PATCH v2 2/3] ARM: dts: imx6: pfla02: Rely on PMIC reboot/reset handler
Date: Sun, 30 Jul 2023 14:41:53 +0800 [thread overview]
Message-ID: <20230730064153.GZ151430@dragon> (raw)
In-Reply-To: <20230719114328.2239818-2-andrej.picej@norik.com>
On Wed, Jul 19, 2023 at 01:43:27PM +0200, Andrej Picej wrote:
> Due to the missing signal connection between i.MX6 WDOG_B pin and the
> PMICs external reset, the internal i.MX6 watchdog is not able to reset
> the phyFLEX SoM properly. Thus disable the internal i.MX6 watchdog to
> prevent unexpected PMIC settings after reset.
>
> NOTE: This patch should not be backported as it might break existing
> uses and fixes in bootloaders.
>
> Signed-off-by: Andrej Picej <andrej.picej@norik.com>
Applied, thanks!
next prev parent reply other threads:[~2023-07-30 6:42 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-19 11:43 [PATCH v2 1/3] ARM: dts: imx6: phytec: fix RTC interrupt level Andrej Picej
2023-07-19 11:43 ` [PATCH v2 2/3] ARM: dts: imx6: pfla02: Rely on PMIC reboot/reset handler Andrej Picej
2023-07-19 11:50 ` Stefan Riedmüller
2023-07-30 6:41 ` Shawn Guo [this message]
2023-07-19 11:43 ` [PATCH v2 3/3] ARM: dts: imx6: phycore: " Andrej Picej
2023-07-19 11:50 ` Stefan Riedmüller
2023-07-30 6:42 ` Shawn Guo
2023-07-19 11:49 ` [PATCH v2 1/3] ARM: dts: imx6: phytec: fix RTC interrupt level Stefan Riedmüller
2023-07-30 6:34 ` Shawn Guo
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=20230730064153.GZ151430@dragon \
--to=shawnguo@kernel.org \
--cc=S.Mueller-Klieser@phytec.de \
--cc=S.Riedmueller@phytec.de \
--cc=andrej.picej@norik.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=festevam@gmail.com \
--cc=kernel@pengutronix.de \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-imx@nxp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=robh+dt@kernel.org \
--cc=s.hauer@pengutronix.de \
--cc=upstream@phytec.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).