From: Sanjeev Sharma <sanjeev_sharma@mentor.com>
To: <Richard.Zhu@freescale.com>, <l.stach@pengutronix.de>,
<bhelgaas@google.com>
Cc: <linux-pci@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
<linux-kernel@vger.kernel.org>,
Sanjeev Sharma <sanjeev_sharma@mentor.com>,
David Mueller <dave.mueller@gmx.ch>
Subject: [PATCH] PCI: imx6:don't sleep in atomic context
Date: Mon, 9 Nov 2015 16:18:00 +0530 [thread overview]
Message-ID: <1447066080-5859-1-git-send-email-sanjeev_sharma@mentor.com> (raw)
If additional PCIe switch get connected between the
host and the NIC,the kernel crashes with "BUG:
scheduling while atomic". To handle this we need to
call mdelay() instead of usleep_range().
For more detail please refer bugzilla.kernel.org, Bug
100031
Signed-off-by: Sanjeev Sharma <sanjeev_sharma@mentor.com>
Signed-off-by: David Mueller <dave.mueller@gmx.ch>
---
drivers/pci/host/pci-imx6.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/pci/host/pci-imx6.c b/drivers/pci/host/pci-imx6.c
index 233a196..9769b13 100644
--- a/drivers/pci/host/pci-imx6.c
+++ b/drivers/pci/host/pci-imx6.c
@@ -499,7 +499,7 @@ static int imx6_pcie_link_up(struct pcie_port *pp)
* Wait a little bit, then re-check if the link finished
* the training.
*/
- usleep_range(1000, 2000);
+ mdelay(1000);
}
/*
* From L0, initiate MAC entry to gen2 if EP/RC supports gen2.
--
1.7.11.7
next reply other threads:[~2015-11-09 10:49 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-09 10:48 Sanjeev Sharma [this message]
2015-11-10 8:41 ` Lucas Stach
2015-11-10 9:28 ` Arnd Bergmann
2015-11-10 9:35 ` Lucas Stach
2015-11-10 9:45 ` Arnd Bergmann
2015-11-16 9:36 ` Sharma, Sanjeev
2015-11-24 13:57 ` Lucas Stach
2015-12-02 7:43 ` [PATCH v2] " Sanjeev Sharma
2016-01-06 2:13 ` Bjorn Helgaas
2016-01-06 22:04 ` [PATCH] " Bjorn Helgaas
2016-02-18 7:17 ` Sharma, Sanjeev
2016-02-18 15:08 ` Bjorn Helgaas
2016-02-19 9:18 ` Sharma, Sanjeev
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=1447066080-5859-1-git-send-email-sanjeev_sharma@mentor.com \
--to=sanjeev_sharma@mentor.com \
--cc=Richard.Zhu@freescale.com \
--cc=bhelgaas@google.com \
--cc=dave.mueller@gmx.ch \
--cc=l.stach@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.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®