From: Jonathan Cameron <jic23-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
To: Marcin Niestroj <m.niestroj-z3quKL4iOrmQ6ZAhV5LmOA@public.gmane.org>
Cc: Peter Meerwald-Stadler
<pmeerw-jW+XmwGofnusTnJN9+BGXg@public.gmane.org>,
Hartmut Knaack <knaack.h-Mmb7MZpHnFY@public.gmane.org>,
Lars-Peter Clausen <lars-Qo5EllUWu/uELgA04lAiVw@public.gmane.org>,
Daniel Baluta
<daniel.baluta-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>,
Gregor Boirie
<gregor.boirie-ITF29qwbsa/QT0dZR+AlfA@public.gmane.org>,
Sanchayan Maity
<maitysanchayan-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
Rob Herring <robh+dt-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>,
Mark Rutland <mark.rutland-5wv7dgnIgG8@public.gmane.org>,
linux-iio-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH v2 5/6] iio: bmi160: Fix time needed to sleep after command execution
Date: Fri, 30 Dec 2016 10:51:53 +0000 [thread overview]
Message-ID: <275616b9-bd6e-2bbe-2e49-f20a6bdc9b1c@kernel.org> (raw)
In-Reply-To: <7668f191-dafd-e616-171a-cafc52791292-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
On 30/12/16 10:49, Jonathan Cameron wrote:
> On 08/12/16 14:22, Marcin Niestroj wrote:
>> Datasheet specifies typical and maximum execution times for which CMD
>> register is occupied after previous command execution. We took these
>> values as minimum and maximum time for usleep_range() call before making
>> a new command execution.
>>
>> To be sure, that the CMD register is no longer occupied we need to wait
>> *at least* the maximum time specified by datasheet.
>>
>> Signed-off-by: Marcin Niestroj <m.niestroj-z3quKL4iOrmQ6ZAhV5LmOA@public.gmane.org>
> This looks like a definite bug that we would want to fix in stable as well.
> If possible, could you ensure this is the first patch in the updated series?
Actually don't worry. It applies cleanly to my fixes-togreg-post-rc1 branch anyway
so I'll take it that way and send upstream asap.
Applied to the fixes-togreg-post-rc1 branch and marked for stable.
Thanks,
Jonathan
>
> Thanks,
>
> Jonathan
>> ---
>> Patch introduced in v2
>>
>> drivers/iio/imu/bmi160/bmi160_core.c | 25 ++++++-------------------
>> 1 file changed, 6 insertions(+), 19 deletions(-)
>>
>> diff --git a/drivers/iio/imu/bmi160/bmi160_core.c b/drivers/iio/imu/bmi160/bmi160_core.c
>> index 095533c..88bcf3f 100644
>> --- a/drivers/iio/imu/bmi160/bmi160_core.c
>> +++ b/drivers/iio/imu/bmi160/bmi160_core.c
>> @@ -67,10 +67,8 @@
>>
>> #define BMI160_REG_DUMMY 0x7F
>>
>> -#define BMI160_ACCEL_PMU_MIN_USLEEP 3200
>> -#define BMI160_ACCEL_PMU_MAX_USLEEP 3800
>> -#define BMI160_GYRO_PMU_MIN_USLEEP 55000
>> -#define BMI160_GYRO_PMU_MAX_USLEEP 80000
>> +#define BMI160_ACCEL_PMU_MIN_USLEEP 3800
>> +#define BMI160_GYRO_PMU_MIN_USLEEP 80000
>> #define BMI160_SOFTRESET_USLEEP 1000
>>
>> #define BMI160_CHANNEL(_type, _axis, _index) { \
>> @@ -153,20 +151,9 @@ static struct bmi160_regs bmi160_regs[] = {
>> },
>> };
>>
>> -struct bmi160_pmu_time {
>> - unsigned long min;
>> - unsigned long max;
>> -};
>> -
>> -static struct bmi160_pmu_time bmi160_pmu_time[] = {
>> - [BMI160_ACCEL] = {
>> - .min = BMI160_ACCEL_PMU_MIN_USLEEP,
>> - .max = BMI160_ACCEL_PMU_MAX_USLEEP
>> - },
>> - [BMI160_GYRO] = {
>> - .min = BMI160_GYRO_PMU_MIN_USLEEP,
>> - .max = BMI160_GYRO_PMU_MIN_USLEEP,
>> - },
>> +static unsigned long bmi160_pmu_time[] = {
>> + [BMI160_ACCEL] = BMI160_ACCEL_PMU_MIN_USLEEP,
>> + [BMI160_GYRO] = BMI160_GYRO_PMU_MIN_USLEEP,
>> };
>>
>> struct bmi160_scale {
>> @@ -293,7 +280,7 @@ int bmi160_set_mode(struct bmi160_data *data, enum bmi160_sensor_type t,
>> if (ret < 0)
>> return ret;
>>
>> - usleep_range(bmi160_pmu_time[t].min, bmi160_pmu_time[t].max);
>> + usleep_range(bmi160_pmu_time[t], bmi160_pmu_time[t] + 1000);
>>
>> return 0;
>> }
>>
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-iio" in
> the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
next prev parent reply other threads:[~2016-12-30 10:51 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-08 14:22 [PATCH v2 0/6] iio: bmi160: cleanups and hardware fifo support Marcin Niestroj
[not found] ` <20161208142259.26230-1-m.niestroj-z3quKL4iOrmQ6ZAhV5LmOA@public.gmane.org>
2016-12-08 14:22 ` [PATCH v2 1/6] iio: bmi160: Add of device table for i2c Marcin Niestroj
[not found] ` <20161208142259.26230-2-m.niestroj-z3quKL4iOrmQ6ZAhV5LmOA@public.gmane.org>
2016-12-30 10:47 ` Jonathan Cameron
2016-12-08 14:22 ` [PATCH v2 2/6] iio: bmi160: Add of device table for spi Marcin Niestroj
2016-12-08 14:22 ` [PATCH v2 3/6] Documentation: DT: Add bmi160 imu binding Marcin Niestroj
[not found] ` <20161208142259.26230-4-m.niestroj-z3quKL4iOrmQ6ZAhV5LmOA@public.gmane.org>
2016-12-12 17:15 ` Rob Herring
2016-12-30 10:40 ` Jonathan Cameron
2016-12-08 14:22 ` [PATCH v2 4/6] iio: bmi160: Protect data transmission with mutex Marcin Niestroj
[not found] ` <20161208142259.26230-5-m.niestroj-z3quKL4iOrmQ6ZAhV5LmOA@public.gmane.org>
2016-12-30 10:47 ` Jonathan Cameron
2016-12-08 14:22 ` [PATCH v2 5/6] iio: bmi160: Fix time needed to sleep after command execution Marcin Niestroj
[not found] ` <20161208142259.26230-6-m.niestroj-z3quKL4iOrmQ6ZAhV5LmOA@public.gmane.org>
2016-12-30 10:49 ` Jonathan Cameron
[not found] ` <7668f191-dafd-e616-171a-cafc52791292-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
2016-12-30 10:51 ` Jonathan Cameron [this message]
2016-12-08 14:22 ` [PATCH v2 6/6] iio: bmi160: Support hardware fifo Marcin Niestroj
[not found] ` <20161208142259.26230-7-m.niestroj-z3quKL4iOrmQ6ZAhV5LmOA@public.gmane.org>
2016-12-30 11:29 ` Jonathan Cameron
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=275616b9-bd6e-2bbe-2e49-f20a6bdc9b1c@kernel.org \
--to=jic23-dgejt+ai2ygdnm+yrofe0a@public.gmane.org \
--cc=daniel.baluta-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org \
--cc=devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=gregor.boirie-ITF29qwbsa/QT0dZR+AlfA@public.gmane.org \
--cc=knaack.h-Mmb7MZpHnFY@public.gmane.org \
--cc=lars-Qo5EllUWu/uELgA04lAiVw@public.gmane.org \
--cc=linux-iio-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=m.niestroj-z3quKL4iOrmQ6ZAhV5LmOA@public.gmane.org \
--cc=maitysanchayan-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
--cc=mark.rutland-5wv7dgnIgG8@public.gmane.org \
--cc=pmeerw-jW+XmwGofnusTnJN9+BGXg@public.gmane.org \
--cc=robh+dt-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.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;
as well as URLs for NNTP newsgroup(s).