mirror of
https://github.com/torvalds/linux.git
synced 2024-12-26 12:52:30 +00:00
c91799c50a
While testing I experience a deadlock while using the at86rf233 on a raspberry pi. The reason was an edge triggered gpio irq because the irq triggered while irq was disabled. This issue doesn't happend on a level triggered irq because the irq will hit after calling enable_irq. This patch adds a warning that it's not recommended to use a edge-triggered irq type. Also change the examples to high-level irqtype. Signed-off-by: Alexander Aring <alex.aring@gmail.com> Signed-off-by: Marcel Holtmann <marcel@holtmann.org>
28 lines
831 B
Plaintext
28 lines
831 B
Plaintext
* AT86RF230 IEEE 802.15.4 *
|
|
|
|
Required properties:
|
|
- compatible: should be "atmel,at86rf230", "atmel,at86rf231",
|
|
"atmel,at86rf233" or "atmel,at86rf212"
|
|
- spi-max-frequency: maximal bus speed, should be set to 7500000 depends
|
|
sync or async operation mode
|
|
- reg: the chipselect index
|
|
- interrupts: the interrupt generated by the device. Non high-level
|
|
can occur deadlocks while handling isr.
|
|
|
|
Optional properties:
|
|
- reset-gpio: GPIO spec for the rstn pin
|
|
- sleep-gpio: GPIO spec for the slp_tr pin
|
|
- xtal-trim: u8 value for fine tuning the internal capacitance
|
|
arrays of xtal pins: 0 = +0 pF, 0xf = +4.5 pF
|
|
|
|
Example:
|
|
|
|
at86rf231@0 {
|
|
compatible = "atmel,at86rf231";
|
|
spi-max-frequency = <7500000>;
|
|
reg = <0>;
|
|
interrupts = <19 4>;
|
|
interrupt-parent = <&gpio3>;
|
|
xtal-trim = /bits/ 8 <0x06>;
|
|
};
|