>> Here’s the relevant parts of the current device tree (it’s a bit of a mess currently, but perhaps you can still see if there’s something fishy):
>>
>> #include <dt-bindings/interrupt-controller/irq.h>
>>
>> &am33xx_pinmux {
>> spi0_pins_default: spi0_pins_default {
>> pinctrl-single,pins = <
>> 0x150 (PIN_INPUT_PULLDOWN | MUX_MODE0) /* spi0_sck */
>> 0x154 (PIN_INPUT | MUX_MODE0) /* spi0_d0 */
>> 0x158 (PIN_OUTPUT | MUX_MODE0) /* spi0_d1 */
>> 0x15C (PIN_OUTPUT_PULLUP | MUX_MODE0) /* spi0_cs0 */
>> 0x17C (PIN_OUTPUT_PULLUP | MUX_MODE7) /* Chip Select on GPIO0[13] (#505) */
>>> ;
>> };
>
> Your pinmuxing for SPI0 is a bit different than for spi1. Just like you
> did for SPI1 set sclk and d0 to an INPUT_PULLUP and d1 to an
> OUTPUT_PULLUP and see if that makes a difference.
I have tried with same pinmux for spi0 as spi1, but that made no difference. Sorry about the state of the dts that I included. I’ve been trying many different combinations, and that was just the current state. The reason for d1 being an input and d0 an output is that I’ve built a cape where function of d0 and d1 was swapped. Using "ti,pindir-d0-out-d1-in = <1>;” works as expected though. But I’ve tried with d0 as input and d1 as output as well with same result.
>
> I have some spi work todo hopefully this week. If your still having
> issues let me know and I'll try to reproduce this issue.
I would be very grateful if you would test functionality of spi0 and spi1 on your end and perhaps show me your device tree if you get it to work!
The pins I would prefer to use are:
SPI0 SCK on P9[22]
SPI0 MOSI on P9[21]
SPI0 MISO on P9[18]
SPI0 CS0 on P9[17]
SPI0 CS1 on P9[19] (configured as gpio)
Regards,
Joantan Magnusson--
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
