From mboxrd@z Thu Jan 1 00:00:00 1970 From: mishal@softerra.com (Mykhail Lodygin) Date: Mon, 28 Jun 2010 01:30:24 +0300 Subject: Using SPI in a kernel module In-Reply-To: <385275.91392.qm@web33802.mail.mud.yahoo.com> References: <385275.91392.qm@web33802.mail.mud.yahoo.com> Message-ID: <4C27D100.2030405@softerra.com> To: linux-arm-kernel@lists.infradead.org List-Id: linux-arm-kernel.lists.infradead.org On 06/28/2010 12:47 AM, Alfredo Quesada S?nchez wrote: > I expected to receive a call to probe as soon as i register an > spi_driver, which doesn't > seem to happen. > of course , you havn't fullfill the appropriate structure fields. > If my driver must be already registered before the machine init then it > can't be a module, it must be inside the kernel, > Why do you think so? spi works for many years - your driver is not the first and definitely not the last, please exame other drivers - you will see how to register. > > What I don't understand is where the spi_device instance is created, > and where. Looks like > it's appearing from nowhere. > come on! drivers/spi/spi.c spi_alloc_device > But even more strange is the fact that spidev only registers > its own spi_driver and according to other people it works, so the only > explanation for me > is that it can only be done as long as it's part of the kernel. But > even being part of the > kernel spi_driver's register should be done before the machine init, > which makes no sense > imho. > Sorry but again - why do you think so? please look at several drivers which utilize spi_driver structure carefully - and you'll see how to do it yourself. > Regards > > > --- El *dom, 27/6/10, Mykhail Lodygin //* escribi?: > > > De: Mykhail Lodygin > Asunto: Re: Using SPI in a kernel module > Para: "Alfredo Quesada S?nchez" > CC: linux-arm-kernel at lists.infradead.org > Fecha: domingo, 27 de junio, 2010 23:26 > > Invocation sequence is the same as described in 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. > which device? - you define it by setting .chip_select, i believe. > > > You could see all calls - just set verbosity to debug function in > the configuration. > > -------------- next part -------------- An HTML attachment was scrubbed... URL: