From: Stefan Agner <stefan@agner.ch>
To: shawnguo@kernel.org, andrew.smirnov@gmail.com
Cc: fabio.estevam@freescale.com, linux-kernel@vger.kernel.org
Subject: i.MX 7 boot freeze with 4.13-rc3
Date: Tue, 01 Aug 2017 19:38:08 -0700 [thread overview]
Message-ID: <444e26ee5297209f1add5cb0f7a949be@agner.ch> (raw)
Hi,
Linux 4.13-rc3 seems to freeze on a Colibri iMX7:
...
8021q: 802.1Q VLAN Support v1.8
Key type dns_resolver registered
Registering SWP/SWPB emulation handler
vdd1p0d: supplied by DCDC3
asoc-simple-card sound: sgtl5000 <-> 308a0000.sai mapping ok
<freeze>
I started a bisect run and I had a hard time to get properly through
imx-dt-4.13. On the imx-dt branch the i.MX 7 GPC changes seem to cause
the UART to only output garbage:
...
io scheduler mq-deadline registered
io scheduler kyber registered
imx7-pgc imx7-pgc-domain.1: Failed to get domain's regulator
�������������������������������������������������~88����������������
It turned out at the merge point 2cb6115deba0 (Merge tag 'imx-dt-4.13'
of...) the behavior changed to the freeze seen in 4.13-rc3.
Reverting 0f90b43ac71b (ARM: dts: imx7s: Add node for GPC) helped in
both cases, and when using v4.13-rc3 (I also had to revert a816d5750edf
and 34adfaa3d404 which depend on this GPC change).
I assume that the merge adds driver changes which changes the behavior
of the GPC driver, hence freeze vs. garbage?
At the moment it is unclear to me why the GPC change leads to freezes on
our platform. On which platform have this changes been tested? Any other
i.MX 7 platforms seeing freezes?
--
Stefan
next reply other threads:[~2017-08-02 2:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-02 2:38 Stefan Agner [this message]
2017-08-02 16:57 ` Andrey Smirnov
2017-08-02 18:26 ` Stefan Agner
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=444e26ee5297209f1add5cb0f7a949be@agner.ch \
--to=stefan@agner.ch \
--cc=andrew.smirnov@gmail.com \
--cc=fabio.estevam@freescale.com \
--cc=linux-kernel@vger.kernel.org \
--cc=shawnguo@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
all inboxes | Powered by JetHome®