From: Hans de Goede <hdegoede@redhat.com>
To: Nicholas Mc Guire <hofrat@osadl.org>,
Dmitry Torokhov <dmitry.torokhov@gmail.com>
Cc: Henrik Rydberg <rydberg@bitmath.org>,
Rob Herring <robh@kernel.org>, Daniel Jansen <djaniboe@gmail.com>,
Dan Carpenter <dan.carpenter@oracle.com>,
Robert Dolca <robert.dolca@intel.com>,
linux-input@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Input: silead: use msleep() for long delays
Date: Thu, 12 Jan 2017 18:46:54 +0100 [thread overview]
Message-ID: <a5d2b275-0418-280f-3cb9-516ef510a05c@redhat.com> (raw)
In-Reply-To: <1484238105-10785-1-git-send-email-hofrat@osadl.org>
Hi,
On 01/12/2017 05:21 PM, Nicholas Mc Guire wrote:
> the delays here are in the 10 to 20ms range so msleep() will do - no
> need to burden the highres timer subsystem.
>
> Signed-off-by: Nicholas Mc Guire <hofrat@osadl.org>
> ---
>
> Problem found by coccinelle script
>
> While msleep(10) has a worst case uncertainty of 10ms (on HZ=100 systems)
> this seems ok here as the delays are not called frequently (init and
> reset functions)
By the same logic, this is not much of a burden on the high-res timer
subsys though.
> and the uncertainty of 10ms fits the permitted range of
> the original usleep_ranges().
Either way this patch is fine with me.
Regards,
Hans
>
> Patch was compile tested with: x86_64_defconfig +
> CONFIG_TOUCHSCREEN_SILEAD=m
>
> Patch is against 4.10-rc3 (localversion-next is next-20170112)
>
> drivers/input/touchscreen/silead.c | 17 ++++++++---------
> 1 file changed, 8 insertions(+), 9 deletions(-)
>
> diff --git a/drivers/input/touchscreen/silead.c b/drivers/input/touchscreen/silead.c
> index 404830a..3aa885c 100644
> --- a/drivers/input/touchscreen/silead.c
> +++ b/drivers/input/touchscreen/silead.c
> @@ -58,8 +58,7 @@
> #define SILEAD_POINT_X_MSB_OFF 0x03
> #define SILEAD_TOUCH_ID_MASK 0xF0
>
> -#define SILEAD_CMD_SLEEP_MIN 10000
> -#define SILEAD_CMD_SLEEP_MAX 20000
> +#define SILEAD_CMD_SLEEP_MIN 10 /* 10+ ms */
> #define SILEAD_POWER_SLEEP 20
> #define SILEAD_STARTUP_SLEEP 30
>
> @@ -190,25 +189,25 @@ static int silead_ts_init(struct i2c_client *client)
> SILEAD_CMD_RESET);
> if (error)
> goto i2c_write_err;
> - usleep_range(SILEAD_CMD_SLEEP_MIN, SILEAD_CMD_SLEEP_MAX);
> + msleep(SILEAD_CMD_SLEEP_MIN);
>
> error = i2c_smbus_write_byte_data(client, SILEAD_REG_TOUCH_NR,
> data->max_fingers);
> if (error)
> goto i2c_write_err;
> - usleep_range(SILEAD_CMD_SLEEP_MIN, SILEAD_CMD_SLEEP_MAX);
> + msleep(SILEAD_CMD_SLEEP_MIN);
>
> error = i2c_smbus_write_byte_data(client, SILEAD_REG_CLOCK,
> SILEAD_CLOCK);
> if (error)
> goto i2c_write_err;
> - usleep_range(SILEAD_CMD_SLEEP_MIN, SILEAD_CMD_SLEEP_MAX);
> + msleep(SILEAD_CMD_SLEEP_MIN);
>
> error = i2c_smbus_write_byte_data(client, SILEAD_REG_RESET,
> SILEAD_CMD_START);
> if (error)
> goto i2c_write_err;
> - usleep_range(SILEAD_CMD_SLEEP_MIN, SILEAD_CMD_SLEEP_MAX);
> + msleep(SILEAD_CMD_SLEEP_MIN);
>
> return 0;
>
> @@ -225,19 +224,19 @@ static int silead_ts_reset(struct i2c_client *client)
> SILEAD_CMD_RESET);
> if (error)
> goto i2c_write_err;
> - usleep_range(SILEAD_CMD_SLEEP_MIN, SILEAD_CMD_SLEEP_MAX);
> + msleep(SILEAD_CMD_SLEEP_MIN);
>
> error = i2c_smbus_write_byte_data(client, SILEAD_REG_CLOCK,
> SILEAD_CLOCK);
> if (error)
> goto i2c_write_err;
> - usleep_range(SILEAD_CMD_SLEEP_MIN, SILEAD_CMD_SLEEP_MAX);
> + msleep(SILEAD_CMD_SLEEP_MIN);
>
> error = i2c_smbus_write_byte_data(client, SILEAD_REG_POWER,
> SILEAD_CMD_START);
> if (error)
> goto i2c_write_err;
> - usleep_range(SILEAD_CMD_SLEEP_MIN, SILEAD_CMD_SLEEP_MAX);
> + msleep(SILEAD_CMD_SLEEP_MIN);
>
> return 0;
>
>
next prev parent reply other threads:[~2017-01-12 17:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-12 16:21 Nicholas Mc Guire
2017-01-12 17:46 ` Hans de Goede [this message]
2017-01-12 18:10 ` Dmitry Torokhov
2017-01-12 18:50 ` Nicholas Mc Guire
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=a5d2b275-0418-280f-3cb9-516ef510a05c@redhat.com \
--to=hdegoede@redhat.com \
--cc=dan.carpenter@oracle.com \
--cc=djaniboe@gmail.com \
--cc=dmitry.torokhov@gmail.com \
--cc=hofrat@osadl.org \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robert.dolca@intel.com \
--cc=robh@kernel.org \
--cc=rydberg@bitmath.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®