From: shawn.guo@freescale.com (Shawn Guo)
To: linux-arm-kernel@lists.infradead.org
Subject: FEC driver hangs hardware on i.MX6SX
Date: Sun, 20 Jul 2014 10:57:33 +0800 [thread overview]
Message-ID: <20140720025732.GF8537@dragon> (raw)
Hi Fugang,
Your commit e8fcfcd5684a (net: fec: optimize the clock management to
save power) landed on mainline with v3.16-rc1. It causes a hardware
hang on i.MX6SX, if the rootfs is not on NFS but something else like
MMC.
I think the cause is that PTP is still accessing registers after FEC
driver calls fec_enet_clk_enable(ndev, false) to disable FEC clocks.
Can you please try to provide a fix for this regression soon?
Shawn
WARNING: multiple messages have this Message-ID (diff)
From: Shawn Guo <shawn.guo@freescale.com>
To: Fugang Duan <B38611@freescale.com>
Cc: Frank Li <Frank.li@freescale.com>,
"David S. Miller" <davem@davemloft.net>,
Shawn Guo <shawn.guo@freescale.com>, <netdev@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>
Subject: FEC driver hangs hardware on i.MX6SX
Date: Sun, 20 Jul 2014 10:57:33 +0800 [thread overview]
Message-ID: <20140720025732.GF8537@dragon> (raw)
Hi Fugang,
Your commit e8fcfcd5684a (net: fec: optimize the clock management to
save power) landed on mainline with v3.16-rc1. It causes a hardware
hang on i.MX6SX, if the rootfs is not on NFS but something else like
MMC.
I think the cause is that PTP is still accessing registers after FEC
driver calls fec_enet_clk_enable(ndev, false) to disable FEC clocks.
Can you please try to provide a fix for this regression soon?
Shawn
next reply other threads:[~2014-07-20 2:57 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-20 2:57 Shawn Guo [this message]
2014-07-20 2:57 ` FEC driver hangs hardware on i.MX6SX Shawn Guo
2014-07-20 6:20 ` Richard Cochran
2014-07-20 6:20 ` Richard Cochran
2014-07-21 1:59 ` Shawn Guo
2014-07-21 1:59 ` Shawn Guo
2014-07-21 2:13 ` fugang.duan at freescale.com
2014-07-21 2:13 ` fugang.duan
2014-07-20 8:06 ` fugang.duan at freescale.com
2014-07-20 8:06 ` fugang.duan
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=20140720025732.GF8537@dragon \
--to=shawn.guo@freescale.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.