:orphan:
.. raw:: html
.. dtcompatible:: adi,max30210
.. _dtbinding_adi_max30210:
adi,max30210 (on i2c bus)
#########################
.. sidebar:: Overview
:Name: ``adi,max30210``
:Vendor: :ref:`Analog Devices, Inc. `
:Used in: :zephyr:board-catalog:`List of boards <#compatibles=adi,max30210>` using
this compatible
:Driver: :zephyr_file:`drivers/sensor/adi/max30210/max30210.c`
Description
***********
.. code-block:: none
MAX30210, a high-accuracy digital temperature sensor from Analog Devices.
Properties
**********
.. tabs::
.. group-tab:: Node specific properties
Properties not inherited from the base binding file.
.. list-table::
:widths: 1 1 4
:header-rows: 1
* - Name
- Type
- Details
* - ``interrupt-gpios``
- ``phandle-array``
- .. code-block:: none
The INT1 pin defaults to active low when produced by the sensor. The property value should
ensure the flags properly describe the signal that is presented to the driver.
* - ``sampling-rate``
- ``int``
- .. code-block:: none
The sampling rate of the sensor in Hz. This value is used to configure the sensor's internal
sampling rate. If not specified, the driver will use a default value of 0.015625 Hz
which is also the reset value.
Legal values: ``0x0``, ``0x1``, ``0x2``, ``0x3``, ``0x4``, ``0x5``, ``0x6``, ``0x7``, ``0x8``, ``0x9``
* - ``alarm-high-setup``
- ``int``
- .. code-block:: none
The high temperature threshold for the sensor in degrees Celsius. When the temperature
exceeds this threshold, the INT1 pin will be asserted. The value is represented as a
signed 16-bit integer in two's complement format, with a resolution of 0.005 degrees Celsius.
Usage: input a temperature in millidegrees Celsius (e.g., 25000 for 25.000°C), and the driver
will convert it to the appropriate register value. Default value is equivalent is 163.835°C
which is equivalent to the reset value (0x7FFF) for ALARM_HI register.
Default value: ``163835``
* - ``alarm-low-setup``
- ``int``
- .. code-block:: none
The low temperature threshold for the sensor in degrees Celsius. When the temperature
falls below this threshold, the INT1 pin will be asserted. The value is represented as a
signed 16-bit integer in two's complement format, with a resolution of 0.005 degrees Celsius.
Usage: input a temperature in millidegrees Celsius (e.g., 25000 for 25.000°C), and the driver
will convert it to the appropriate register value. Default value is equivalent is -163.840°C
which is equivalent to the reset value (0x8000) for ALARM_LO register.
Default value: ``-163840``
* - ``inc-fast-thresh``
- ``int``
- .. code-block:: none
The increment threshold between samples. If the temperature increments
by more than N x 5 m°C between samples, the INT1 pin will be asserted
when interrupts are enabled. The default value is 0, which represents 0 m°C
and corresponds to the device register reset value.
* - ``dec-fast-thresh``
- ``int``
- .. code-block:: none
The decrement threshold between samples. If the temperature decrements
by more than N x 5 m°C between samples, the INT1 pin will be asserted
when interrupts are enabled. The default value is 0, which represents 0 m°C
and corresponds to the device register reset value.
* - ``hi-trip-count``
- ``int``
- .. code-block:: none
The number of trip counts exceeding the high temperature threshold that must occur
to assert required to assert the TEMP_HI alarm on the INT1 pin. Default value is 1
which equates to a single sample exceeding the high temperature threshold and corresponds
to the device register reset value.
Default value: ``1``
Legal values: ``1``, ``2``, ``3``, ``4``
* - ``lo-trip-count``
- ``int``
- .. code-block:: none
The number of trip counts below the low temperature threshold that must occur
to assert required to assert the TEMP_LO alarm on the INT1 pin. Default value is 1
which equates to a single sample below the low temperature threshold and corresponds
to the device register reset value.
Default value: ``1``
Legal values: ``1``, ``2``, ``3``, ``4``
* - ``hi-trip-non-consecutive``
- ``boolean``
- .. code-block:: none
If true, the high temperature threshold trip count is non-consecutive.
* - ``lo-trip-non-consecutive``
- ``boolean``
- .. code-block:: none
If true, the low temperature threshold trip count is non-consecutive.
* - ``start-continuous-conversion``
- ``boolean``
- .. code-block:: none
If true, the sensor will start temperature conversions immediately after initialization.
If false, the sensor will remain in standby mode until explicitly started by the driver.
* - ``friendly-name``
- ``string``
- .. code-block:: none
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).
* - ``supply-gpios``
- ``phandle-array``
- .. code-block:: none
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``
- .. code-block:: none
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.
.. group-tab:: Deprecated node specific properties
Deprecated properties not inherited from the base binding file.
(None)
.. group-tab:: Base properties
Properties inherited from the base binding file, which defines
common properties that may be set on many nodes. Not all of these
may apply to the "adi,max30210" compatible.
.. list-table::
:widths: 1 1 4
:header-rows: 1
* - Name
- Type
- Details
* - ``reg``
- ``array``
- .. code-block:: none
Information used to address the device. The value is specific to
the device (i.e. is different depending on the compatible
property).
The "reg" property is typically a sequence of (address, length) pairs.
Each pair is called a "register block". Values are
conventionally written in hex.
For details, see "2.3.6 reg" in Devicetree Specification v0.4.
This property is **required**.
See :ref:`zephyr:dt-important-props` for more information.
* - ``status``
- ``string``
- .. code-block:: none
Indicates the operational status of the hardware or other
resource that the node represents. In particular:
- "okay" means the resource is operational and, for example,
can be used by device drivers
- "disabled" means the resource is not operational and the system
should treat it as if it is not present
For details, see "2.3.4 status" in Devicetree Specification v0.4.
Legal values: ``okay``, ``disabled``, ``reserved``, ``fail``, ``fail-sss``
See :ref:`zephyr:dt-important-props` for more information.
* - ``compatible``
- ``string-array``
- .. code-block:: none
This property is a list of strings that essentially define what
type of hardware or other resource this devicetree node
represents. Each device driver checks for specific compatible
property values to find the devicetree nodes that represent
resources that the driver should manage.
The recommended format is "vendor,device", The "vendor" part is
an abbreviated name of the vendor. The "device" is usually from
the datasheet.
The compatible property can have multiple values, ordered from
most- to least-specific. Having additional values is useful when the
device is a specific instance of a more general family, to allow the
system to match the most specific driver available.
For details, see "2.3.1 compatible" in Devicetree Specification v0.4.
This property is **required**.
See :ref:`zephyr:dt-important-props` for more information.
* - ``reg-names``
- ``string-array``
- .. code-block:: none
Optional names given to each register block in the "reg" property.
For example:
/ {
soc {
#address-cells = <1>;
#size-cells = <1>;
uart@1000 {
reg = <0x1000 0x2000>, <0x3000 0x4000>;
reg-names = "foo", "bar";
};
};
};
The uart@1000 node has two register blocks:
- one with base address 0x1000, size 0x2000, and name "foo"
- another with base address 0x3000, size 0x4000, and name "bar"
* - ``interrupts``
- ``array``
- .. code-block:: none
Information about interrupts generated by the device, encoded as an array
of one or more interrupt specifiers. The format of the data in this property
varies by where the device appears in the interrupt tree. Devices with the same
"interrupt-parent" will use the same format in their interrupts properties.
For details, see "2.4 Interrupts and Interrupt Mapping" in
Devicetree Specification v0.4.
See :ref:`zephyr:dt-important-props` for more information.
* - ``interrupts-extended``
- ``compound``
- .. code-block:: none
Extended interrupt specifier for device, used as an alternative to
the "interrupts" property.
For details, see "2.4 Interrupts and Interrupt Mapping" in
Devicetree Specification v0.4.
* - ``interrupt-names``
- ``string-array``
- .. code-block:: none
Optional names given to each interrupt generated by a device.
The interrupts themselves are defined in either "interrupts" or
"interrupts-extended" properties.
For details, see "2.4 Interrupts and Interrupt Mapping" in
Devicetree Specification v0.4.
* - ``interrupt-parent``
- ``phandle``
- .. code-block:: none
If present, this refers to the node which handles interrupts generated
by this device.
For details, see "2.4 Interrupts and Interrupt Mapping" in
Devicetree Specification v0.4.
* - ``label``
- ``string``
- .. code-block:: none
Human readable string describing the device. Use of this property is
deprecated except as needed on a case-by-case basis.
For details, see "4.1.2 Miscellaneous Properties" in Devicetree
Specification v0.4.
See :ref:`zephyr:dt-important-props` for more information.
* - ``clocks``
- ``phandle-array``
- .. code-block:: none
Information about the device's clock providers. In general, this property
should follow conventions established in the dt-schema binding:
https://github.com/devicetree-org/dt-schema/blob/main/dtschema/schemas/clock/clock.yaml
* - ``clock-names``
- ``string-array``
- .. code-block:: none
Optional names given to each clock provider in the "clocks" property.
* - ``#address-cells``
- ``int``
- .. code-block:: none
This property encodes the number of cells used by address fields
in "reg" properties in this node's children.
For details, see "2.3.5 #address-cells and #size-cells" in Devicetree
Specification v0.4.
* - ``#size-cells``
- ``int``
- .. code-block:: none
This property encodes the number of cells used by size fields in
"reg" properties in this node's children.
For details, see "2.3.5 #address-cells and #size-cells" in Devicetree
Specification v0.4.
* - ``dmas``
- ``phandle-array``
- .. code-block:: none
DMA channel specifiers relevant to the device.
* - ``dma-names``
- ``string-array``
- .. code-block:: none
Optional names given to the DMA channel specifiers in the "dmas" property.
* - ``io-channels``
- ``phandle-array``
- .. code-block:: none
IO channel specifiers relevant to the device.
* - ``io-channel-names``
- ``string-array``
- .. code-block:: none
Optional names given to the IO channel specifiers in the "io-channels" property.
* - ``mboxes``
- ``phandle-array``
- .. code-block:: none
Mailbox / IPM channel specifiers relevant to the device.
* - ``mbox-names``
- ``string-array``
- .. code-block:: none
Optional names given to the mbox specifiers in the "mboxes" property.
* - ``power-domains``
- ``phandle-array``
- .. code-block:: none
Power domain specifiers relevant to the device.
* - ``power-domain-names``
- ``string-array``
- .. code-block:: none
Optional names given to the power domain specifiers in the "power-domains" property.
* - ``#power-domain-cells``
- ``int``
- .. code-block:: none
Number of cells in power-domains property
* - ``hwlocks``
- ``phandle-array``
- .. code-block:: none
HW spinlock id relevant to the device.
* - ``hwlock-names``
- ``string-array``
- .. code-block:: none
Optional names given to the hwlock specifiers in the "hwlocks" property.
* - ``zephyr,deferred-init``
- ``boolean``
- .. code-block:: none
Do not initialize device automatically on boot. Device should be manually
initialized using device_init().
* - ``wakeup-source``
- ``boolean``
- .. code-block:: none
Property to identify that a device can be used as wake up source.
When this property is provided a specific flag is set into the
device that tells the system that the device is capable of
wake up the system.
Wake up capable devices are disabled (interruptions will not wake up
the system) by default but they can be enabled at runtime if necessary.
* - ``zephyr,pm-device-runtime-auto``
- ``boolean``
- .. code-block:: none
Automatically configure the device for runtime power management after the
init function runs.
* - ``zephyr,disabling-power-states``
- ``phandles``
- .. code-block:: none
List of power states that will disable this device power.