Hi Kevin,
I can successfully run 'spidev_test' from user space as shown below.
address@hidden debug]# ./spidev_test
spi mode: 0
bits per word: 8
max speed: 500000 Hz (500 KHz)
00 00 00 00 00 00
00 00 00 00 00 00
00 00 00 00 00 00
00 00 00 00 00 00
00 00 00 00 00 00
00 00 00 00 00 00
00 00
But when I passed on command line option '-O' , I received error
message.
address@hidden debug]# ./spidev_test -O
can't set spi mode: Invalid argument
Aborted
'dmesg' shows:
......
spidev spi1.0: setup: unsupported mode bits 2
......
According to source code: driver/spi/spi.c
............................
bad_bits = spi->mode & ~spi->master->mode_bits;
if (bad_bits) {
dev_dbg(&spi->dev, "setup: unsupported mode bits %x\n",
bad_bits);
return -EINVAL;
}
..............................
It seems has something to do with '~spi->master->mode_bits'.
Any comments on this error?
What could be the reason?
Question Two:
Have you ever tried to run 'spidev_test' on dev:ssp1 on Phytec board?
I could not see any 'SPI CLK signal' on PCM-988/GPIO Expansion Board
Patch Field 43E although I was able to run 'spidev_test'.
I am wondering whether it's hardware related or just firmware's problem?
If you can run 'spidev_test' on your phytec board on dev:ssp1, then I
can rule out the possibility of hardware fault.
I am waiting for the arrival of our Hardware debugger TRACE32, which is
the last resort.
Thanks
Regards,
Quentin