On Sat, Dec 3, 2016 at 2:30 PM, Jonathan Cameron wrote:
> On 02/12/16 19:07, Aniroop Mathur wrote:
>> On Wed, Nov 30, 2016 at 8:13 PM, Aniroop Mathur wrote:
>>> On 30 Nov 2016 19:05, "Lars-Peter Clausen" wrote:
>>> >
>>> > On 11/27/2016
On Sat, Dec 3, 2016 at 2:30 PM, Jonathan Cameron wrote:
> On 02/12/16 19:07, Aniroop Mathur wrote:
>> On Wed, Nov 30, 2016 at 8:13 PM, Aniroop Mathur wrote:
>>> On 30 Nov 2016 19:05, "Lars-Peter Clausen" wrote:
>>> >
>>> > On 11/27/2016 11:51 AM, Jonathan Cameron wrote:
>>> > > On 26/11/16
On 02/12/16 19:07, Aniroop Mathur wrote:
> On Wed, Nov 30, 2016 at 8:13 PM, Aniroop Mathur wrote:
>> On 30 Nov 2016 19:05, "Lars-Peter Clausen" wrote:
>> >
>> > On 11/27/2016 11:51 AM, Jonathan Cameron wrote:
>> > > On 26/11/16 03:47, Aniroop Mathur
On 02/12/16 19:07, Aniroop Mathur wrote:
> On Wed, Nov 30, 2016 at 8:13 PM, Aniroop Mathur wrote:
>> On 30 Nov 2016 19:05, "Lars-Peter Clausen" wrote:
>> >
>> > On 11/27/2016 11:51 AM, Jonathan Cameron wrote:
>> > > On 26/11/16 03:47, Aniroop Mathur wrote:
>> > >> msleep(1~20) may not do
On Wed, Nov 30, 2016 at 8:13 PM, Aniroop Mathur wrote:
> On 30 Nov 2016 19:05, "Lars-Peter Clausen" wrote:
> >
> > On 11/27/2016 11:51 AM, Jonathan Cameron wrote:
> > > On 26/11/16 03:47, Aniroop Mathur wrote:
> > >> msleep(1~20) may not do what the
On Wed, Nov 30, 2016 at 8:13 PM, Aniroop Mathur wrote:
> On 30 Nov 2016 19:05, "Lars-Peter Clausen" wrote:
> >
> > On 11/27/2016 11:51 AM, Jonathan Cameron wrote:
> > > On 26/11/16 03:47, Aniroop Mathur wrote:
> > >> msleep(1~20) may not do what the caller intends, and will often sleep
>
On Wed, Nov 30, 2016 at 5:49 PM, Linus Walleij wrote:
> On Sun, Nov 27, 2016 at 11:51 AM, Jonathan Cameron wrote:
>> On 26/11/16 03:47, Aniroop Mathur wrote:
>
> [bmp280.c]
>
>>> /* Wait to make sure we started up properly */
>>> -
On Wed, Nov 30, 2016 at 5:49 PM, Linus Walleij wrote:
> On Sun, Nov 27, 2016 at 11:51 AM, Jonathan Cameron wrote:
>> On 26/11/16 03:47, Aniroop Mathur wrote:
>
> [bmp280.c]
>
>>> /* Wait to make sure we started up properly */
>>> - mdelay(data->start_up_time);
>>> +
On 30 Nov 2016 19:05, "Lars-Peter Clausen" wrote:
>
> On 11/27/2016 11:51 AM, Jonathan Cameron wrote:
> > On 26/11/16 03:47, Aniroop Mathur wrote:
> >> msleep(1~20) may not do what the caller intends, and will often sleep
> >> longer.
> >> (~20 ms actual sleep for any
On 30 Nov 2016 19:05, "Lars-Peter Clausen" wrote:
>
> On 11/27/2016 11:51 AM, Jonathan Cameron wrote:
> > On 26/11/16 03:47, Aniroop Mathur wrote:
> >> msleep(1~20) may not do what the caller intends, and will often sleep
> >> longer.
> >> (~20 ms actual sleep for any value given in the
On 11/27/2016 11:51 AM, Jonathan Cameron wrote:
> On 26/11/16 03:47, Aniroop Mathur wrote:
>> msleep(1~20) may not do what the caller intends, and will often sleep longer.
>> (~20 ms actual sleep for any value given in the 1~20ms range)
>> This is not the desired behaviour for many cases like
On 11/27/2016 11:51 AM, Jonathan Cameron wrote:
> On 26/11/16 03:47, Aniroop Mathur wrote:
>> msleep(1~20) may not do what the caller intends, and will often sleep longer.
>> (~20 ms actual sleep for any value given in the 1~20ms range)
>> This is not the desired behaviour for many cases like
On Sun, Nov 27, 2016 at 11:51 AM, Jonathan Cameron wrote:
> On 26/11/16 03:47, Aniroop Mathur wrote:
[bmp280.c]
>> /* Wait to make sure we started up properly */
>> - mdelay(data->start_up_time);
>> + usleep_range(data->start_up_time, data->start_up_time + 100);
On Sun, Nov 27, 2016 at 11:51 AM, Jonathan Cameron wrote:
> On 26/11/16 03:47, Aniroop Mathur wrote:
[bmp280.c]
>> /* Wait to make sure we started up properly */
>> - mdelay(data->start_up_time);
>> + usleep_range(data->start_up_time, data->start_up_time + 100);
>
> As this in
On 26/11/16 03:47, Aniroop Mathur wrote:
> msleep(1~20) may not do what the caller intends, and will often sleep longer.
> (~20 ms actual sleep for any value given in the 1~20ms range)
> This is not the desired behaviour for many cases like device resume time,
> device suspend time, device enable
On 26/11/16 03:47, Aniroop Mathur wrote:
> msleep(1~20) may not do what the caller intends, and will often sleep longer.
> (~20 ms actual sleep for any value given in the 1~20ms range)
> This is not the desired behaviour for many cases like device resume time,
> device suspend time, device enable
msleep(1~20) may not do what the caller intends, and will often sleep longer.
(~20 ms actual sleep for any value given in the 1~20ms range)
This is not the desired behaviour for many cases like device resume time,
device suspend time, device enable time, data reading time, etc.
Thus, change msleep
msleep(1~20) may not do what the caller intends, and will often sleep longer.
(~20 ms actual sleep for any value given in the 1~20ms range)
This is not the desired behaviour for many cases like device resume time,
device suspend time, device enable time, data reading time, etc.
Thus, change msleep
18 matches
Mail list logo