thermal: samsung: import exynos7870 TMU driver for a3y17lte
The a3y17lte thermal management is based on the TEM1455X TMU block
driving three sensors (CPUCL0, CPUCL1, G3D) configured from the
tmuctrl nodes in exynos7870-a3y17lte_common.dtsi, with per-trip
throttling levels, cpufreq/gpufreq cooling tables and the cluster1
hotplug throttle.
Taken from samsungexynos7870/android_kernel_samsung_exynos7870
lineage-20 drivers/thermal/samsung (exynos_tmu.c, exynos_tmu_data.c
and the exynos thermal common layer) plus its ipa.h, exynos-ss.h and
soc/samsung/cpufreq.h headers, placed in a 7870 subdirectory under
the new EXYNOS_THERMAL_CORE option because this tree's EXYNOS_THERMAL
driver only supports the Exynos9820 TME1010 block and both drivers
register the same "exynos-tmu" platform driver name (the 7870 one
is renamed "exynos7870-tmu"). The cpufreq_cooling_get_level()
export is declared in linux/cpu_cooling.h.
Adapted to the 4.14 thermal API:
- cpufreq cooling devices are registered per cpufreq policy (with a
held policy reference) instead of per cpumask, and the registration
is skipped with a warning when no cpufreq driver is present instead
of deferring the probe forever
- the suspend/resume temperature hint goes through the cooling
device set_cur_temp operation instead of the
cpufreq_set_cur_temp()/gpufreq_set_cur_temp() global hooks
- thermal_zone_bind_cooling_device() gets the new direction argument
- the cluster cpufreq policy clamp in the bind callback looks up the
cluster's first cpu via cpu_topology instead of the 3.18 cluster id
convention and degrades to a warning without a cpufreq driver
The a3y17lte thermal management is based on the TEM1455X TMU block
driving three sensors (CPUCL0, CPUCL1, G3D) configured from the
tmuctrl nodes in exynos7870-a3y17lte_common.dtsi, with per-trip
throttling levels, cpufreq/gpufreq cooling tables and the cluster1
hotplug throttle.
Taken from samsungexynos7870/android_kernel_samsung_exynos7870
lineage-20 drivers/thermal/samsung (exynos_tmu.c, exynos_tmu_data.c
and the exynos thermal common layer) plus its ipa.h, exynos-ss.h and
soc/samsung/cpufreq.h headers, placed in a 7870 subdirectory under
the new EXYNOS_THERMAL_CORE option because this tree's EXYNOS_THERMAL
driver only supports the Exynos9820 TME1010 block and both drivers
register the same "exynos-tmu" platform driver name (the 7870 one
is renamed "exynos7870-tmu"). The cpufreq_cooling_get_level()
export is declared in linux/cpu_cooling.h.
Adapted to the 4.14 thermal API:
- cpufreq cooling devices are registered per cpufreq policy (with a
held policy reference) instead of per cpumask, and the registration
is skipped with a warning when no cpufreq driver is present instead
of deferring the probe forever
- the suspend/resume temperature hint goes through the cooling
device set_cur_temp operation instead of the
cpufreq_set_cur_temp()/gpufreq_set_cur_temp() global hooks
- thermal_zone_bind_cooling_device() gets the new direction argument
- the cluster cpufreq policy clamp in the bind callback looks up the
cluster's first cpu via cpu_topology instead of the 3.18 cluster id
convention and degrades to a warning without a cpufreq driver
Offtopic Lore 2.0 TDI CBAB
Photo
gore "😭" win emoji
Forwarded from Colin Chapman
I have downloaded two Eylem Aroma Rom zipp files one is 1.74gb and other is 1.08gb Could you advise
『 ⌥ 』 ℤ𝔾𝕏 // #𝕿𝖍𝖊𝕽𝖊𝖙𝖚𝖗𝖓
Photo
probably cuz it got sent to group?
Offtopic Lore 2.0 TDI CBAB
probably cuz it got sent to group?
no
Tg doesn't add a counter for msgs forwarded to a group thats linked to the channel
Tg doesn't add a counter for msgs forwarded to a group thats linked to the channel