On Fri, Jan 26, 2024 at 10:23:41PM +0100, Konrad Dybcio wrote: > On 26.01.2024 18:00, Johan Hovold wrote: > > On Fri, Jan 26, 2024 at 08:51:13AM -0800, Bjorn Andersson wrote: > >> On Fri, Jan 26, 2024 at 05:36:10PM +0100, Johan Hovold wrote: > > > >>> Shall you submit a follow-on patch to set the polling delays to zero > >>> for the other thermal zones (cpu, cluster, mem) so that we don't poll > >>> for those? > >> > >> I optimistically interpreted Konrad's response as a promise by him to do > >> so ;) > >> > >> I do like his patch which remove the poll-properties for non-polling > >> mode. Would be nice to not first change the values to 0 and then remove > >> the properties... > > That was my intention as well.. > > > > > No, that should not be an issue as it allows us to get rid of the > > polling without waiting for a binding update which may or may not > > materialise in 6.9-rc1. > > If you really insist, I may do that, but if the thermal guys act on it > quickly and we negotiate an immutable branch, we can simply but atop it, > saving the submitter timeof(patchset), the reviewers timeof(verify), the > build bots timeof(builds) and the applier timeof(pick-build-push).. Why would introduce such a dependency for really no good reason? Submit a patch based on the current binding, then when/if your proposed binding update hits mainline, you can send a *single* patch dropping the parameters from all qualcomm dtsi. Updating the binding is a separate and lower priority task. In fact, it may not even be desirable at all as an omission of adding these parameters could then lead to broken thermal management on platforms where the interrupts do not work. Having an explicit poll-delay of zero at least gives people a reason to think about it when merging a new platform. But again, that's a separate discussion. Don't make this patch depend on that. > > But whoever updates those properties need to do some proper testing to > > make sure that those interrupts really work. > > They seem to, check /proc/interrupts before and after adding an e.g. 45degC > trip point on one of the CPU thermal zones, they fire aplenty. That's not proper testing. Add/enable debugging in the thermal driver and make sure that you trigger precisely once when passing the threshold in both directions. Johan
