Repository navigation
thermal: samsung: gs101_acpm_tmu: Add the Tensor G4 - #86
Conversation
The Tensor G4 (zumapro) reads its SoC temperatures through the same ACPM TMU service as gs101, with a seventh sensor, AUR, after the six gs101 has. Add google,zumapro-acpm-tmu. Signed-off-by: W4HO <87742609+W4HO-ham@users.noreply.github.com>
The Tensor G4 (zumapro) reads its SoC temperatures through the same ACPM TMU service on channel 9, with the same sensor order plus a seventh, AUR. Make the sensor count part of the match data and add google,zumapro-acpm-tmu with seven sensors. Tested on the Pixel 9a: the driver binds the thermal-sensor node under ACPM, the firmware accepts the TMU init, and the big, mid, little and GPU thermal zones register with their cpufreq and devfreq cooling maps and read 46-48 C idle. Signed-off-by: W4HO <87742609+W4HO-ham@users.noreply.github.com>
|
Thanks, this is a tidy extension. I checked it against Google's sources: channel 9 is Since this driver is shared with the Pixel 6 phones, I built Two small requests, neither blocking:
This can land any time and should land before #87, whose DT uses the new compatible. |
The Tensor G4 (zumapro) reads its SoC temperatures through the same ACPM TMU service as gs101: channel 9, the same sensor order (big, mid, little, GPU, ISP, TPU), plus a seventh sensor, AUR. This adds
google,zumapro-acpm-tmuto the binding and togs101_acpm_tmu, with the sensor count now in the match data.Tested on the Pixel 9a (
7.3.0-rc6-omamobile-tegu-s2mpg15-m1-g991042e2eff3-dirty, this driver as a module, the DT'sthermal-sensormoved underacpm_ipcwith the new compatible):This replaces our out-of-tree
tegu-acpm-thermalon the palmtop. The 9a's thermal zones come in a board DT change.checkpatch --strict is clean on both commits, and the driver builds with W=1.
dt_binding_checkforgoogle,gs101-acpm-ipc.yamlreports only "'clocks' is a dependency of 'assigned-clocks'", which the base gives too.