Linux kernel mirror (for testing)
git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
kernel
os
linux
docs: iio: bno055: Correct wording in driver documentation
Fix typos and improve wording in the bno055 driver documentation.
Signed-off-by: Erick Setubal Bacurau <erick.setubal@gmx.de>
Reviewed-by: Bagas Sanjaya <bagasdotme@gmail.com>
Link: https://patch.msgid.link/20250815070001.55185-1-erick.setubal@gmx.de
Signed-off-by: Jonathan Cameron <Jonathan.Cameron@huawei.com>
authored by
Erick Setubal Bacurau
and committed by
Jonathan Cameron
c1d7b8fe
4c0cdcf1
+6
-6
+6
-6
Documentation/iio/bno055.rst
+6
-6
Documentation/iio/bno055.rst
···
9
9
10
10
This driver supports Bosch BNO055 IMUs (on both serial and I2C busses).
11
11
12
-
Accelerometer, magnetometer and gyroscope measures are always provided.
12
+
Accelerometer, magnetometer and gyroscope measurements are always available.
13
13
When "fusion_enable" sysfs attribute is set to 1, orientation (both Euler
14
14
angles and quaternion), linear velocity and gravity vector are also
15
15
provided, but some sensor settings (e.g. low pass filtering and range)
16
-
became locked (the IMU firmware controls them).
16
+
become locked (the IMU firmware controls them).
17
17
18
18
This driver supports also IIO buffers.
19
19
···
24
24
operating in fusion mode. The magnetometer autocalibration can however be
25
25
disabled by writing 0 in the sysfs in_magn_calibration_fast_enable attribute.
26
26
27
-
The driver provides access to autocalibration flags (i.e. you can known if
28
-
the IMU has successfully autocalibrated) and to the calibration data blob.
27
+
The driver provides access to autocalibration flags (i.e. you can determine
28
+
if the IMU has successfully autocalibrated) and to the calibration data blob.
29
29
30
30
The user can save this blob in a firmware file (i.e. in /lib/firmware) that
31
31
the driver looks for at probe time. If found, then the IMU is initialized
32
32
with this calibration data. This saves the user from performing the
33
-
calibration procedure every time (which consist of moving the IMU in
34
-
various way).
33
+
calibration procedure every time (which consists of moving the IMU in
34
+
various ways).
35
35
36
36
The driver looks for calibration data file using two different names: first
37
37
a file whose name is suffixed with the IMU unique ID (exposed in sysfs as