From: Guenter Roeck <linux@roeck-us.net>
To: Parag Warudkar <parag.lkml@gmail.com>
Cc: lm-sensors@lm-sensors.org, linux-kernel@vger.kernel.org,
rydberg@euromail.se, khali@linux-fr.org
Subject: Re: [PATCH] applesmc: Bump max wait and rearrange udelay
Date: Sat, 15 Sep 2012 21:31:16 -0700 [thread overview]
Message-ID: <20120916043116.GA4477@roeck-us.net> (raw)
In-Reply-To: <alpine.DEB.2.02.1209152323490.2088@ubuntu>
On Sat, Sep 15, 2012 at 11:29:58PM -0400, Parag Warudkar wrote:
>
>
> On Sat, 15 Sep 2012, Parag Warudkar wrote:
>
> >
> >
> > On Sat, 15 Sep 2012, Guenter Roeck wrote:
> > >
> > > Also, since the delay time can get quite large, would it make sense to replace
> > > udelay with usleep_range() ?
> > >
> >
> > Yes, I think that would be a good thing to do. We could sleep in range of
> > us<<=1 and us<<1 and if usleep_range() returns actual sleep time we can
> > factor that in for next loop iteration if necessary. Gotta think a bit on
> > that one.
> >
> > I will rework the patch to fix the loop termination and keep the bump to
> > 0x10000 in place and possibly also experiment with usleep_range().
> >
>
> Below is what I am experimenting with right now. I chose to keep the
> APPLESMC_MAX_WAIT to current 0x8000 (32ms). With the fixed loop
> termination and use of usleep_range() instead of udelay - I will try to
> run this a couple days and see if I can recreate the failure within 32ms.
>
> Does this look ok? (I haven't yet changed send_byte to use usleep_range -
> if this approach looks ok I can change that as well.)
>
> Signed-off-by: Parag Warudkar <parag.lkml@gmail.com>
>
> diff --git a/drivers/hwmon/applesmc.c b/drivers/hwmon/applesmc.c
> index 2827088..6610037 100644
> --- a/drivers/hwmon/applesmc.c
> +++ b/drivers/hwmon/applesmc.c
> @@ -168,15 +168,20 @@ static struct workqueue_struct *applesmc_led_wq;
> static int wait_read(void)
> {
> u8 status;
> - int us;
> - for (us = APPLESMC_MIN_WAIT; us < APPLESMC_MAX_WAIT; us <<= 1) {
> - udelay(us);
> + unsigned long r1_us = APPLESMC_MIN_WAIT;
> + unsigned long r2_us;
> + do {
> status = inb(APPLESMC_CMD_PORT);
> /* read: wait for smc to settle */
> if (status & 0x01)
> return 0;
> - }
> -
> + r2_us = r1_us << 2;
> + if (r2_us > APPLESMC_MAX_WAIT)
> + goto fail;
> + usleep_range(r1_us, r2_us);
> + r1_us = r2_us;
That looks terribly complicated. Better keep the loop, and just replace
udelay(us);
with something like
usleep_range(us, us << 1);
Alternatively, just use a constant such as
usleep_range(us, us + APPLESMC_MIN_WAIT);
Guenter
next prev parent reply other threads:[~2012-09-16 4:31 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-15 22:42 [PATCH] applesmc: Bump max wait and rearrange udelay Parag Warudkar
2012-09-15 22:58 ` Guenter Roeck
2012-09-15 23:35 ` Parag Warudkar
2012-09-15 23:38 ` Parag Warudkar
2012-09-16 3:29 ` Parag Warudkar
2012-09-16 4:31 ` Guenter Roeck [this message]
2012-09-16 9:35 ` Henrik Rydberg
2012-09-16 21:22 ` Parag Warudkar
2012-09-16 22:00 ` Guenter Roeck
2012-09-16 22:30 ` Henrik Rydberg
2012-09-17 0:11 ` Parag Warudkar
2012-09-17 16:27 ` Henrik Rydberg
2012-09-17 16:37 ` Guenter Roeck
2012-09-17 20:14 ` Henrik Rydberg
2012-09-17 22:03 ` Guenter Roeck
2012-09-17 18:06 ` Parag Warudkar
2012-09-17 18:49 ` Henrik Rydberg
2012-09-17 18:54 ` Parag Warudkar
2012-09-17 19:14 ` Henrik Rydberg
2012-09-17 19:46 ` Henrik Rydberg
2012-09-17 18:22 ` Parag Warudkar
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=20120916043116.GA4477@roeck-us.net \
--to=linux@roeck-us.net \
--cc=khali@linux-fr.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lm-sensors@lm-sensors.org \
--cc=parag.lkml@gmail.com \
--cc=rydberg@euromail.se \
/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