Hi Arnd, As explained in previous mail, the IOCTL is actually an inteface to block layer and it is only expecting read/write commands to be sent through the interface.The prrof of it can be seen in write_flag present in the IOCTL structure which indicates the either the command can be read or a write command.
So, can I submit a linux module to the kernel which uses the same mmc_ioc_cmd structure and do all the required processing in my module. To be clear on my requirement: it is To test ALL SD/MMC Commands and NOT just the Read/Write Commands. or should I extend the mmc_test module present in kernel to support testing of individual commands as well ? Can I get some suggestions on what approach to take ? On Thu, Oct 20, 2011 at 12:48 PM, Arnd Bergmann <a...@arndb.de> wrote: > > On Thursday 20 October 2011 10:39:00 Shashidhar Hiremath wrote: > > I am planning to use the existing IOCTL interface for SD/MMC present > > in the kernel. > > Since, the IOCTL interface expects a read/write flag , and the MMC > > IOCTL is actually an interface to block layer I feel without modifying > > the block layer for the support of non-read write commands ,I may not > > be able to test the non-read/write commands through the IOCTL > > interface . > > Is there a way of doing this without modifying block layer ? > > Hi Shashidhar, > > I think there is actually no problem here at all. The block layer simply > passes the ioctl command number and argument to the driver, which can > do anything with it. > > What functionality are you actually looking for? > > Arnd -- regards, Shashidhar Hiremath -- To unsubscribe from this list: send the line "unsubscribe linux-mmc" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
