nordic,nrf-twis
Vendor: Nordic Semiconductor
Description
These nodes are “i2c” bus nodes.
Nordic nRF family TWIS (TWI slave with EasyDMA).
Note: for Zephyr users, the I2C slave API is not available for
these devices. See this issue for more details and a HAL-based
workaround:
https://github.com/zephyrproject-rtos/zephyr/issues/21445
This binding can be used for nodes which can represent TWIS
peripherals. A single SoC peripheral ID is often associated with
multiple I2C peripherals, like a TWIM and a TWIS. You can choose
TWIS by setting the node's "compatible" to "nordic,nrf-twis"
and its "status" to "okay", e.g. using an overlay file like this:
/* This is for TWIS0 -- change to "i2c1" for TWIS1, etc. */
&i2c0 {
compatible = "nordic,nrf-twis";
status = "okay";
/* other property settings can go here */
};
This works on any supported SoC, for all TWIS instances.
Properties
Properties not inherited from the base binding file.
Name |
Type |
Details |
---|---|---|
|
|
Initial clock frequency in Hz
|
|
|
Size of the submission queue for blocking requests
Default value: |
|
|
Size of the completion queue for blocking requests
Default value: |
|
|
Pin configuration/s for the first state. Content is specific to the
selected pin controller driver implementation.
This property is required. |
|
|
Pin configuration/s for the second state. See pinctrl-0.
|
|
|
Pin configuration/s for the third state. See pinctrl-0.
|
|
|
Pin configuration/s for the fourth state. See pinctrl-0.
|
|
|
Pin configuration/s for the fifth state. See pinctrl-0.
|
|
|
Names for the provided states. The number of names needs to match the
number of states.
|
|
|
List of signals that require CLOCKPIN setting enablement.
|
|
|
Maximum number of bits available in the EasyDMA MAXCNT register. This
property must be set at SoC level DTS files.
This property is required. |
|
|
List of memory region phandles
|
|
|
A list of names, one for each corresponding phandle in memory-region
|
|
|
TWI slave address 0
|
|
|
TWI slave address 1
|
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 “nordic,nrf-twis” compatible.
Name |
Type |
Details |
---|---|---|
|
|
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.
|
|
|
Power domain the device belongs to.
The device will be notified when the power domain it belongs to is either
suspended or resumed.
|
|
|
Automatically configure the device for runtime power management after the
init function runs.
|
|
|
indicates the operational status of a device
Legal values: See Important properties for more information. |
|
|
compatible strings
This property is required. See Important properties for more information. |
|
|
register space
This property is required. See Important properties for more information. |
|
|
name of each register space
|
|
|
interrupts for device
This property is required. See Important properties for more information. |
|
|
extended interrupt specifier for device
|
|
|
name of each interrupt
|
|
|
phandle to interrupt controller node
|
|
|
Human readable string describing the device (used as device_get_binding() argument)
See Important properties for more information. This property is deprecated. |
|
|
Clock gate information
|
|
|
name of each clock
|
|
|
number of address cells in reg property
This property is required. Constant value: |
|
|
number of size cells in reg property
This property is required. |
|
|
DMA channels specifiers
|
|
|
Provided names of DMA channel specifiers
|
|
|
IO channels specifiers
|
|
|
Provided names of IO channel specifiers
|
|
|
mailbox / IPM channels specifiers
|
|
|
Provided names of mailbox / IPM channel specifiers
|
|
|
Do not initialize device automatically on boot. Device should be manually
initialized using device_init().
|