On 06/05/2012 09:56 AM, E Layec wrote: > You will find in attached file our current source code.
One thing that jumps out at me is the -EINVAL as .bus_num and .irq in your board file. IRQ is just passed through to the driver (so it's likely not causing _this_ problem), but .bus_num may be causing you a problem. If you look in spi.h, bus_num is a u16, so -EINVAL is never valid for that field. What goes in that field is the SPI bus your device is connected to. On the Beagle Bone, SPI bus number 2 is the one I'm using, and it's labeled SPI1 in the Beagle Bone SRM. Also, I assume that you are checking that spi1_init() is actually getting called. On the board file, look at my patch again (from May 23). That's really all you need to do in the board file. I literally just changed "spidev" to "mrf24j40" to make it start using my driver. You seem to be doing similar things (except for .bus_num). On the driver side, spi_register_driver() with your spi_driver struct should be all that's needed for the SPI subsystem to probe your driver (if your driver is loaded manually with modprobe). Like I said before, setting up the MODULE_DEVICE_TABLE will make the module load automatically. Alan. ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ Linux-zigbee-devel mailing list Linux-zigbee-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/linux-zigbee-devel
