:orphan:
.. raw:: html
.. dtcompatible:: atmel,rf2xx
.. _dtbinding_atmel_rf2xx:
atmel,rf2xx (on spi bus)
########################
Vendor: :ref:`Atmel Corporation `
.. note::
An implementation of a driver matching this compatible is available in
:zephyr_file:`drivers/ieee802154/ieee802154_rf2xx.c`.
Description
***********
.. code-block:: none
ATMEL AT86RF2xx 802.15.4 wireless transceiver
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
* - ``irq-gpios``
- ``phandle-array``
- This property is **required**.
* - ``reset-gpios``
- ``phandle-array``
- This property is **required**.
* - ``slptr-gpios``
- ``phandle-array``
- .. code-block:: none
Multi-functional pin that controls sleep, deep sleep, transmit
start and receive states
This property is **required**.
* - ``dig2-gpios``
- ``phandle-array``
- .. code-block:: none
RX and TX Frame Time Stamping(TX_ARET)
* - ``clkm-gpios``
- ``phandle-array``
- .. code-block:: none
Master clock signal output
* - ``local-mac-address``
- ``uint8-array``
- .. code-block:: none
Specifies the MAC address that was assigned to the network
device
* - ``channel-page``
- ``int``
- .. code-block:: none
Selects Channel Page accordingly with IEEE 802.15.4 standard. The Page 0
is used in both Sub-Giga and 2.4GHz. It allows select channels 0-10 in
Sub-Giga band (0: BPSK-20, 1-10: BPSK-40) and 11-26 in 2.4GHz band
(11-26: O-QPSK-250). Channel 2 is for Sub-Giga and selects
(0: OQPSK-SIN-RC-100, 1-10: OQPSK-SIN-250). Channel 5 is for Sub-Giga
(JAPAN) and selects (0-3: OQPSK-RC-250) .
0: Page 0 - BPSK-20 [0], BPSK-40 [1-10], O-QPSK-250 [11-26].
2: Page 2 - OQPSK-SIN-RC-100 [0], OQPSK-SIN-250 [1-10].
5: Page 5 - OQPSK-RC-250 [0-3].
Legal values: ``0``, ``2``, ``5``
* - ``tx-pwr-table``
- ``uint8-array``
- .. code-block:: none
This is the Transmission Power Mapping Table array used to comply with
local regulations. By default this value set an output power above 0dBm
for all transceivers. This property must be used with tx-pwr-min and
tx-pwr-max for normal operations. The number of elements is defined by
the size of the tx-pwr-table array property. The max entry value for
2.4GHz is 0x0f and 0xff for Sub-Giga. See PHY_TX_PWR at datasheet for
more details.
The output power is determined by following formula:
linear_step = (tx-pwr-max - tx-pwr-min)
/ (sizeof(tx-pwr-table) - 1.0);
table_index = abs((value_in_dbm - tx-pwr-max) / linear_step);
output_power = tx-pwr-table[table_index];
Using AT86RF233 as example without external PA. By the datasheet the
tx-pwr-min = -17 dBm and tx-pwr-max = +4 dBm. Using 48 elements in the
tx-pwr-table array. The table array is filled from higher to lower power.
tx-pwr-min = [01 11]; /* -17.0 dBm */
tx-pwr-max = [00 04]; /* 4.0 dBm */
tx-pwr-table = [00 01 03 04 05 05 06 06
07 07 07 08 08 09 09 0a
0a 0a 0b 0b 0b 0b 0c 0c
0c 0c 0d 0d 0d 0d 0d 0d
0d 0d 0e 0e 0e 0e 0e 0e
0e 0e 0e 0e 0e 0e 0f 0f];
The values in the table are filled based on table 9-9 [TX Output Power]
using the linear step in dBm as:
linear_step = (4 - (-17)) / (48 - 1) => ~0.45 dBm
Assuming that user wants set 0 dBm as output power:
table_index = abs((0 - 4) / 0.45) => 8.95 ( round to 9 )
output_power = tx-pwr-table[9] => 0x07 ( 0 dBm as table 9-9 )
Note when tx-pwr-min is [0x00, 0x00] and tx-pwr-max is [0x00, 0x00]
the linear step is zero. This means that table_index will be always the
first element of the tx-pwr-table array, which is 0x00 by default. This
is defined as general case when user not define any tx-pwr-* entries. It
sets the transceiver to use always a value above 0 dBm as output power.
Default value: ``[0]``
* - ``tx-pwr-min``
- ``uint8-array``
- .. code-block:: none
This value represent minimum normalized value in dBm for the transceiver
output power. This property must be used when tx-pwr-table is defined.
The value is represented by two entries where first element represents
the signal indication [0x00-positive, 0x01-negative] and second element
is the minimal value in dBm for the transceiver output power. By default,
the combination of tx-pwr-min as [0x00, 0x00] and tx-pwr-max as [0x00,
0x00] will create a fixed transmission power.
Default value: ``[0, 0]``
* - ``tx-pwr-max``
- ``uint8-array``
- .. code-block:: none
This value represent maximum normalized value in dBm for the transceiver
output power. This property must be used when tx-pwr-table is defined.
The value is represented by two entries where first element represents
the signal indication [ 0x00-positive] and second element is the maximum
value in dBm for the transceiver output power. By default, the
combination of tx-pwr-max as [0x00, 0x00] and tx-pwr-min as [0x00,
0x00] will create a fixed transmission power.
Default value: ``[0, 0]``
* - ``spi-max-frequency``
- ``int``
- .. code-block:: none
Maximum clock frequency of device's SPI interface in Hz
This property is **required**.
* - ``duplex``
- ``int``
- .. code-block:: none
Duplex mode, full or half. By default it's always full duplex thus 0
as this is, by far, the most common mode.
Use the macros not the actual enum value, here is the concordance
list (see dt-bindings/spi/spi.h)
0 SPI_FULL_DUPLEX
2048 SPI_HALF_DUPLEX
Legal values: ``0``, ``2048``
* - ``frame-format``
- ``int``
- .. code-block:: none
Motorola or TI frame format. By default it's always Motorola's,
thus 0 as this is, by far, the most common format.
Use the macros not the actual enum value, here is the concordance
list (see dt-bindings/spi/spi.h)
0 SPI_FRAME_FORMAT_MOTOROLA
32768 SPI_FRAME_FORMAT_TI
Legal values: ``0``, ``32768``
* - ``spi-cpol``
- ``boolean``
- .. code-block:: none
SPI clock polarity which indicates the clock idle state.
If it is used, the clock idle state is logic high; otherwise, low.
* - ``spi-cpha``
- ``boolean``
- .. code-block:: none
SPI clock phase that indicates on which edge data is sampled.
If it is used, data is sampled on the second edge; otherwise, on the first edge.
* - ``spi-hold-cs``
- ``boolean``
- .. code-block:: none
In some cases, it is necessary for the master to manage SPI chip select
under software control, so that multiple spi transactions can be performed
without releasing it. A typical use case is variable length SPI packets
where the first spi transaction reads the length and the second spi transaction
reads length bytes.
* - ``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 "atmel,rf2xx" 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: ``'ok'``, ``'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
* - ``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.