Hi, Lucas, As you have mentioned thermal.c, I think you are using ACPI thermal control on your platform, right? trip_point_?_hyst files are created by thermal core, if the platform thermal driver supports hysteresis, and ACPI thermal driver, which is used in your case, does not support hysteresis. On 二, 2016-07-26 at 23:01 +0200, Lucas Levrel wrote: > Hi (once more), > > Isn't there anyone who could spare a few minutes to guide me on this? > > I found some references to trip_point_?_hyst files, which seem > promising, > but they aren't there in my sysfs, and I cannot create them (e.g. > "touch: > cannot touch `trip_point_4_hyst': No such file or directory"). > > Thanks. > > Lucas Levrel > > Le 22 juillet 2016, Lucas Levrel a écrit : > > > > > Hi, > > > > Is this the right place to request for help and/or information > > about thermal > > zones? If not, please point me to the right place. > > > > I browsed through thermal.c but couldn't find an answer to my > > question (it > > goes without saying I'm not an expert), namely: > > how are trip point temperatures set at boot, ACPI thermal driver gets the trip point temperature information from ACPI tables. > > and how are they reset when > > crossed? > > Usually, ACPI trip point is not reset when crossed, but it does have granularity, which determines when to generate a temperature change notification. Say, for a platform that the trip point temperature is 50C, and granularity is 5C, when the ACPI thermal driver receives a notification at 50C, it starts to spin the fan. Then next time when the ACPI thermal driver gets a temperature change notification, the temperature is either 55C, which means we need to take further action to cool the system, or the temperature is 45C and we can turn off the fan. In some cases, the trip point may get reset. You can refer to section 11.1.2 in ACPI spec 6.1. IN this case, a trip point change notification will be sent to thermal driver, and ACPI thermal driver will re- evaluate the trip point control methods to get new trip point temperature. But AFAICS, this is really rare. > > I'm aiming at changing the temperatures at which the fan starts and > > stops. > > The kernel parameter thermal.act=XXX did change the "fan on" > > temperature, but > > not the "fan off" one. I expected the hysteresis T(on)-T(off) to be > > constant, > > and thus I thought T(off) would raise as much as I raised T(on), > > but this is > > not the case. > > Dynamic trip point can only be supported by platform thermal design. Specifying such values in userspace does not make sense, because it's not guaranteed that the thermal driver can get notification upon the values you specified, thus it would screw up the thermal control entirely. thanks, rui > > Any help is greatly appreciated. > > > > Lucas Levrel > -- > 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 -- 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
