> The reason is that the FIRMWARE is responsible for deciding when > to notify Linux if when a trip point actually trips -- and if the > firmware doesn't know that your trip point has moved, then > its notifications effectively become random, and the user > has been fooled into thinking that the trip point they moved > actually does something, when it may do nothing. I am trying to add this support for the platform DTS, for which the thresholds need to be configured at run time. In this case, the firmware is not involved. Also, the new thresholds are written into the h/w registers. So, everybody down the stack, will know that the trip points have moved. And notifications will be w.r.t the newly written thresholds only. Thanks, Durgadoss -- 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
