It would be helpful if you explained what it is you are trying to do and then we will provide suggestions on how to proceed.
Regards, John > On Jan 4, 2016, at 1:34 AM, [email protected] wrote: > > Hello, > I saw your publish question about using SPI in a kernel module. I kind of > stucking in this problem as well. > So i wonder if you find a solution? > > I know it's too late to ask, but i hope i'm lucky to get some feedback from > you. > > Regards, > Cheng > > Le lundi 28 juillet 2014 16:00:59 UTC+2, Nils a écrit : > Hello, > > I'm currently working on a kernel module which needs to communicate via SPI > to an external microchip. > > I used the cape manager to enable SPI. The device is accessible through > /dev/spidev1.0. > But since it's a kernel module, I guess it's not recommended to access files > via sys_open()? > > Another approach I found would be adding a struct to > arch/arm/mach-omap2/board-am335xevm.c and then use spi_register_driver() in > my kernel module. But in my kernel sources (3.8.13) this file doesn't exist. > > What would be the right way to use SPI in my kernel module? > > Regards, > Nils > > -- > For more options, visit http://beagleboard.org/discuss > <http://beagleboard.org/discuss> > --- > You received this message because you are subscribed to the Google Groups > "BeagleBoard" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected] > <mailto:[email protected]>. > For more options, visit https://groups.google.com/d/optout > <https://groups.google.com/d/optout>. -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups "BeagleBoard" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
