On Tue, Feb 22, 2011 at 10:22:11AM +0900, Tomoya MORINAGA wrote: > Hi, > > issue: after reload the spi module, it can't do SPI communication. > > We have faced issue when execute the following command. > insmod xxx.ko(Then, /dev/spidev0.0 is created with success) > rmmod xxx.ko (Then, /dev/spidev0.0 is deleted with success) > insmod xxx.ko(Then, /dev/spidev0.0 is created, however, below error message > is showed) > > 0000:02:0c.1: registered master spi0 > 0000:02:0c.1: chipselect 0 already in use > 0000:02:0c.1: can't create new device for spidev > > Do you have any information about the above ?
Nope, I'm not an expert on that driver, but it definitely looks like a bug! :-) It *looks* like the spi_device slaves are not getting unregistered when the driver unloads. That's where I would start investigating. The bug could either be in core code or the device driver itself, but I don't know without digging deeper. g. ------------------------------------------------------------------------------ Free Software Download: Index, Search & Analyze Logs and other IT data in Real-Time with Splunk. Collect, index and harness all the fast moving IT data generated by your applications, servers and devices whether physical, virtual or in the cloud. Deliver compliance at lower cost and gain new business insights. http://p.sf.net/sfu/splunk-dev2dev _______________________________________________ spi-devel-general mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/spi-devel-general
