Hi, I am trying to get my TFT LCD (LTV350QV) working on my embedded platform (uses the Simtec s3c2440 module). I have managed to get the framebuffer activated but the LCD also needs to be initialised via a SPI interface and this is where I am battling at the moment. I have obtained some code that has been used with the LTV350QV LCD on another mach and I am trying to adapt it to work on my mach. At the moment I am trying to understand the spi device driver framework. I have read the spi documentation in the kernel and I understand how you should declare your slave using the spi_board_info structure and the spi_register_board_info(). I also understand how this can be matched to a protocol driver with the same name (my_spi_board_info.modalias). However, I do not understand how the protocol driver is bound to a controller driver that supports the actual SPI hardware interface. My protocol driver's spi_register_driver() works OK but my mod_probe() never gets called and it is here that I initialise my slave device (LTV350QV TFT LCD). It would seem that the protocol driver should associate itself with one of the hardware controller drivers, but I cannot see how this is done. Can anyone help ? Mark -- Kernelnewbies: Help each other learn about the Linux kernel. Archive: http://mail.nl.linux.org/kernelnewbies/ FAQ: http://kernelnewbies.org/faq/
