Linux-IIO Archive on lore.kernel.org
 help / color / Atom feed
* [BUG] iio: imu: st_lsm6dsx: read error when resuming from suspend
@ 2019-10-07 10:21 Sean Nyekjaer
  2019-10-07 10:34 ` Lorenzo Bianconi
  0 siblings, 1 reply; 3+ messages in thread
From: Sean Nyekjaer @ 2019-10-07 10:21 UTC (permalink / raw)
  To: Lorenzo Bianconi; +Cc: linux-iio

Hi Lorenzo,

I'm seeing this error sometimes when resuming:
st_lsm6dsx_i2c 1-006a: failed to read fifo status (err=-13)

I doesn't matter if it's the ism330 or another wake source.
I have not enabled fifo readings.

I have tried the "[PATCH 00/13] various st_lsm6dsx fixes and missing 
bits​" same results.

The regmap_read in st_lsm6dsx_handler_thread for the event seems to be 
reading something as the event is reported correctly.

Later events are reported correctly...

/Sean

^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: [BUG] iio: imu: st_lsm6dsx: read error when resuming from suspend
  2019-10-07 10:21 [BUG] iio: imu: st_lsm6dsx: read error when resuming from suspend Sean Nyekjaer
@ 2019-10-07 10:34 ` Lorenzo Bianconi
  2019-10-07 10:51   ` Sean Nyekjaer
  0 siblings, 1 reply; 3+ messages in thread
From: Lorenzo Bianconi @ 2019-10-07 10:34 UTC (permalink / raw)
  To: Sean Nyekjaer; +Cc: linux-iio

[-- Attachment #1: Type: text/plain, Size: 809 bytes --]

> Hi Lorenzo,
> 

Hi Sean,

> I'm seeing this error sometimes when resuming:
> st_lsm6dsx_i2c 1-006a: failed to read fifo status (err=-13)

it seems the error is directly reported by regmap/i2c driver you are running,
it is not related to the last series I sent.

> 
> I doesn't matter if it's the ism330 or another wake source.
> I have not enabled fifo readings.
> 
> I have tried the "[PATCH 00/13] various st_lsm6dsx fixes and missing bits​"
> same results.
> 
> The regmap_read in st_lsm6dsx_handler_thread for the event seems to be
> reading something as the event is reported correctly.
> 
> Later events are reported correctly...

So IIUC the system just reports a sporadic error sometimes during resume but it
is able to recover, right?

Regards,
Lorenzo

> 
> /Sean

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]

^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: [BUG] iio: imu: st_lsm6dsx: read error when resuming from suspend
  2019-10-07 10:34 ` Lorenzo Bianconi
@ 2019-10-07 10:51   ` Sean Nyekjaer
  0 siblings, 0 replies; 3+ messages in thread
From: Sean Nyekjaer @ 2019-10-07 10:51 UTC (permalink / raw)
  To: Lorenzo Bianconi; +Cc: linux-iio



On 07/10/2019 12.34, Lorenzo Bianconi wrote:
>> Hi Lorenzo,
>>
> 
> Hi Sean,
> 
>> I'm seeing this error sometimes when resuming:
>> st_lsm6dsx_i2c 1-006a: failed to read fifo status (err=-13)
> 
> it seems the error is directly reported by regmap/i2c driver you are running,
> it is not related to the last series I sent.
> 
No not related :) The same error with or without the series ;)
>>
>> I doesn't matter if it's the ism330 or another wake source.
>> I have not enabled fifo readings.
>>
>> I have tried the "[PATCH 00/13] various st_lsm6dsx fixes and missing bits​"
>> same results.
>>
>> The regmap_read in st_lsm6dsx_handler_thread for the event seems to be
>> reading something as the event is reported correctly.
>>
>> Later events are reported correctly...
> 
> So IIUC the system just reports a sporadic error sometimes during resume but it
> is able to recover, right?
> Yes, it's sporadic and suspend/resume sometimes does this... and we are 
able to recover.
I just find it weird that regmap_read goes well and the next call to 
regmap_bulk_read (st_lsm6dsx_read_locked) gets "permission denied".

So all in all, just a heads up. Maybe we can ignore it for now :)

/Sean

^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, back to index

Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2019-10-07 10:21 [BUG] iio: imu: st_lsm6dsx: read error when resuming from suspend Sean Nyekjaer
2019-10-07 10:34 ` Lorenzo Bianconi
2019-10-07 10:51   ` Sean Nyekjaer

Linux-IIO Archive on lore.kernel.org

Archives are clonable:
	git clone --mirror https://lore.kernel.org/linux-iio/0 linux-iio/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 linux-iio linux-iio/ https://lore.kernel.org/linux-iio \
		linux-iio@vger.kernel.org linux-iio@archiver.kernel.org
	public-inbox-index linux-iio

Example config snippet for mirrors

Newsgroup available over NNTP:
	nntp://nntp.lore.kernel.org/org.kernel.vger.linux-iio


AGPL code for this site: git clone https://public-inbox.org/ public-inbox