From: Andres Salomon <dilinger@queued.net>
To: Jesper Juhl <jj@chaosbits.net>
Cc: linux-kernel@vger.kernel.org,
David Woodhouse <dwmw2@infradead.org>,
Jordan Crouse <jordan@cosmicpenguin.net>,
Chris Ball <cjb@laptop.org>,
Jon Nettleton <jon.nettleton@gmail.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Valentin Rothberg <valentinrothberg@googlemail.com>,
Wolfram Sang <w.sang@pengutronix.de>,
Paul Gortmaker <paul.gortmaker@windriver.com>,
devel@driverdev.osuosl.org
Subject: Re: [PATCH] staging: olpc_dcon.c: checkpatch.pl and style fixups
Date: Sat, 14 Apr 2012 19:26:38 -0700 [thread overview]
Message-ID: <20120414192638.31fa501d@debxo> (raw)
In-Reply-To: <alpine.LNX.2.00.1204150049270.15578@swampdragon.chaosbits.net>
On Sun, 15 Apr 2012 00:53:04 +0200 (CEST)
Jesper Juhl <jj@chaosbits.net> wrote:
> This patch removes the few checkpatch.pl issues that are currently
> reported for this file.
>
> It makes these changes:
>
> 1. Quoted strings that were broken over multiple lines are put on a
> single line for easier grep'ability.
>
> 2. Add missing level to a printk().
>
> 3. A few casts have had their space between the cast and variable
> removed.
>
These first three look fine.
> 4. Two msleep() calls with times <= 20 have been changed to
> usleep_range() calls instead since msleep(<=20) may sleep for 20ms
> (on 100Hz kernels for instance).
> Picking a value for the lower bound of the range was easy, that was
> just the value passed to msleep(). As for picking the upper bound
> of the sleep I just went with two times the lower bound, for no
> other reason than the fact that in both cases that value was <=20ms
> and the end result will in any case be closer to the intention than
> a 20ms sleep.
That msleep(1) was replaced with a longer msleep and fewer dcon_read
attempts in OLPC's XO-1.75 kernel. The msleep(10) should probably be
a shorter usleep (though we'd need to test it). In general, this
stuff was done to work around bugs in the dcon, and the timing of these
bugs appears to differ (probably due to smbus timing) between the
various OLPC platforms - XO-1 (x86 amd geode), XO-1.5 (x86 via), and
XO-1.75 (arm armada 610).
Given that, I'd prefer to leave these alone and figure out the proper
values later (with lots of testing). Mind resubmitting with the
msleep changes removed?
next prev parent reply other threads:[~2012-04-15 2:26 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-14 22:53 Jesper Juhl
2012-04-15 2:26 ` Andres Salomon [this message]
2012-04-15 5:13 ` Jordan Crouse
2012-04-15 21:39 ` Jesper Juhl
2012-04-15 22:07 ` Andres Salomon
2012-04-18 23:30 ` Greg Kroah-Hartman
2012-04-18 23:39 ` Jesper Juhl
2012-04-18 23:30 ` Greg Kroah-Hartman
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=20120414192638.31fa501d@debxo \
--to=dilinger@queued.net \
--cc=cjb@laptop.org \
--cc=devel@driverdev.osuosl.org \
--cc=dwmw2@infradead.org \
--cc=gregkh@linuxfoundation.org \
--cc=jj@chaosbits.net \
--cc=jon.nettleton@gmail.com \
--cc=jordan@cosmicpenguin.net \
--cc=linux-kernel@vger.kernel.org \
--cc=paul.gortmaker@windriver.com \
--cc=valentinrothberg@googlemail.com \
--cc=w.sang@pengutronix.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
Powered by JetHome