On Fri, Feb 14, 2014 at 10:06:01AM +0100, Richard Cochran wrote: > On Thu, Feb 13, 2014 at 05:39:57PM -0500, David Miller wrote: > > If you don't like it, be angry at whoever added this module parameter > > in the first place, not me. Module parameters are 99 times out of 100 > > not the right way to configure something, really. > > Yeah, I am the one, be angry with me. Look back at this driver, there was in fact a good reason to have at least the "calibration" pin as a module parameter. When using multiple phyters, together they should act as one clock. The driver does this automatically during the probe method, and so it needs to know which pin to use well before user space is ready. However, the other pin functions could have waited for user space configuration, but I had just lumped them all together. Going forward, I think the get/setpin ioctl will work fine both for this driver (without changing the legacy module parameters) and for future ones. Thanks, Richard -- To unsubscribe from this list: send the line "unsubscribe devicetree" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
