From: Ajay Singh <ajay.kathat@microchip.com>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: <devel@driverdev.osuosl.org>, <venkateswara.kaja@microchip.com>,
<linux-wireless@vger.kernel.org>, <ganesh.krishna@microchip.com>,
<adham.abozaeid@microchip.com>, <aditya.shankar@microchip.com>
Subject: Re: [PATCH 7/8] staging: wilc1000: replace udelay with usleep_range
Date: Sat, 4 Aug 2018 21:07:32 +0530 [thread overview]
Message-ID: <20180804210732.7952867a@ajaysk-VirtualBox> (raw)
In-Reply-To: <20180805141117.GA3895@kroah.com>
Hi Greg,
On Sun, 5 Aug 2018 16:11:17 +0200
Greg KH <gregkh@linuxfoundation.org> wrote:
> On Fri, Aug 03, 2018 at 01:58:51PM +0530, Ajay Singh wrote:
> > Hi Greg,
> >
> > On Thu, 2 Aug 2018 09:34:15 +0200
> > Greg KH <gregkh@linuxfoundation.org> wrote:
> >
> > > On Sun, Jul 29, 2018 at 11:36:56AM +0530, Ajay Singh wrote:
> > > > Cleanup patch to avoid the below checkpatch reported issue.
> > > >
> > > > "usleep_range is preferred over udelay; see
> > > > Documentation/timers/timers-howto.txt".
> > > >
> > > > Signed-off-by: Ajay Singh <ajay.kathat@microchip.com>
> > > > ---
> > > > drivers/staging/wilc1000/wilc_wlan.c | 2 +-
> > > > 1 file changed, 1 insertion(+), 1 deletion(-)
> > > >
> > > > diff --git a/drivers/staging/wilc1000/wilc_wlan.c
> > > > b/drivers/staging/wilc1000/wilc_wlan.c index 6bac3f7..655952a
> > > > 100644 --- a/drivers/staging/wilc1000/wilc_wlan.c
> > > > +++ b/drivers/staging/wilc1000/wilc_wlan.c
> > > > @@ -425,7 +425,7 @@ void chip_wakeup(struct wilc *wilc)
> > > > } while (wilc_get_chipid(wilc, true) == 0);
> > > > } else if ((wilc->io_type & 0x1) == HIF_SDIO) {
> > > > wilc->hif_func->hif_write_reg(wilc, 0xfa, 1);
> > > > - udelay(200);
> > > > + usleep_range(200, 201);
> > >
> > > Hah, that's funny.
> > >
> > > No, do it right, don't try to game checkpatch here.
> >
> > The delay of 200us was added to have a short wait between HW
> > register write and read operation. The short delay of 200us was
> > enough for this but the duration range is not available. So to
> > replace udelay() of 200us with usleep_range(), I have used used
> > range from 200, 201.
>
> What do you mean that "the duration range is not available"? You know
> what is allowed here, please provide that range. You do know the
> reason for this suggestion from checkpatch, right? By doing what you
> did here, you are totally subverting the real goal here, you are not
> solving anything.
Actually, we need a delay of 200us but there is no upper limit for it.
usleep_range() also expects upper limit, so added '1us' to the
lower limit (200us) to use for upper limit value.
I will rework on this and resubmit the patch.
Thank you.
Regards,
Ajay
next prev parent reply other threads:[~2018-08-06 13:29 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-29 6:06 [PATCH 0/8] staging: wilc1000: changes to address TODO items Ajay Singh
2018-07-29 6:06 ` [PATCH 1/8] staging: wilc1000: fix TODO to compile spi and sdio components in single module Ajay Singh
2018-07-29 6:06 ` [PATCH 2/8] staging: wilc1000: remove unnecessary comments and comments description Ajay Singh
2018-07-29 6:06 ` [PATCH 3/8] staging: wilc1000: remove unnecessary copyright information in file Ajay Singh
2018-08-02 7:33 ` Greg KH
2018-08-02 8:24 ` Ajay Singh
2018-07-29 6:06 ` [PATCH 4/8] staging: wilc1000: modified debug log messages description Ajay Singh
2018-07-29 6:06 ` [PATCH 5/8] staging: wilc1000: added comments for 'hif_cs' mutex lock Ajay Singh
2018-07-29 6:06 ` [PATCH 6/8] staging: wilc1000: rename 'rcvd_ch_cnt' element in 'user_scan_req' struct Ajay Singh
2018-07-29 6:06 ` [PATCH 7/8] staging: wilc1000: replace udelay with usleep_range Ajay Singh
2018-08-02 7:34 ` Greg KH
2018-08-03 8:28 ` Ajay Singh
2018-08-05 14:11 ` Greg KH
2018-08-04 15:37 ` Ajay Singh [this message]
2018-07-29 6:06 ` [PATCH 8/8] staging: wilc1000: added parentheses in macro to avoid checkpatch issue Ajay Singh
2018-08-02 7:34 ` Greg KH
2018-08-02 8:26 ` Ajay Singh
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=20180804210732.7952867a@ajaysk-VirtualBox \
--to=ajay.kathat@microchip.com \
--cc=adham.abozaeid@microchip.com \
--cc=aditya.shankar@microchip.com \
--cc=devel@driverdev.osuosl.org \
--cc=ganesh.krishna@microchip.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-wireless@vger.kernel.org \
--cc=venkateswara.kaja@microchip.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).