summaryrefslogtreecommitdiffstats
path: root/tools/perf/scripts/python
diff options
context:
space:
mode:
authorMatti Vaittinen <mazziesaccount@gmail.com>2024-11-21 10:19:50 +0200
committerJonathan Cameron <Jonathan.Cameron@huawei.com>2024-12-07 17:47:58 +0000
commitd95986fb818d3f76841f2cd32c74dd7961a2a15d (patch)
treebb242f6a4231580d6141b023a89ff83756d8a880 /tools/perf/scripts/python
parent9fdf1d03331623e377d8445e600b09111259a608 (diff)
downloadlinux-d95986fb818d3f76841f2cd32c74dd7961a2a15d.tar.gz
linux-d95986fb818d3f76841f2cd32c74dd7961a2a15d.zip
iio: accel: kx022a: Improve reset delay
All the sensors supported by kx022a driver seemed to require some delay after software reset to be operational again. More or less a random msleep(1) was added to cause the driver to go to sleep so the sensor has time to become operational again. Now we have official docuumentation available: https://fscdn.rohm.com/kionix/en/document/AN010_KX022ACR-Z_Power-on_Procedure_E.pdf https://fscdn.rohm.com/kionix/en/document/TN027-Power-On-Procedure.pdf https://fscdn.rohm.com/kionix/en/document/AN011_KX134ACR-LBZ_Power-on_Procedure_E.pdf stating the required time is 2 ms. Due to the nature of the current msleep implementation, the msleep(1) is likely to be sleeping more than 2ms already - but the value "1" is misleading in case someone needs to optimize the start time and change the msleep to a more accurate delay. Hence it is better for "documentation" purposes to use value which actually reflects the specified 2ms wait time. Change the value of delay after software reset to match the specifications and add links to the power-on procedure specifications. Signed-off-by: Matti Vaittinen <mazziesaccount@gmail.com> Link: https://patch.msgid.link/ac1b6705945cded0e79593d64e55522681e00f9a.1732105157.git.mazziesaccount@gmail.com Signed-off-by: Jonathan Cameron <Jonathan.Cameron@huawei.com>
Diffstat (limited to 'tools/perf/scripts/python')
0 files changed, 0 insertions, 0 deletions