public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: arnd@arndb.de (Arnd Bergmann)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] PCI: imx6:don't sleep in atomic context
Date: Tue, 10 Nov 2015 10:28:46 +0100	[thread overview]
Message-ID: <4800389.dqcmlJY3HC@wuerfel> (raw)
In-Reply-To: <1447144878.3142.3.camel@pengutronix.de>

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.

	Arnd

  reply	other threads:[~2015-11-10  9:28 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1447066080-5859-1-git-send-email-sanjeev_sharma@mentor.com>
2015-11-10  8:41 ` [PATCH] PCI: imx6:don't sleep in atomic context Lucas Stach
2015-11-10  9:28   ` Arnd Bergmann [this message]
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
     [not found] ` <1449042196-25710-1-git-send-email-sanjeev_sharma@mentor.com>
2016-01-06  2:13   ` [PATCH v2] " 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=4800389.dqcmlJY3HC@wuerfel \
    --to=arnd@arndb.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