From: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>
To: Jia-Ju Bai <baijiaju1990@gmail.com>,
davem@davemloft.net, frankt@promise.com, andre@linux-ide.org
Cc: linux-ide@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] ide: pdc202xx_new: Replace mdelay with usleep_range in detect_pll_input_clock
Date: Wed, 11 Apr 2018 11:33:59 +0300 [thread overview]
Message-ID: <7558e956-62bd-39b9-6ff1-4d5f7ee2c9a3@cogentembedded.com> (raw)
In-Reply-To: <1523433162-3910-1-git-send-email-baijiaju1990@gmail.com>
Hello!
On 4/11/2018 10:52 AM, Jia-Ju Bai wrote:
> detect_pll_input_clock() is never called in atomic context.
>
> detect_pll_input_clock() is only called by init_chipset_pdcnew(), which
> is set as ".init_chipset" in struct ide_port_info.
> This function is not called in atomic context.
>
> Despite never getting called from atomic context, detect_pll_input_clock()
> calls mdelay() to busily wait.
> This is not necessary and can be replaced with usleep_range() to
> avoid busy waiting.
>
> This is found by a static analysis tool named DCNS written by myself.
> And I also manually check it.
>
> Signed-off-by: Jia-Ju Bai <baijiaju1990@gmail.com>
> ---
> drivers/ide/pdc202xx_new.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/ide/pdc202xx_new.c b/drivers/ide/pdc202xx_new.c
> index b33646b..6afa66d 100644
> --- a/drivers/ide/pdc202xx_new.c
> +++ b/drivers/ide/pdc202xx_new.c
> @@ -258,7 +258,7 @@ static long detect_pll_input_clock(unsigned long dma_base)
> outb(scr1 | 0x40, dma_base + 0x03);
>
> /* Let the counter run for 10 ms. */
> - mdelay(10);
> + usleep_range(10);
This function takes 2 arguments.
[...]
MBR, Sergei
next prev parent reply other threads:[~2018-04-11 8:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-11 7:52 Jia-Ju Bai
2018-04-11 8:33 ` Sergei Shtylyov [this message]
2018-04-11 8:35 ` Jia-Ju Bai
2018-04-12 4:05 ` kbuild test robot
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=7558e956-62bd-39b9-6ff1-4d5f7ee2c9a3@cogentembedded.com \
--to=sergei.shtylyov@cogentembedded.com \
--cc=andre@linux-ide.org \
--cc=baijiaju1990@gmail.com \
--cc=davem@davemloft.net \
--cc=frankt@promise.com \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@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®