Hi Jonathan/Michael, > I'd say this is just the wrong way round: > Design goal should be to keep application as is and just load another > driver on H/W change + changing access path in some config file. I get that. I am assuming that in order to get the sht15 driver working on my platform, all i need to do is populate the correct GPIO's in the platform device structure. Any idea as to how to do that , i mean where(which file in the source) does the actual platform device strucutre's pdata get populated. What would be the optimal method to tie it to the userspace. Can i add an ioctl to the sht15 driver and export it for the userspace driver to use. Appreciate your comments. Thanks, Alfred. -- To unsubscribe from this list: send the line "unsubscribe linux-i2c" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
