<feed xmlns='http://www.w3.org/2005/Atom'>
<title>kernel.git/drivers/iio/imu, branch linux-5.7.y</title>
<subtitle>Hosts the 0x221E linux distro kernel.
</subtitle>
<id>https://git.0xinfinity.dev/distro/kernel.git/atom?h=linux-5.7.y</id>
<link rel='self' href='https://git.0xinfinity.dev/distro/kernel.git/atom?h=linux-5.7.y'/>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/'/>
<updated>2020-08-21T11:07:23Z</updated>
<entry>
<title>iio: imu: st_lsm6dsx: reset hw ts after resume</title>
<updated>2020-08-21T11:07:23Z</updated>
<author>
<name>Lorenzo Bianconi</name>
</author>
<published>2020-07-13T11:40:19Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=d7ccfcd8445971bd2fce1ee2b8ba4e566e76754a'/>
<id>urn:sha1:d7ccfcd8445971bd2fce1ee2b8ba4e566e76754a</id>
<content type='text'>
commit a1bab9396c2d98c601ce81c27567159dfbc10c19 upstream.

Reset hw time samples generator after system resume in order to avoid
disalignment between system and device time reference since FIFO
batching and time samples generator are disabled during suspend.

Fixes: 213451076bd3 ("iio: imu: st_lsm6dsx: add hw timestamp support")
Tested-by: Sean Nyekjaer &lt;sean@geanix.com&gt;
Signed-off-by: Lorenzo Bianconi &lt;lorenzo@kernel.org&gt;
Cc: &lt;Stable@vger.kernel.org&gt;
Signed-off-by: Jonathan Cameron &lt;Jonathan.Cameron@huawei.com&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;

</content>
</entry>
<entry>
<title>iio: imu: st_lsm6dsx: unlock on error in st_lsm6dsx_shub_write_raw()</title>
<updated>2020-04-25T17:33:54Z</updated>
<author>
<name>Dan Carpenter</name>
</author>
<published>2020-04-22T09:38:11Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=115c215a7e5753ddf982c8760ce7904dd3fbb8ae'/>
<id>urn:sha1:115c215a7e5753ddf982c8760ce7904dd3fbb8ae</id>
<content type='text'>
We need to release a lock if st_lsm6dsx_check_odr() fails, we can't
return directly.

Fixes: 76551a3c3df1 ("iio: imu: st_lsm6dsx: specify slave odr in slv_odr")
Signed-off-by: Dan Carpenter &lt;dan.carpenter@oracle.com&gt;
Signed-off-by: Jonathan Cameron &lt;Jonathan.Cameron@huawei.com&gt;
</content>
</entry>
<entry>
<title>iio: imu: inv_mpu6050: fix suspend/resume with runtime power</title>
<updated>2020-04-19T16:50:02Z</updated>
<author>
<name>Jean-Baptiste Maneyrol</name>
</author>
<published>2020-03-31T13:38:50Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=0a2bf9200aeaa8c1dd23ec65af30af3643ace887'/>
<id>urn:sha1:0a2bf9200aeaa8c1dd23ec65af30af3643ace887</id>
<content type='text'>
Suspend/resume were not working correctly with pm runtime.
Now suspend check if the chip is already suspended, and
resume put runtime pm in the correct state.

Issues seen prior to this were:

When entering suspend, there was an error in logs because we
were disabling vddio regulator although it was already disabled.
And when resuming, the chip was pull back to full power but the
pm_runtime state was not updated. So it was believing it was
still suspended.

Fixes: 4599cac84614 ("iio: imu: inv_mpu6050: use runtime pm with autosuspend")
Signed-off-by: Jean-Baptiste Maneyrol &lt;jmaneyrol@invensense.com&gt;
Signed-off-by: Jonathan Cameron &lt;Jonathan.Cameron@huawei.com&gt;
</content>
</entry>
<entry>
<title>iio: imu: st_lsm6dsx: flush hw FIFO before resetting the device</title>
<updated>2020-04-19T16:50:01Z</updated>
<author>
<name>Lorenzo Bianconi</name>
</author>
<published>2020-03-13T18:06:00Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=3a63da26db0a864134f023f088d41deacd509997'/>
<id>urn:sha1:3a63da26db0a864134f023f088d41deacd509997</id>
<content type='text'>
flush hw FIFO before device reset in order to avoid possible races
on interrupt line 1. If the first interrupt line is asserted during
hw reset the device will work in I3C-only mode (if it is supported)

Fixes: 801a6e0af0c6 ("iio: imu: st_lsm6dsx: add support to LSM6DSO")
Fixes: 43901008fde0 ("iio: imu: st_lsm6dsx: add support to LSM6DSR")
Reported-by: Mario Tesi &lt;mario.tesi@st.com&gt;
Signed-off-by: Lorenzo Bianconi &lt;lorenzo@kernel.org&gt;
Reviewed-by: Vitor Soares &lt;vitor.soares@synopsys.com&gt;
Tested-by: Vitor Soares &lt;vitor.soares@synopsys.com&gt;
Cc: &lt;Stable@vger.kernel.org&gt;
Signed-off-by: Jonathan Cameron &lt;Jonathan.Cameron@huawei.com&gt;
</content>
</entry>
<entry>
<title>iio: imu: st_lsm6dsx: specify slave odr in slv_odr</title>
<updated>2020-03-28T16:35:03Z</updated>
<author>
<name>Lorenzo Bianconi</name>
</author>
<published>2020-03-13T17:54:42Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=76551a3c3df151750a842b003c6899e9c62e0fd2'/>
<id>urn:sha1:76551a3c3df151750a842b003c6899e9c62e0fd2</id>
<content type='text'>
Introduce slv_odr in ext_info data structure in order to distinguish
between sensor hub trigger (accel sensor) odr and i2c slave odr and
properly compute samples in FIFO pattern

