From: Lucas Stach <l.stach@pengutronix.de>
To: Arnd Bergmann <arnd@arndb.de>
Cc: linux-arm-kernel@lists.infradead.org,
Sanjeev Sharma <sanjeev_sharma@mentor.com>,
linux-pci@vger.kernel.org, Richard.Zhu@freescale.com,
linux-kernel@vger.kernel.org, David Mueller <dave.mueller@gmx.ch>,
bhelgaas@google.com
Subject: Re: [PATCH] PCI: imx6:don't sleep in atomic context
Date: Tue, 10 Nov 2015 10:35:10 +0100 [thread overview]
Message-ID: <1447148110.3142.6.camel@pengutronix.de> (raw)
In-Reply-To: <4800389.dqcmlJY3HC@wuerfel>
Am Dienstag, den 10.11.2015, 10:28 +0100 schrieb Arnd Bergmann:
> On Tuesday 10 November 2015 09:41:18 Lucas Stach wrote:
> > > 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);
> >
> > A mdelay(1000) is a whole different timescale than a usleep(1000). If
> > this patch works for you with mdelay(1) or maybe mdelay(2) I would be
> > fine with it.
>
> mdelay(1) is still a really long time to block the CPU for, on potentially
> every config space access.
>
> Everybody else just returns the link status here, which seems to be
> the better alternative. If you need to delay the startup, better have
> a msleep(1) loop in the initial probe function where you are allowed to
> sleep.
>
Yes, it's somewhere on my TODO list to rework the link-up handling here,
but as there are quite a few timing and ordering implications in that
code, this needs a good thought and a good deal of testing. So I'm
inclined to ACK the current patch to get rid of the obvious bug and sort
things out properly in a follow on patchset.
Regards,
Lucas
--
Pengutronix e.K. | Lucas Stach |
Industrial Linux Solutions | http://www.pengutronix.de/ |
next prev parent reply other threads:[~2015-11-10 9:35 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-09 10:48 [PATCH] PCI: imx6:don't sleep in atomic context Sanjeev Sharma
2015-11-10 8:41 ` Lucas Stach
2015-11-10 9:28 ` Arnd Bergmann
2015-11-10 9:35 ` Lucas Stach [this message]
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=1447148110.3142.6.camel@pengutronix.de \
--to=l.stach@pengutronix.de \
--cc=Richard.Zhu@freescale.com \
--cc=arnd@arndb.de \
--cc=bhelgaas@google.com \
--cc=dave.mueller@gmx.ch \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=sanjeev_sharma@mentor.com \
/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).