<table cellspacing="0" cellpadding="0" border="0" ><tr><td valign="top" style="font: inherit;">I expected to receive a call to probe as soon as i register an spi_driver, which doesn't<br>seem to happen. If my driver must be already registered before the machine init then it<br>can't be a module, it must be inside the kernel, which looks really strange.<br><br>What I don't understand is where the spi_device instance is created, and where. Looks like<br>it's appearing from nowhere. But even more strange is the fact that spidev only registers<br>its own spi_driver and according to other people it works, so the only explanation for me<br>is that it can only be done as long as it's part of the kernel. But even being part of the<br>kernel spi_driver's register should be done before the machine init, which makes no sense<br>imho.<br><br>Regards<br><br><br>--- El <b>dom, 27/6/10, Mykhail Lodygin <i><mishal@softerra.com></i></b> escribió:<br><blockquote
style="border-left: 2px solid rgb(16, 16, 255); margin-left: 5px; padding-left: 5px;"><br>De: Mykhail Lodygin <mishal@softerra.com><br>Asunto: Re: Using SPI in a kernel module<br>Para: "Alfredo Quesada Sánchez" <freddy2_es@yahoo.com><br>CC: linux-arm-kernel@lists.infradead.org<br>Fecha: domingo, 27 de junio, 2010 23:26<br><br><div id="yiv1321449321">
<pre><big><big><big><big><small>Invocation sequence is the same as described</small> <small>in</small> </big>ek_spi_devices. So since there is no YOUR driver in ek_spi_devices - i can't say when it would be called - for now - never.<br>which device? - you define it by setting .chip_select, i believe. <br></big></big></big></pre>
You could see all calls - just set verbosity to debug function in the
configuration.<br>
<br>
</div></blockquote></td></tr></table><br>