On Tue, Sep 11, 2012 at 05:07:29AM +0000, R, Durgadoss wrote: > Hi Jean/Guenter, > > In thermal_sys.c we have a CONFIG_THERMAL_HWMON. > If enabled, this creates sysfs nodes for thermal zones inside > hwmon. Do we need this functionality inside thermal_sys.c ? > Or is it Ok to remove this ? > > I wanted to know your opinion before submitting a patch. > Hi Durga, question is really what would replace it. From the plumbers conference, I understand the idea was that drivers would have to register to both hwmon and the thermal subsystem. Is that going to happen ? Second question is why you want to remove it in the first place. It only matters for drivers which _do_ register with both hwmon and thermal - in other words, none today. This case could be handled with a new thermal API, which would specifically exclude hwmon registration. My concern at this point with the thermal plans is that you might end up duplicating a bunch of temperature sensor drivers in the thermal subsystem. And if drivers are to support both subsystems, you would end up duplicating a lot of common code in drivers which support both the thermal subsystem and hwmon. I personally don't think that is a good idea, and would prefer a more unified approach where it would be possible to register a hwmon temperature sensor driver with the thermal subsystem. Since that would be quite limited in scope, it might not be too difficult to define an API for it which should both simplify hwmon temperature sensor drivers and provide an interface to the thermal subsystem. Thanks, Guenter -- To unsubscribe from this list: send the line "unsubscribe linux-acpi" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
