summaryrefslogtreecommitdiffstats
path: root/mm/hugetlb_cgroup.c
diff options
context:
space:
mode:
authorLucas Stach <l.stach@pengutronix.de>2014-07-31 20:16:05 +0200
committerBjorn Helgaas <bhelgaas@google.com>2014-09-04 15:32:21 +0200
commit3e3e406e3807235906ee0b7c697664ea6dfd88de (patch)
treede09c4ec9710c207118fac0cd4ab52fde2f1d856 /mm/hugetlb_cgroup.c
parentMAINTAINERS: Add Lucas Stach as co-maintainer for i.MX6 PCI driver (diff)
downloadlinux-3e3e406e3807235906ee0b7c697664ea6dfd88de.tar.xz
linux-3e3e406e3807235906ee0b7c697664ea6dfd88de.zip
PCI: imx6: Put LTSSM in "Detect" state before disabling it
This fixes a boot hang observed when the bootloader already enabled the PCIe link for its own use. The fundamental problem is that Freescale forgot to wire up the core reset, so software doesn't have a sane way to get the core into a defined state. According to the DW PCIe core reference manual, configuration of the core may only happen when the LTSSM is disabled, so this is one of the first things we need to do. Apparently this isn't safe to do when the LTSSM is in any state other than "detect" as we observe an instant machine hang when trying to do so while the link is already up. As a workaround, force LTSSM into detect state right before hitting the disable switch. There is still a race window because the LTSSM may transition out of "detect" before we can disable it, but it's the best we can do for now. [bhelgaas: mention race window] Link: http://lkml.kernel.org/r/1406830565-23450-3-git-send-email-l.stach@pengutronix.de Reported-by: Fabio Estevam <fabio.estevam@freescale.com> Signed-off-by: Lucas Stach <l.stach@pengutronix.de> Signed-off-by: Bjorn Helgaas <bhelgaas@google.com> Acked-by: Tim Harvey <tharvey@gateworks.com>
Diffstat (limited to 'mm/hugetlb_cgroup.c')
0 files changed, 0 insertions, 0 deletions