From: Marek Vasut <marek.vasut@gmail.com>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: linux-pci <linux-pci@vger.kernel.org>,
Marek Vasut <marek.vasut+renesas@gmail.com>,
Geert Uytterhoeven <geert+renesas@glider.be>,
Phil Edworthy <phil.edworthy@renesas.com>,
Simon Horman <horms+renesas@verge.net.au>,
Wolfram Sang <wsa@the-dreams.de>,
Linux-Renesas <linux-renesas-soc@vger.kernel.org>
Subject: Re: [PATCH] PCI: rcar: Poll more often in rcar_pcie_wait_for_dl()
Date: Tue, 22 May 2018 11:48:50 +0200 [thread overview]
Message-ID: <3936f87b-155f-7fc1-1618-287d5d64b7b3@gmail.com> (raw)
In-Reply-To: <CAMuHMdVkeSEsO-jRCzh-_9VkzZ+4X-VAN1KZOA2wB7bUQTrRYg@mail.gmail.com>
On 05/22/2018 11:42 AM, Geert Uytterhoeven wrote:
> Hi Marek,
Hi,
> On Mon, May 21, 2018 at 11:05 PM, Marek Vasut <marek.vasut@gmail.com> wrote:
>> The data link active signal usually takes ~20 uSec to be asserted,
>> poll the bit more often to avoid useless delays in this function.
>> Use udelay() instead of usleep() for such a small delay as suggested
>> by the timer documentation and because this will be used in atomic
>> context later on when the suspend/resume patches land.
>>
>> Signed-off-by: Marek Vasut <marek.vasut+renesas@gmail.com>
>
> Thanks for your patch!
>
>> --- a/drivers/pci/host/pcie-rcar.c
>> +++ b/drivers/pci/host/pcie-rcar.c
>> @@ -529,13 +529,13 @@ static void phy_write_reg(struct rcar_pcie *pcie,
>>
>> static int rcar_pcie_wait_for_dl(struct rcar_pcie *pcie)
>> {
>> - unsigned int timeout = 10;
>> + unsigned int timeout = 10000;
>>
>> while (timeout--) {
>> if ((rcar_pci_read_reg(pcie, PCIETSTR) & DATA_LINK_ACTIVE))
>> return 0;
>>
>> - msleep(5);
>> + udelay(5);
>
> + cpu_relax()?
Is it safe to use in atomic context ? Because of that suspend/resume thing.
>> }
>
> if this ever happens, it will have blocked for more than 50 ms...
Well yes, so did the previous thing.
--
Best regards,
Marek Vasut
next prev parent reply other threads:[~2018-05-22 10:00 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-21 21:05 [PATCH] PCI: rcar: Poll more often in rcar_pcie_wait_for_dl() Marek Vasut
2018-05-22 9:42 ` Geert Uytterhoeven
2018-05-22 9:48 ` Marek Vasut [this message]
2018-05-22 10:33 ` Geert Uytterhoeven
2018-05-22 12:20 ` Marek Vasut
-- strict thread matches above, loose matches on Subject: below --
2018-05-21 17:02 Marek Vasut
2018-05-21 18:09 ` Sergei Shtylyov
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=3936f87b-155f-7fc1-1618-287d5d64b7b3@gmail.com \
--to=marek.vasut@gmail.com \
--cc=geert+renesas@glider.be \
--cc=geert@linux-m68k.org \
--cc=horms+renesas@verge.net.au \
--cc=linux-pci@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=marek.vasut+renesas@gmail.com \
--cc=phil.edworthy@renesas.com \
--cc=wsa@the-dreams.de \
/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).