>>>>> "Arnd" == Arnd Bergmann <arnd@xxxxxxxx> writes: Arnd> Looking through what other drivers do, I've found a couple of Arnd> patterns now. n particular, most use the SG_IO ioctl to pass down Arnd> commands from user space into a device specific command Arnd> queue. Have you looked at that interface in the past to see if it Arnd> would fit your use case? Arnd> There is also a 'bsg' API that some drivers implement, which I Arnd> think would be another alternative. Arnd> Could any of the SCSI experts comment on what they expect a driver Arnd> to use out of those three alternatives (if any): My preference is that if you want to expose any information that a user or admin would care about, put it in sysfs where it is easily accessible and can be scripted. For things that need to directly send commands to the hardware (to configure vendor specific settings or inspect parameters for development purposes) use the sg or bsg interfaces like we do for both ATA and SCSI. bsg is newer and supports more features like bidirectional commands. But for this particular use case I don't think it offers any particular advantages over SG_IO. Both interfaces take the same descriptors so it really doesn't matter much. See: http://sg.danny.cz/sg/ -- Martin K. Petersen Oracle Linux Engineering -- To unsubscribe from this list: send the line "unsubscribe linux-arm-msm" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