Fixes: e485e2a2cfd6 ("iio: imu: st_lsm6dsx: enable sensor-hub support for lsm6dsm")
Signed-off-by: Lorenzo Bianconi &lt;lorenzo@kernel.org&gt;
Signed-off-by: Jonathan Cameron &lt;Jonathan.Cameron@huawei.com&gt;
</content>
</entry>
<entry>
<title>iio: imu: st_lsm6dsx: fix read misalignment on untagged FIFO</title>
<updated>2020-03-28T16:35:02Z</updated>
<author>
<name>Lorenzo Bianconi</name>
</author>
<published>2020-03-13T17:54:41Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=7762902c89c4c78d32ec562f1ada44d02039104b'/>
<id>urn:sha1:7762902c89c4c78d32ec562f1ada44d02039104b</id>
<content type='text'>
st_lsm6dsx suffers of a read misalignment on untagged FIFO when
all 3 supported sensors (accel, gyro and ext device) are running
at different ODRs (the use-case is reported in the LSM6DSM Application
Note at pag 100).
Fix the issue taking into account decimation factor reading the FIFO
pattern.

Fixes: e485e2a2cfd6 ("iio: imu: st_lsm6dsx: enable sensor-hub support for lsm6dsm")
Signed-off-by: Lorenzo Bianconi &lt;lorenzo@kernel.org&gt;
Signed-off-by: Jonathan Cameron &lt;Jonathan.Cameron@huawei.com&gt;
</content>
</entry>
<entry>
<title>iio: imu: adis_buffer: Use new structure for SPI transfer delays</title>
<updated>2020-03-08T17:28:45Z</updated>
<author>
<name>Sergiu Cuciurean</name>
</author>
<published>2020-02-27T12:38:59Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=61e618be6a0efa8728e2172dc47c47c72217d49b'/>
<id>urn:sha1:61e618be6a0efa8728e2172dc47c47c72217d49b</id>
<content type='text'>
In a recent change to the SPI subsystem [1], a new `delay` struct was added
to replace the `delay_usecs`. This change replaces the current
`delay_usecs` with `delay` for this driver.

The `spi_transfer_delay_exec()` function [in the SPI framework] makes sure
that both `delay_usecs` &amp; `delay` are used (in this order to preserve
backwards compatibility).

[1] commit bebcfd272df6 ("spi: introduce `delay` field for
`spi_transfer` + spi_transfer_delay_exec()")

Signed-off-by: Sergiu Cuciurean &lt;sergiu.cuciurean@analog.com&gt;
Signed-off-by: Jonathan Cameron &lt;Jonathan.Cameron@huawei.com&gt;
</content>
</entry>
<entry>
<title>iio: imu: inv_mpu6050: temperature only work with accel/gyro</title>
<updated>2020-03-08T17:28:40Z</updated>
<author>
<name>Jean-Baptiste Maneyrol</name>
</author>
<published>2020-02-19T14:39:58Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=74a40e19f9db6606b5263aa08af2c684dd67b3d3'/>
<id>urn:sha1:74a40e19f9db6606b5263aa08af2c684dd67b3d3</id>
<content type='text'>
Temperature sensor works correctly only when accel and/or gyro
is turned on. Prevent polling value if they are not running.
Anyway it doesn't make sense to use it without sensor engines
on.

Signed-off-by: Jean-Baptiste Maneyrol &lt;jmaneyrol@invensense.com&gt;
Signed-off-by: Jonathan Cameron &lt;Jonathan.Cameron@huawei.com&gt;
</content>
</entry>
<entry>
<title>iio: imu: inv_mpu6050: use runtime pm with autosuspend</title>
<updated>2020-03-08T17:28:39Z</updated>
<author>
<name>Jean-Baptiste Maneyrol</name>
</author>
<published>2020-02-19T14:39:57Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=4599cac8461468a10dc375f4d4e12442e2d16d3f'/>
<id>urn:sha1:4599cac8461468a10dc375f4d4e12442e2d16d3f</id>
<content type='text'>
Use runtime power management for handling chip power and
sensor engines on/off. Simplifies things a lot since pm
runtime already has reference counter.
Usage of autosuspend reduces the number of power on/off. This
makes polling interface now usable to get data at low
frequency.

Signed-off-by: Jean-Baptiste Maneyrol &lt;jmaneyrol@invensense.com&gt;
Signed-off-by: Jonathan Cameron &lt;Jonathan.Cameron@huawei.com&gt;
</content>
</entry>
<entry>
<title>iio: imu: inv_mpu6050: dynamic sampling rate change</title>
<updated>2020-03-08T17:28:39Z</updated>
<author>
<name>Jean-Baptiste Maneyrol</name>
</author>
<published>2020-02-19T14:39:56Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=5e95ca3637d6f706d157a5f12e51f3e1c175285a'/>
<id>urn:sha1:5e95ca3637d6f706d157a5f12e51f3e1c175285a</id>
<content type='text'>
Sampling rate can be changed while the chip is running. It can
be useful thus do not prevent it.

Signed-off-by: Jean-Baptiste Maneyrol &lt;jmaneyrol@invensense.com&gt;
Signed-off-by: Jonathan Cameron &lt;Jonathan.Cameron@huawei.com&gt;
</content>
</entry>
</feed>
