Hi,
I am currently having issues with the SPI driver on the beaglebone using
the 3.7-rc8 kernel[1]. I have probed the SPI pins and I have found that
writing works however reading doesn't. When using DMA the program seems
to lock hard and no data is sent on the bus. I am testing the bus using
spidev and the spidev_test[2] application, however I first came across
spi issues with a custom spi driver which stopped working when I
transitioned from 3.2-psp to 3.7-rc8.
The current output I am seeing from the spidev_test program is just a
series of 0x00 data, which looks to me like no data is getting in at
all. The spidev_test program is not using DMA as the buffer size is too
low, so I forced the dma on when buffer size is > 1 and the program
hangs hard with the system still responding to other commands.I have
briged the pins 18 and 21 on the BeagleBone P9 header.
Has anyone seen issues like this, or if not if someone could please test
the latest 3.7-rc8 from [1] and let me know if it works for them and the
issue is at my end.
To get spidev working with devicetree I applied the patch from [3] and
changed the dtb as in the patch pasted below.
[1] https://github.com/beagleboard/kernel/tree/3.7
[2] http://lxr.linux.no/#linux+v3.6.9/Documentation/spi/spidev_test.c
[3]
http://www.mail-archive.com/spi-devel-general@xxxxxxxxxxxxxxxxxxxxx/msg09958.html
diff --git a/arch/arm/boot/dts/am335x-bone-common.dtsi
b/arch/arm/boot/dts/am335x-bone-common.dtsi
index 543365d..8fff665 100644
--- a/arch/arm/boot/dts/am335x-bone-common.dtsi
+++ b/arch/arm/boot/dts/am335x-bone-common.dtsi
@@ -440,10 +440,19 @@
};
&spi0 {
+ status = "okay";
pinctrl-names = "default";
pinctrl-0 = <&spi0_pins>;
+
+ spidev: spidev@0 {
+ compatible = "linux,spidev";
+ reg = <0>;
+ spi-max-frequency = <24000000>;
+ };
+
};
+
&spi1 {
pinctrl-names = "default";
pinctrl-0 = <&spi1_pins>;
--
Jack Mitchell (jack@xxxxxxxxxxx)
Embedded Systems Engineer
http://www.embed.me.uk
--
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
