From: Joe Perches <joe@perches.com>
To: UlfHansson <ulf.hansson@linaro.org>,
MichaelTurquette <mturquette@baylibre.com>,
StephenBoyd <sboyd@kernel.org>,
"RafaelJ.Wysocki" <rjw@rjwysocki.net>,
VireshKumar <viresh.kumar@linaro.org>,
BenjaminHerrenschmidt <benh@kernel.crashing.org>,
PaulMackerras <paulus@samba.org>,
MichaelEllerman <mpe@ellerman.id.au>,
SakariAilus <sakari.ailus@iki.fi>,
MauroCarvalhoChehab <mchehab@kernel.org>,
SebastianReichel <sre@kernel.org>,
GregKroah-Hartman <gregkh@linuxfoundation.org>,
LiamGirdwood <lgirdwood@gmail.com>,
MarkBrown <broonie@kernel.org>, JaroslavKysela <perex@perex.cz>,
TakashiIwai <tiwai@suse.com>
Cc: devel@driverdev.osuosl.org, alsa-devel@alsa-project.org,
linux-pm@vger.kernel.org, linux-kernel@vger.kernel.org,
linuxppc-dev@lists.ozlabs.org, linux-clk@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-media@vger.kernel.org
Subject: usleep_range without a range
Date: Mon, 12 Feb 2018 14:03:48 -0800 [thread overview]
Message-ID: <1518473028.22190.20.camel@perches.com> (raw)
scheduling can generally be better when these values are
not identical. Perhaps these ranges should be expanded.
$ git grep -P -n "usleep_range\s*\(\s*([\w\.\>\-]+)\s*,\s*\1\s*\)"
drivers/clk/ux500/clk-sysctrl.c:45: usleep_range(clk->enable_delay_us, clk->enable_delay_us);
drivers/cpufreq/pmac64-cpufreq.c:140: usleep_range(1000, 1000);
drivers/cpufreq/pmac64-cpufreq.c:239: usleep_range(10000, 10000); /* should be faster , to fix */
drivers/cpufreq/pmac64-cpufreq.c:284: usleep_range(500, 500);
drivers/media/i2c/smiapp/smiapp-core.c:1228: usleep_range(1000, 1000);
drivers/media/i2c/smiapp/smiapp-core.c:1235: usleep_range(1000, 1000);
drivers/media/i2c/smiapp/smiapp-core.c:1240: usleep_range(sleep, sleep);
drivers/media/i2c/smiapp/smiapp-core.c:1387: usleep_range(5000, 5000);
drivers/media/i2c/smiapp/smiapp-quirk.c:205: usleep_range(2000, 2000);
drivers/media/i2c/smiapp/smiapp-regs.c:279: usleep_range(2000, 2000);
drivers/power/supply/ab8500_fg.c:643: usleep_range(100, 100);
drivers/staging/rtl8192u/r819xU_phy.c:180: usleep_range(1000, 1000);
drivers/staging/rtl8192u/r819xU_phy.c:736: usleep_range(1000, 1000);
drivers/staging/rtl8192u/r819xU_phy.c:740: usleep_range(1000, 1000);
sound/soc/codecs/ab8500-codec.c:1065: usleep_range(AB8500_ANC_SM_DELAY, AB8500_ANC_SM_DELAY);
sound/soc/codecs/ab8500-codec.c:1068: usleep_range(AB8500_ANC_SM_DELAY, AB8500_ANC_SM_DELAY);
_______________________________________________
devel mailing list
devel@linuxdriverproject.org
http://driverdev.linuxdriverproject.org/mailman/listinfo/driverdev-devel
WARNING: multiple messages have this Message-ID (diff)
From: Joe Perches <joe@perches.com>
To: UlfHansson <ulf.hansson@linaro.org>,
MichaelTurquette <mturquette@baylibre.com>,
StephenBoyd <sboyd@kernel.org>,
"RafaelJ.Wysocki" <rjw@rjwysocki.net>,
VireshKumar <viresh.kumar@linaro.org>,
BenjaminHerrenschmidt <benh@kernel.crashing.org>,
PaulMackerras <paulus@samba.org>,
MichaelEllerman <mpe@ellerman.id.au>,
SakariAilus <sakari.ailus@iki.fi>,
MauroCarvalhoChehab <mchehab@kernel.org>,
SebastianReichel <sre@kernel.org>,
GregKroah-Hartman <gregkh@linuxfoundation.org>,
LiamGirdwood <lgirdwood@gmail.com>,
MarkBrown <broonie@kernel.org>, JaroslavKysela <perex@perex.cz>,
TakashiIwai <tiwai@suse.com>
Cc: linux-arm-kernel@lists.infradead.org, linux-clk@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-pm@vger.kernel.org,
linuxppc-dev@lists.ozlabs.org, linux-media@vger.kernel.org,
devel@driverdev.osuosl.org, alsa-devel@alsa-project.org
Subject: usleep_range without a range
Date: Mon, 12 Feb 2018 14:03:48 -0800 [thread overview]
Message-ID: <1518473028.22190.20.camel@perches.com> (raw)
scheduling can generally be better when these values are
not identical. Perhaps these ranges should be expanded.
$ git grep -P -n "usleep_range\s*\(\s*([\w\.\>\-]+)\s*,\s*\1\s*\)"
drivers/clk/ux500/clk-sysctrl.c:45: usleep_range(clk->enable_delay_us, clk->enable_delay_us);
drivers/cpufreq/pmac64-cpufreq.c:140: usleep_range(1000, 1000);
drivers/cpufreq/pmac64-cpufreq.c:239: usleep_range(10000, 10000); /* should be faster , to fix */
drivers/cpufreq/pmac64-cpufreq.c:284: usleep_range(500, 500);
drivers/media/i2c/smiapp/smiapp-core.c:1228: usleep_range(1000, 1000);
drivers/media/i2c/smiapp/smiapp-core.c:1235: usleep_range(1000, 1000);
drivers/media/i2c/smiapp/smiapp-core.c:1240: usleep_range(sleep, sleep);
drivers/media/i2c/smiapp/smiapp-core.c:1387: usleep_range(5000, 5000);
drivers/media/i2c/smiapp/smiapp-quirk.c:205: usleep_range(2000, 2000);
drivers/media/i2c/smiapp/smiapp-regs.c:279: usleep_range(2000, 2000);
drivers/power/supply/ab8500_fg.c:643: usleep_range(100, 100);
drivers/staging/rtl8192u/r819xU_phy.c:180: usleep_range(1000, 1000);
drivers/staging/rtl8192u/r819xU_phy.c:736: usleep_range(1000, 1000);
drivers/staging/rtl8192u/r819xU_phy.c:740: usleep_range(1000, 1000);
sound/soc/codecs/ab8500-codec.c:1065: usleep_range(AB8500_ANC_SM_DELAY, AB8500_ANC_SM_DELAY);
sound/soc/codecs/ab8500-codec.c:1068: usleep_range(AB8500_ANC_SM_DELAY, AB8500_ANC_SM_DELAY);
WARNING: multiple messages have this Message-ID (diff)
From: Joe Perches <joe@perches.com>
To: UlfHansson <ulf.hansson@linaro.org>,
MichaelTurquette <mturquette@baylibre.com>,
StephenBoyd <sboyd@kernel.org>,
"RafaelJ.Wysocki" <rjw@rjwysocki.net>,
VireshKumar <viresh.kumar@linaro.org>,
BenjaminHerrenschmidt <benh@kernel.crashing.org>,
PaulMackerras <paulus@samba.org>,
MichaelEllerman <mpe@ellerman.id.au>,
SakariAilus <sakari.ailus@iki.fi>,
MauroCarvalhoChehab <mchehab@kernel.org>,
SebastianReichel <sre@kernel.org>,
GregKroah-Hartman <gregkh@linuxfoundation.org>,
LiamGirdwood <lgirdwood@gmail.com>,
MarkBrown <broonie@kernel.org>, JaroslavKysela <perex@perex.cz>,
TakashiIwai <tiwai@suse.com>
Cc: linux-arm-kernel@lists.infradead.org, linux-clk@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-pm@vger.kernel.org,
linuxppc-dev@lists.ozlabs.org, linux-media@vger.kernel.org,
devel@driverdev.osuosl.org, alsa-devel@alsa-project.org
Subject: usleep_range without a range
Date: Mon, 12 Feb 2018 14:03:48 -0800 [thread overview]
Message-ID: <1518473028.22190.20.camel@perches.com> (raw)
scheduling can generally be better when these values are
not identical. Perhaps these ranges should be expanded.
$ git grep -P -n "usleep_range\s*\(\s*([\w\.\>\-]+)\s*,\s*\1\s*\)"
drivers/clk/ux500/clk-sysctrl.c:45: usleep_range(clk->enable_delay_us, clk->enable_delay_us);
drivers/cpufreq/pmac64-cpufreq.c:140: usleep_range(1000, 1000);
drivers/cpufreq/pmac64-cpufreq.c:239: usleep_range(10000, 10000); /* should be faster , to fix */
drivers/cpufreq/pmac64-cpufreq.c:284: usleep_range(500, 500);
drivers/media/i2c/smiapp/smiapp-core.c:1228: usleep_range(1000, 1000);
drivers/media/i2c/smiapp/smiapp-core.c:1235: usleep_range(1000, 1000);
drivers/media/i2c/smiapp/smiapp-core.c:1240: usleep_range(sleep, sleep);
drivers/media/i2c/smiapp/smiapp-core.c:1387: usleep_range(5000, 5000);
drivers/media/i2c/smiapp/smiapp-quirk.c:205: usleep_range(2000, 2000);
drivers/media/i2c/smiapp/smiapp-regs.c:279: usleep_range(2000, 2000);
drivers/power/supply/ab8500_fg.c:643: usleep_range(100, 100);
drivers/staging/rtl8192u/r819xU_phy.c:180: usleep_range(1000, 1000);
drivers/staging/rtl8192u/r819xU_phy.c:736: usleep_range(1000, 1000);
drivers/staging/rtl8192u/r819xU_phy.c:740: usleep_range(1000, 1000);
sound/soc/codecs/ab8500-codec.c:1065: usleep_range(AB8500_ANC_SM_DELAY, AB8500_ANC_SM_DELAY);
sound/soc/codecs/ab8500-codec.c:1068: usleep_range(AB8500_ANC_SM_DELAY, AB8500_ANC_SM_DELAY);
WARNING: multiple messages have this Message-ID (diff)
From: Joe Perches <joe@perches.com>
To: UlfHansson <ulf.hansson@linaro.org>,
MichaelTurquette <mturquette@baylibre.com>,
StephenBoyd <sboyd@kernel.org>,
"RafaelJ.Wysocki" <rjw@rjwysocki.net>,
VireshKumar <viresh.kumar@linaro.org>,
BenjaminHerrenschmidt <benh@kernel.crashing.org>,
PaulMackerras <paulus@samba.org>,
MichaelEllerman <mpe@ellerman.id.au>,
SakariAilus <sakari.ailus@iki.fi>,
MauroCarvalhoChehab <mchehab@kernel.org>,
SebastianReichel <sre@kernel.org>,
GregKroah-Hartman <gregkh@linuxfoundation.org>,
LiamGirdwood <lgirdwood@gmail.com>,
MarkBrown <broonie@kernel.org>, JaroslavKysela <perex@perex.cz>,
TakashiIwai <tiwai@suse.com>
Cc: devel@driverdev.osuosl.org, alsa-devel@alsa-project.org,
linux-pm@vger.kernel.org, linux-kernel@vger.kernel.org,
linuxppc-dev@lists.ozlabs.org, linux-clk@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-media@vger.kernel.org
Subject: usleep_range without a range
Date: Mon, 12 Feb 2018 14:03:48 -0800 [thread overview]
Message-ID: <1518473028.22190.20.camel@perches.com> (raw)
scheduling can generally be better when these values are
not identical. Perhaps these ranges should be expanded.
$ git grep -P -n "usleep_range\s*\(\s*([\w\.\>\-]+)\s*,\s*\1\s*\)"
drivers/clk/ux500/clk-sysctrl.c:45: usleep_range(clk->enable_delay_us, clk->enable_delay_us);
drivers/cpufreq/pmac64-cpufreq.c:140: usleep_range(1000, 1000);
drivers/cpufreq/pmac64-cpufreq.c:239: usleep_range(10000, 10000); /* should be faster , to fix */
drivers/cpufreq/pmac64-cpufreq.c:284: usleep_range(500, 500);
drivers/media/i2c/smiapp/smiapp-core.c:1228: usleep_range(1000, 1000);
drivers/media/i2c/smiapp/smiapp-core.c:1235: usleep_range(1000, 1000);
drivers/media/i2c/smiapp/smiapp-core.c:1240: usleep_range(sleep, sleep);
drivers/media/i2c/smiapp/smiapp-core.c:1387: usleep_range(5000, 5000);
drivers/media/i2c/smiapp/smiapp-quirk.c:205: usleep_range(2000, 2000);
drivers/media/i2c/smiapp/smiapp-regs.c:279: usleep_range(2000, 2000);
drivers/power/supply/ab8500_fg.c:643: usleep_range(100, 100);
drivers/staging/rtl8192u/r819xU_phy.c:180: usleep_range(1000, 1000);
drivers/staging/rtl8192u/r819xU_phy.c:736: usleep_range(1000, 1000);
drivers/staging/rtl8192u/r819xU_phy.c:740: usleep_range(1000, 1000);
sound/soc/codecs/ab8500-codec.c:1065: usleep_range(AB8500_ANC_SM_DELAY, AB8500_ANC_SM_DELAY);
sound/soc/codecs/ab8500-codec.c:1068: usleep_range(AB8500_ANC_SM_DELAY, AB8500_ANC_SM_DELAY);
WARNING: multiple messages have this Message-ID (diff)
From: joe@perches.com (Joe Perches)
To: linux-arm-kernel@lists.infradead.org
Subject: usleep_range without a range
Date: Mon, 12 Feb 2018 14:03:48 -0800 [thread overview]
Message-ID: <1518473028.22190.20.camel@perches.com> (raw)
scheduling can generally be better when these values are
not identical. Perhaps these ranges should be expanded.
$ git grep -P -n "usleep_range\s*\(\s*([\w\.\>\-]+)\s*,\s*\1\s*\)"
drivers/clk/ux500/clk-sysctrl.c:45: usleep_range(clk->enable_delay_us, clk->enable_delay_us);
drivers/cpufreq/pmac64-cpufreq.c:140: usleep_range(1000, 1000);
drivers/cpufreq/pmac64-cpufreq.c:239: usleep_range(10000, 10000); /* should be faster , to fix */
drivers/cpufreq/pmac64-cpufreq.c:284: usleep_range(500, 500);
drivers/media/i2c/smiapp/smiapp-core.c:1228: usleep_range(1000, 1000);
drivers/media/i2c/smiapp/smiapp-core.c:1235: usleep_range(1000, 1000);
drivers/media/i2c/smiapp/smiapp-core.c:1240: usleep_range(sleep, sleep);
drivers/media/i2c/smiapp/smiapp-core.c:1387: usleep_range(5000, 5000);
drivers/media/i2c/smiapp/smiapp-quirk.c:205: usleep_range(2000, 2000);
drivers/media/i2c/smiapp/smiapp-regs.c:279: usleep_range(2000, 2000);
drivers/power/supply/ab8500_fg.c:643: usleep_range(100, 100);
drivers/staging/rtl8192u/r819xU_phy.c:180: usleep_range(1000, 1000);
drivers/staging/rtl8192u/r819xU_phy.c:736: usleep_range(1000, 1000);
drivers/staging/rtl8192u/r819xU_phy.c:740: usleep_range(1000, 1000);
sound/soc/codecs/ab8500-codec.c:1065: usleep_range(AB8500_ANC_SM_DELAY, AB8500_ANC_SM_DELAY);
sound/soc/codecs/ab8500-codec.c:1068: usleep_range(AB8500_ANC_SM_DELAY, AB8500_ANC_SM_DELAY);
next reply other threads:[~2018-02-12 22:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-12 22:03 Joe Perches [this message]
2018-02-12 22:03 ` usleep_range without a range Joe Perches
2018-02-12 22:03 ` Joe Perches
2018-02-12 22:03 ` Joe Perches
2018-02-12 22:03 ` Joe Perches
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=1518473028.22190.20.camel@perches.com \
--to=joe@perches.com \
--cc=alsa-devel@alsa-project.org \
--cc=benh@kernel.crashing.org \
--cc=broonie@kernel.org \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@linuxfoundation.org \
--cc=lgirdwood@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mchehab@kernel.org \
--cc=mpe@ellerman.id.au \
--cc=mturquette@baylibre.com \
--cc=paulus@samba.org \
--cc=perex@perex.cz \
--cc=rjw@rjwysocki.net \
--cc=sakari.ailus@iki.fi \
--cc=sboyd@kernel.org \
--cc=sre@kernel.org \
--cc=tiwai@suse.com \
--cc=ulf.hansson@linaro.org \
--cc=viresh.kumar@linaro.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.