This is the documentation for the latest (main) development branch of Zephyr. If you are looking for the documentation of previous releases, use the drop-down menu on the left and select the desired version.

st,iis2dlpc (on i2c bus)

Vendor: STMicroelectronics

Description

STMicroelectronics IIS2DLPC accelerometer accessed through I2C bus

Properties

Properties not inherited from the base binding file.

Name

Type

Details

supply-gpios

phandle-array

GPIO specifier that controls power to the device.

This property should be provided when the device has a dedicated
switch that controls power to the device.  The supply state is
entirely the responsibility of the device driver.

Contrast with vin-supply.

vin-supply

phandle

Reference to the regulator that controls power to the device.
The referenced devicetree node must have a regulator compatible.

This property should be provided when device power is supplied
by a shared regulator.  The supply state is dependent on the
request status of all devices fed by the regulator.

Contrast with supply-gpios.  If both properties are provided
then the regulator must be requested before the supply GPIOS is
set to an active state, and the supply GPIOS must be set to an
inactive state before releasing the regulator.

drdy-gpios

phandle-array

DRDY pin

This pin defaults to active high when produced by the sensor.
The property value should ensure the flags properly describe
the signal that is presented to the driver.

drdy-int

int

Select DRDY pin number (1 or 2).

This number represents which of the two interrupt pins
(INT1 or INT2) the drdy line is attached to. This property is not
mandatory and if not present it defaults to 1 which is the
configuration at power-up.

- 1 # drdy is generated from INT1
- 2 # drdy is generated from INT2

Default value: 1

Legal values: 1, 2

range

int

Range in g. Default is power-up configuration.

- 16 # 16g (1.952 mg/LSB)
- 8  #  8g (0.976 mg/LSB)
- 4  #  4g (0.488 mg/LSB)
- 2  #  2g (0.244 mg/LSB)

Default value: 2

Legal values: 16, 8, 4, 2

power-mode

int

Specify the sensor power mode. Default is power-up configuration.

- 0 # IIS2DLPC_DT_LP_M1
- 1 # IIS2DLPC_DT_LP_M2
- 2 # IIS2DLPC_DT_LP_M3
- 3 # IIS2DLPC_DT_LP_M4
- 4 # IIS2DLPC_DT_HP_MODE

Legal values: 0, 1, 2, 3, 4

tap-mode

int

Tap mode. Default is power-up configuration.

- 0 # IIS2DLPC_DT_SINGLE_TAP
- 1 # IIS2DLPC_DT_SINGLE_DOUBLE_TAP

Legal values: 0, 1

tap-threshold

array

Tap X/Y/Z axes threshold. Default is power-up configuration.
(X/Y/Z values range from 0x00 to 0x1F)

Thresholds to start the tap-event detection procedure on the X/Y/Z axes.
Threshold values for each axis are unsigned 5-bit corresponding
to a 2g acceleration full-scale range. A threshold value equal to zero
corresponds to disable the tap detection on that axis.

For example, if you want to set the threshold for X to 12, for Z to 14
and want to disable tap detection on Y, you should specify in Device Tree

    tap-threshold = <12>, <0>, <14>

which is equivalent to X = 12 * 2g/32 = 750mg and Z = 14 * 2g/32 = 875mg.

Default value: [0, 0, 0]

tap-shock

int

Tap shock value. Default is power-up configuration.
(values range from 0x0 to 0x3)
This register represents the maximum time of an over-threshold signal
detection to be recognized as a tap event. Where 0 equals 4*1/ODR and
1LSB = 8*1/ODR.

tap-latency

int

Tap latency. Default is power-up configuration.
(values range from 0x0 to 0xF)
When double-tap recognition is enabled, this register expresses the
maximum time between two successive detected taps to determine a
double-tap event. Where 0 equals 16*1/ODR and 1LSB = 32*1/ODR.

tap-quiet

int

Expected quiet time after a tap detection. Default is power-up configuration.
(values range from 0x0 to 0x3)
This register represents the time after the first detected tap in which
there must not be any overthreshold event. Where 0 equals 2*1/ODR
and 1LSB = 4*1/ODR.

friendly-name

string

Human readable string describing the sensor. It can be used to
distinguish multiple instances of the same model (e.g., lid accelerometer
vs. base accelerometer in a laptop) to a host operating system.

This property is defined in the Generic Sensor Property Usages of the HID
Usage Tables specification
(https://usb.org/sites/default/files/hut1_3_0.pdf, section 22.5).