ti,tmp451 (on i2c bus)
Description
Texas Instruments TMP451 remote and local temperature sensor.
See https://www.ti.com/product/TMP451
Properties
Properties not inherited from the base binding file.
Name |
Type |
Details |
|---|---|---|
|
|
Conversion rate in micro-Hz. Controls how often the sensor
performs temperature conversions in continuous mode.
62500 = 0.0625 Hz (16s)
125000 = 0.125 Hz (8s)
250000 = 0.25 Hz (4s)
500000 = 0.5 Hz (2s)
1000000 = 1 Hz (1s)
2000000 = 2 Hz (500ms)
4000000 = 4 Hz (250ms)
8000000 = 8 Hz (125ms)
16000000 = 16 Hz (63ms)
32000000 = 32 Hz (32ms)
Defaults to 16000000 (16 Hz), which matches POR value.
Default value: Legal values: |
|
|
THERM hysteresis value in deg C. Defines how far below the
THERM limit the temperature must drop before the THERM output is
de-asserted.
Valid range: 0 to 255.
Defaults to 10, which matches POR value.
Default value: |
|
|
Ideality factor (eta-factor) correction register value for the remote diode.
See Table 27 in the TMP451 datasheet for the mapping between
register value and effective ideality factor.
Valid range: -128 to 127.
Defaults to 0 (eta = 1.008), which matches POR value.
Default value: |
|
|
Digital filter control register value. Enables the on-chip digital
filter on the remote temperature channel.
0 = filter disabled
1 = filter level 1 enabled (averages last 4 samples)
2 = filter level 2 enabled (averages last 8 samples)
Defaults to 0 (disabled), which matches POR value.
Default value: Legal values: |
|
|
Remote temperature offset in milli-deg C. This value is
added to the remote ADC result to compensate for system-level
calibration errors. The TMP451 offset register has 0.0625 deg C
resolution.
Valid range: -128000 to 127937.
Defaults to 0, which matches POR value.
Default value: |
|
|
Local temperature THERM limit in deg C.
When the local temperature exceeds this value, the THERM output (pin 4) is asserted.
Valid range: -64 to 191.
Defaults to 85, which matches POR value (but raw value adjusted for extended range).
Default value: |
|
|
Remote temperature THERM limit in deg C.
When the remote temperature exceeds this value, the THERM output (pin 4) is asserted.
Valid range: -64 to 191.
Defaults to 108, which matches POR value (but raw value adjusted for extended range).
Default value: |
|
|
Configures the function of pin 6 (ALERT/THERM2).
Note: Software triggers only support the ALERT configuration; the driver assumes
if this pin is configured for THERM2 it will not be used as an interrupt.
"alert" = latching; triggers on any limit violation or remote diode open
"therm2" = non-latching; triggers on high limit exceeded only, self-clears with hysteresis
Defaults to "alert", which matches POR value.
Default value: Legal values: |
|
|
Number of consecutive out-of-limit measurements required before the ALERT pin is asserted.
Note: Only applies when pin6-mode is configured as ALERT.
Defaults to 1, which matches POR value.
Default value: Legal values: |
|
|
GPIO connected to the ALERT pin (pin 6).
Active-low, open-drain output.
Note: The driver only supports this if pin6-mode is configured as ALERT.
|
|
|
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).
|
|
|
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.
|
|
|
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.
|
Deprecated properties not inherited from the base binding file.
(None)
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 “ti,tmp451” compatible.
Name |
Type |
Details |
|---|---|---|
|
|
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: See Important properties for more information. |
|
|
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 Important properties for more information. |
|
|
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 Important properties for more information. |
|
|
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"
|
|
|
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 Important properties for more information. |
|
|
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.
|
|
|
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.
|
|
|
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.
|
|
|
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 Important properties for more information. |
|
|
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
|
|
|
Optional names given to each clock provider in the "clocks" property.
|
|
|
This property encodes the number of <u32> 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.
|
|
|
This property encodes the number of <u32> 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.
|
|
|
Indicates that the device is capable of coherent DMA operations.
For details, see "2.3.10 dma-coherent" in Devicetree Specification v0.4.
|
|
|
DMA channel specifiers relevant to the device.
|
|
|
Optional names given to the DMA channel specifiers in the "dmas" property.
|
|
|
IO channel specifiers relevant to the device.
|
|
|
Optional names given to the IO channel specifiers in the "io-channels" property.
|
|
|
Mailbox / IPM channel specifiers relevant to the device.
|
|
|
Optional names given to the mbox specifiers in the "mboxes" property.
|
|
|
Power domain specifiers relevant to the device.
|
|
|
Optional names given to the power domain specifiers in the "power-domains" property.
|
|
|
Number of cells in power-domains property
|
|
|
HW spinlock id relevant to the device.
|
|
|
Optional names given to the hwlock specifiers in the "hwlocks" property.
|
|
|
Do not initialize device automatically on boot. Device should be manually
initialized using device_init().
|
|
|
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.
|
|
|
Automatically configure the device for runtime power management after the
init function runs.
|
|
|
List of power states that will disable this device power.
|