On 27/11/2014 at 11:31:36 -0800, Guenter Roeck wrote : > On 11/27/2014 11:06 AM, Boris Brezillon wrote: > >>As for DT not supposed to be used for configuration, that is really a > >>tricky problem which is hard to solve. I seem to recall, though, that > >>it may be now acceptable under certain conditions. A module parameter > >>might be easier. > > > >I'm not a big fan of passing these kind information through module > >params, cause it's kind of hard to assign parameters when you have > >multiple device instances (it might not be applicable to watchdog > >devices though). > >Moreover, adding more module parameters will just expand the cmdline > >and make it less and less readable. > > > Agreed but ... > > >Anyway, this is not my call to make :-). > > it isn't us who restrict the DT scope (though of course timeout-sec > _is_ configuration, but that was before things got more restrictive). > My understanding is that it is OK if this is something you need at boot time versus something you can configure from userspace later. But I'm not a DT expert ;) -- Alexandre Belloni, Free Electrons Embedded Linux, Kernel and Android engineering http://free-electrons.com -- To unsubscribe from this list: send the line "unsubscribe linux-watchdog" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
