From: u.kleine-koenig@pengutronix.de (Uwe Kleine-König)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v1] watchdog: imx2: fix hang-up on boot for i.MX21, i.MX27 and i.MX31 SoCs
Date: Wed, 28 Dec 2016 21:38:05 +0100 [thread overview]
Message-ID: <20161228203805.26urb7hzpb5kgigr@pengutronix.de> (raw)
In-Reply-To: <CAOMZO5CqpfH6nq_mqPitztfSX4-oR4-61z7PnYhvOYAVnYF0yA@mail.gmail.com>
On Sat, Dec 24, 2016 at 11:00:59AM -0200, Fabio Estevam wrote:
> On Sat, Dec 10, 2016 at 11:06 PM, Vladimir Zapolskiy <vz@mleia.com> wrote:
>
> > static const struct of_device_id imx2_wdt_dt_ids[] = {
> > - { .compatible = "fsl,imx21-wdt", },
> > + { .compatible = "fsl,imx21-wdt", .data = IMX2_WDT_NO_WMCR },
> > + { .compatible = "fsl,imx25-wdt", },
> > + { .compatible = "fsl,imx27-wdt", .data = IMX2_WDT_NO_WMCR },
> > + { .compatible = "fsl,imx31-wdt", .data = IMX2_WDT_NO_WMCR },
> > + { .compatible = "fsl,imx35-wdt", },
> > + { .compatible = "fsl,imx50-wdt", },
> > + { .compatible = "fsl,imx51-wdt", },
> > + { .compatible = "fsl,imx53-wdt", },
> > + { .compatible = "fsl,imx6q-wdt", },
> > + { .compatible = "fsl,imx6sl-wdt", },
> > + { .compatible = "fsl,imx6sx-wdt", },
> > + { .compatible = "fsl,imx6ul-wdt", },
> > + { .compatible = "fsl,imx7d-wdt", },
> > + { .compatible = "fsl,vf610-wdt", },
> > { /* sentinel */ }
>
> I understand this compatible list is not very nice, but in order to
> keep old dtb's working I don't see a better solution, so:
>
> Reviewed-by: Fabio Estevam <fabio.estevam@nxp.com>
You can at least drop fsl,imx27-wdt and fsl,imx31-wdt which then fall
back correctly to fsl,imx21-wdt.
Best regards
Uwe
--
Pengutronix e.K. | Uwe Kleine-K?nig |
Industrial Linux Solutions | http://www.pengutronix.de/ |
prev parent reply other threads:[~2016-12-28 20:38 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-11 1:06 [PATCH v1] watchdog: imx2: fix hang-up on boot for i.MX21, i.MX27 and i.MX31 SoCs Vladimir Zapolskiy
2016-12-11 2:18 ` Guenter Roeck
2016-12-11 8:58 ` Magnus Lilja
2016-12-11 9:35 ` Uwe Kleine-König
2016-12-11 10:01 ` Vladimir Zapolskiy
2016-12-11 10:26 ` Uwe Kleine-König
2016-12-11 11:21 ` Vladimir Zapolskiy
2016-12-11 12:28 ` Uwe Kleine-König
2016-12-23 1:55 ` Guenter Roeck
2016-12-23 8:20 ` Vladimir Zapolskiy
2016-12-23 8:32 ` Uwe Kleine-König
2016-12-23 9:27 ` Vladimir Zapolskiy
2016-12-23 10:01 ` Uwe Kleine-König
2016-12-23 11:21 ` Vladimir Zapolskiy
2016-12-23 14:11 ` Uwe Kleine-König
2016-12-24 5:08 ` Vladimir Zapolskiy
2016-12-28 20:54 ` Uwe Kleine-König
2016-12-28 21:33 ` Fabio Estevam
2016-12-28 21:46 ` Uwe Kleine-König
2016-12-28 23:39 ` Fabio Estevam
2016-12-29 22:04 ` Uwe Kleine-König
2016-12-29 23:40 ` Fabio Estevam
2016-12-24 13:00 ` Fabio Estevam
2016-12-28 20:38 ` Uwe Kleine-König [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=20161228203805.26urb7hzpb5kgigr@pengutronix.de \
--to=u.kleine-koenig@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.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).