Hi, ----- Original Message ----- > From: "Shashidhar Hiremath" <shashidharh@xxxxxxxxxxxxxxx> > To: "Chris Ball" <cjb@xxxxxxxxxx>, "J Freyensee" <james_p_freyensee@xxxxxxxxxxxxxxx>, "John Calixto" > <john.calixto@xxxxxxxxxxxxxx>, linux-mmc@xxxxxxxxxxxxxxx > Sent: Thursday, October 20, 2011 1:09:00 AM > Subject: A question on IOCTL interface for MMC > > Hi , > 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 . Unsure what you mean. Certainly it's up to you how to handle the data you pass to the ioctl(). The "in" and "out" just says whether you are passing data to the kernel or expecting something back, no more - no less. What are you actually trying to do? What are you trying to expose or control through an ioctl? A -- To unsubscribe from this list: send the line "unsubscribe linux-mmc" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
