linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: l.stach@pengutronix.de (Lucas Stach)
To: linux-arm-kernel@lists.infradead.org
Subject: imx6: PCIe imx6_pcie_assert_core_reset() hangs after watchdog reset
Date: Wed, 08 Apr 2015 15:37:06 +0200	[thread overview]
Message-ID: <1428500226.2809.28.camel@pengutronix.de> (raw)
In-Reply-To: <CAOMZO5CDOJXp3Hbe8a9dPh=krWhw-i5i8Zoa5Hb+2XGAdou7ew@mail.gmail.com>

Am Mittwoch, den 08.04.2015, 10:32 -0300 schrieb Fabio Estevam:
> Hi Stefan,
> 
> On Wed, Mar 25, 2015 at 6:29 AM, Stefan Roese <sr@denx.de> wrote:
> > Hi!
> >
> > I'm currently facing a problem in the imx6 PCIe driver. The
> > problem happens, after the Linux imx6 internal watchdog has timed-out
> > and issues a reset (this is intended, as I'm testing this wdog right
> > now). But the next Linux boot hangs in imx6_pcie_assert_core_reset()
> > while accessing a register from the PCIe port logic memory:
> 
> I am not able to reproduce this problem on a imx6q-sabresd.
> 
> Even with PCI enabled in U-boot, when I run 'reboot' the kernel
> re-starts fine here.
> 
If you do a proper shutdown in Linux the kernel will make sure to
properly disable PCIe before rebooting and leave things behind in a
deterministic state.

The problem appears when a watchdog reset happens, so the kernel has no
chance to clean things up before rebooting. This isn't a problem if you
do a full system reset via the watchdog out line to the PMIC, but gets
ugly if only the i.MX6 is reset (which apparently doesn't clear the GPR
bits).

Regards,
Lucas

-- 
Pengutronix e.K.             | Lucas Stach                 |
Industrial Linux Solutions   | http://www.pengutronix.de/  |

  reply	other threads:[~2015-04-08 13:37 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-25  9:29 imx6: PCIe imx6_pcie_assert_core_reset() hangs after watchdog reset Stefan Roese
2015-03-25  9:39 ` Lucas Stach
2015-03-25 10:32   ` Stefan Roese
2015-03-25 10:38     ` Lucas Stach
2015-03-26 11:06     ` Lucas Stach
2015-03-26 13:23       ` Tim Harvey
2015-03-26 13:39         ` Lucas Stach
2016-11-06 15:31           ` Philippe De Muyter
2016-11-06 16:59             ` Fabio Estevam
2016-11-07 10:34               ` Lucas Stach
2016-11-07 12:15                 ` Fabio Estevam
2016-11-07 14:23                   ` Lucas Stach
2017-01-19 14:24                   ` Lucas Stach
2017-01-20 16:02                     ` Fabio Estevam
2015-04-08 13:32 ` Fabio Estevam
2015-04-08 13:37   ` Lucas Stach [this message]
2015-04-08 13:42     ` Fabio Estevam

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=1428500226.2809.28.camel@pengutronix.de \
    --to=l.stach@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).