nvidia-tegra-modules.git/include/linux/therm_est.h, branch rtss22-ae NVIDIA's kernel modules to support tegra chips (used in Jetson boards) pwm: fan: get regulator name from DT 2021-07-05T17:55:18+00:00 Aaron Tian atian@nvidia.com 2021-06-24T12:50:44+00:00 1a370dd0df9670b9b0f1e347c559609d2a1b18b5 To support platforms that used common power supply for PWM fan, configure regulator name by DT property: regulator_name. Default regulator name is "vdd-fan" when the DT property does not exist. Bug 200743936 Change-Id: I6951e340e5444141a72de5187e3887de49244caf Signed-off-by: Aaron Tian <atian@nvidia.com> Reviewed-on: https://git-master.nvidia.com/r/c/linux-nvidia/+/2549408 Reviewed-by: svcacv <svcacv@nvidia.com> Reviewed-by: svc-mobile-coverity <svc-mobile-coverity@nvidia.com> Reviewed-by: Sandipan Patra <spatra@nvidia.com> Reviewed-by: Bibek Basu <bbasu@nvidia.com> Reviewed-by: mobile promotions <svcmobile_promotions@nvidia.com> Tested-by: mobile promotions <svcmobile_promotions@nvidia.com> GVS: Gerrit_Virtual_Submit 
To support platforms that used common power supply for
PWM fan, configure regulator name by DT property:
regulator_name. Default regulator name is "vdd-fan" when
the DT property does not exist.

Bug 200743936

Change-Id: I6951e340e5444141a72de5187e3887de49244caf
Signed-off-by: Aaron Tian <atian@nvidia.com>
Reviewed-on: https://git-master.nvidia.com/r/c/linux-nvidia/+/2549408
Reviewed-by: svcacv <svcacv@nvidia.com>
Reviewed-by: svc-mobile-coverity <svc-mobile-coverity@nvidia.com>
Reviewed-by: Sandipan Patra <spatra@nvidia.com>
Reviewed-by: Bibek Basu <bbasu@nvidia.com>
Reviewed-by: mobile promotions <svcmobile_promotions@nvidia.com>
Tested-by: mobile promotions <svcmobile_promotions@nvidia.com>
GVS: Gerrit_Virtual_Submit
pwm: fan: fix deadlock due to incorrect locking 2021-05-25T14:24:23+00:00 Sumit Gupta sumitg@nvidia.com 2021-03-24T14:11:56+00:00 2c40a6bc48f6701fe44cb7edadca26f6a40892da Bug 3227296 Bug 200695596 Bug 200728417 Signed-off-by: Sumit Gupta <sumitg@nvidia.com> Change-Id: Ib64915556d285bd798e95da81a261eb2c16b4dab Reviewed-on: https://git-master.nvidia.com/r/c/linux-nvidia/+/2503884 Reviewed-by: svcacv <svcacv@nvidia.com> Reviewed-by: svc-mobile-coverity <svc-mobile-coverity@nvidia.com> Reviewed-by: Bibek Basu <bbasu@nvidia.com> Reviewed-by: mobile promotions <svcmobile_promotions@nvidia.com> GVS: Gerrit_Virtual_Submit Tested-by: Bibek Basu <bbasu@nvidia.com> Tested-by: mobile promotions <svcmobile_promotions@nvidia.com> 
Bug 3227296
Bug 200695596
Bug 200728417

Signed-off-by: Sumit Gupta <sumitg@nvidia.com>
Change-Id: Ib64915556d285bd798e95da81a261eb2c16b4dab
Reviewed-on: https://git-master.nvidia.com/r/c/linux-nvidia/+/2503884
Reviewed-by: svcacv <svcacv@nvidia.com>
Reviewed-by: svc-mobile-coverity <svc-mobile-coverity@nvidia.com>
Reviewed-by: Bibek Basu <bbasu@nvidia.com>
Reviewed-by: mobile promotions <svcmobile_promotions@nvidia.com>
GVS: Gerrit_Virtual_Submit
Tested-by: Bibek Basu <bbasu@nvidia.com>
Tested-by: mobile promotions <svcmobile_promotions@nvidia.com>
thermal: continuous: add custom dt entry support 2021-01-07T10:25:44+00:00 Karthik Mantravadi mkarthik@nvidia.com 2020-12-30T16:04:30+00:00 115da7825ec197d4ed0eb7d84880e8821e69c90f Why? In the case of therm-fan-est driver, the dt entry is not added as part of thermal-zones. Hence, any continuous governor parameters defined under therm-fan-est node will not be considered by the continuous governor while binding to the thermal zone. How? Expose the dt parsing logic in continuous governor driver. This way therm-fan-est driver can call the dt parsing function passing the dt node defined under therm-fan-est dt entry. Bug 200594433 Change-Id: I06f1653209887f674db0636fe6f5803771d46877 Signed-off-by: Karthik Mantravadi <mkarthik@nvidia.com> Reviewed-on: https://git-master.nvidia.com/r/c/linux-nvidia/+/2464743 Tested-by: mobile promotions <svcmobile_promotions@nvidia.com> Reviewed-by: mobile promotions <svcmobile_promotions@nvidia.com> 
Why?
In the case of therm-fan-est driver, the dt entry is not added
as part of thermal-zones. Hence, any continuous governor parameters
defined under therm-fan-est node will not be considered by the
continuous governor while binding to the thermal zone.

How?
Expose the dt parsing logic in continuous governor driver. This way
therm-fan-est driver can call the dt parsing function passing the
dt node defined under therm-fan-est dt entry.

Bug 200594433

Change-Id: I06f1653209887f674db0636fe6f5803771d46877
Signed-off-by: Karthik Mantravadi <mkarthik@nvidia.com>
Reviewed-on: https://git-master.nvidia.com/r/c/linux-nvidia/+/2464743
Tested-by: mobile promotions <svcmobile_promotions@nvidia.com>
Reviewed-by: mobile promotions <svcmobile_promotions@nvidia.com>
pwm: fan: Add support for always on fan 2020-12-25T17:38:32+00:00 Mantravadi Karthik mkarthik@nvidia.com 2020-11-20T07:43:40+00:00 c3cd2b4417ea8767d35b4e04ba9731fb58a2a477 Why? In case of continuous governor, the fan-poweron pwm value is assumed to be at index 1 of pwm values. In case of tmargin the pwm table would be reversed (high to low) and hence the assumption is invalid. How? While calculating the pwm value in the case of continuous governor, add a check if the cooling device is always on fan. If true, for all values of temp, pwm should be calculated instead of assigning 0. Bug 200646929 Change-Id: Ibed572fa2af9f8bd36a4a4cbb472029e21aeb442 Signed-off-by: Mantravadi Karthik <mkarthik@nvidia.com> Reviewed-on: https://git-master.nvidia.com/r/c/linux-nvidia/+/2448826 Tested-by: mobile promotions <svcmobile_promotions@nvidia.com> Reviewed-by: svc-mobile-coverity <svc-mobile-coverity@nvidia.com> Reviewed-by: Bibek Basu <bbasu@nvidia.com> Reviewed-by: mobile promotions <svcmobile_promotions@nvidia.com> GVS: Gerrit_Virtual_Submit 
Why?
In case of continuous governor, the fan-poweron pwm
value is assumed to be at index 1 of pwm values.
In case of tmargin the pwm table would be reversed
(high to low) and hence the assumption is invalid.

How?
While calculating the pwm value in the case of
continuous governor, add a check if the cooling device
is always on fan. If true, for all values of temp,
pwm should be calculated instead of assigning 0.

Bug 200646929

Change-Id: Ibed572fa2af9f8bd36a4a4cbb472029e21aeb442
Signed-off-by: Mantravadi Karthik <mkarthik@nvidia.com>
Reviewed-on: https://git-master.nvidia.com/r/c/linux-nvidia/+/2448826
Tested-by: mobile promotions <svcmobile_promotions@nvidia.com>
Reviewed-by: svc-mobile-coverity <svc-mobile-coverity@nvidia.com>
Reviewed-by: Bibek Basu <bbasu@nvidia.com>
Reviewed-by: mobile promotions <svcmobile_promotions@nvidia.com>
GVS: Gerrit_Virtual_Submit
thermal: pwm-fan: Add support for tmargin 2020-12-17T19:40:05+00:00 Mantravadi Karthik mkarthik@nvidia.com 2020-12-16T18:09:53+00:00 22fd87123c4a31566d621efd4ab007e481a0e937 Why? Tmargin feature uses reverse pwm mapping in DT. The current rru/rrd calculation logic assumes that the pwm table is in ascending order. In the case of tmargin, the pwm table is given in descending order. How? pwm fan dt node should have a "use_tmargin" identifier similar to therm_fan_est dt node. This dt entry switches the logic in rru/rrd calculation Bug 200646929 Change-Id: I2042aaff5347553202212c6b69f707511bb9b7dd Signed-off-by: Mantravadi Karthik <mkarthik@nvidia.com> Reviewed-on: https://git-master.nvidia.com/r/c/linux-nvidia/+/2460881 Tested-by: Rajkumar Kasirajan <rkasirajan@nvidia.com> Tested-by: mobile promotions <svcmobile_promotions@nvidia.com> Reviewed-by: svc-mobile-coverity <svc-mobile-coverity@nvidia.com> Reviewed-by: Rajkumar Kasirajan <rkasirajan@nvidia.com> Reviewed-by: Bibek Basu <bbasu@nvidia.com> Reviewed-by: mobile promotions <svcmobile_promotions@nvidia.com> GVS: Gerrit_Virtual_Submit 
Why?
Tmargin feature uses reverse pwm mapping in DT. The current
rru/rrd calculation logic assumes that the pwm table is in
ascending order. In the case of tmargin, the pwm table is
given in descending order.

How?
pwm fan dt node should have a "use_tmargin" identifier similar
to therm_fan_est dt node. This dt entry switches the logic in
rru/rrd calculation

Bug 200646929

Change-Id: I2042aaff5347553202212c6b69f707511bb9b7dd
Signed-off-by: Mantravadi Karthik <mkarthik@nvidia.com>
Reviewed-on: https://git-master.nvidia.com/r/c/linux-nvidia/+/2460881
Tested-by: Rajkumar Kasirajan <rkasirajan@nvidia.com>
Tested-by: mobile promotions <svcmobile_promotions@nvidia.com>
Reviewed-by: svc-mobile-coverity <svc-mobile-coverity@nvidia.com>
Reviewed-by: Rajkumar Kasirajan <rkasirajan@nvidia.com>
Reviewed-by: Bibek Basu <bbasu@nvidia.com>
Reviewed-by: mobile promotions <svcmobile_promotions@nvidia.com>
GVS: Gerrit_Virtual_Submit
therm-fan-est: Add support for Tmargin to drive fan 2020-09-15T15:39:29+00:00 mkarthik mkarthik@nvidia.com 2020-06-17T12:01:11+00:00 f9d1658833bbd2dfd5b24bb8cfff4da88db658ce Why? Tmargin method of fan control allows multiple groups of therma-fan-est devices temperatures to be considered for the fan control algorithm/fan curve. The limitation of the existing max temp algorithm in therm-fan-est driver is that devices with different fan curves cannot be accomodated in the driver. In case, there are multple fan curves, the device which has the steepest curve wins the algoritm. Hence, taking the temperatures as a reference from their respective critical temperatures and using that value to drive the fan will help in accomodating both the devices' fan curves. How? * Calculate the effective crit temp of all the thermal zones during probe. * In the polling cycles, calculate the effective temperatures of the individual groups and use the tmargin formula to calculate the current temperature. * Since the Tmargin temp trip values are in reverse order, we need to use the reverse order in the pwm-fan dt profile. * The hysterysis is subtracted from the temp in cooling scenario to avoid frequent switching at trip temps. Since the tmargin trip values are taken in the decending order, hysterysis temps in dt should be given as negative values. Bug 200627962 Change-Id: Ideba4bfdb3d3306d1b4aff15093bcfac13d7bb86 Signed-off-by: Mantravadi Karthik <mkarthik@nvidia.com> Reviewed-on: https://git-master.nvidia.com/r/c/linux-nvidia/+/2362354 Reviewed-by: automaticguardword <automaticguardword@nvidia.com> Reviewed-by: Rajkumar Kasirajan <rkasirajan@nvidia.com> Reviewed-by: Bibek Basu <bbasu@nvidia.com> Reviewed-by: mobile promotions <svcmobile_promotions@nvidia.com> Tested-by: Rajkumar Kasirajan <rkasirajan@nvidia.com> Tested-by: mobile promotions <svcmobile_promotions@nvidia.com> GVS: Gerrit_Virtual_Submit 
Why?
Tmargin method of fan control allows multiple groups of
therma-fan-est devices temperatures to be considered for
the fan control algorithm/fan curve. The limitation of the
existing max temp algorithm in therm-fan-est driver is that
devices with different fan curves cannot be accomodated in
the driver. In case, there are multple fan curves, the device
which has the steepest curve wins the algoritm. Hence, taking
the temperatures as a reference from their respective critical
temperatures and using that value to drive the fan will help in
accomodating both the devices' fan curves.

How?
* Calculate the effective crit temp of all the thermal zones
  during probe.
* In the polling cycles, calculate the effective temperatures
  of the individual groups and use the tmargin formula to
  calculate the current temperature.
* Since the Tmargin temp trip values are in reverse order, we
  need to use the reverse order in the pwm-fan dt profile.
* The hysterysis is subtracted from the temp in cooling scenario
  to avoid frequent switching at trip temps. Since the tmargin
  trip values are taken in the decending order, hysterysis temps
  in dt should be given as negative values.

Bug 200627962

Change-Id: Ideba4bfdb3d3306d1b4aff15093bcfac13d7bb86
Signed-off-by: Mantravadi Karthik <mkarthik@nvidia.com>
Reviewed-on: https://git-master.nvidia.com/r/c/linux-nvidia/+/2362354
Reviewed-by: automaticguardword <automaticguardword@nvidia.com>
Reviewed-by: Rajkumar Kasirajan <rkasirajan@nvidia.com>
Reviewed-by: Bibek Basu <bbasu@nvidia.com>
Reviewed-by: mobile promotions <svcmobile_promotions@nvidia.com>
Tested-by: Rajkumar Kasirajan <rkasirajan@nvidia.com>
Tested-by: mobile promotions <svcmobile_promotions@nvidia.com>
GVS: Gerrit_Virtual_Submit
thermal: pwm-fan: Add tach feedback support 2020-09-02T13:24:37+00:00 mkarthik mkarthik@nvidia.com 2020-07-01T13:26:10+00:00 d489e9eab5e854ca996753f7fe314f1337e1308c Why? The current implementation of the pwm-fan driver only writes a pwm value to the HW when requested. There is no tachometer rpm read back to check if the thermal performance is as expected. This change aims to add the rpm offsets necessary to maintain the desired fan rpm. How? A new work queue is added which gets the pwm fan rpm and checks the same for a rpm diff tolerance value. In case the tolerance value is exceeded, the next pwm corresponding to the next rpm ramp index is written to the pwm controller. Bug 200646929 Change-Id: Iff780a7edf98ca457ace10079149925adf06189d Signed-off-by: Mantravadi Karthik <mkarthik@nvidia.com> Reviewed-on: https://git-master.nvidia.com/r/c/linux-nvidia/+/2369412 Tested-by: Rajkumar Kasirajan <rkasirajan@nvidia.com> Tested-by: mobile promotions <svcmobile_promotions@nvidia.com> Reviewed-by: Rajkumar Kasirajan <rkasirajan@nvidia.com> Reviewed-by: Bibek Basu <bbasu@nvidia.com> Reviewed-by: Sandipan Patra <spatra@nvidia.com> Reviewed-by: mobile promotions <svcmobile_promotions@nvidia.com> GVS: Gerrit_Virtual_Submit 
Why?
The current implementation of the pwm-fan driver only writes
a pwm value to the HW when requested. There is no tachometer
rpm read back to check if the thermal performance is as
expected. This change aims to add the rpm offsets necessary
to maintain the desired fan rpm.

How?
A new work queue is added which gets the pwm fan rpm and checks
the same for a rpm diff tolerance value. In case the tolerance
value is exceeded, the next pwm corresponding to the next rpm
ramp index is written to the pwm controller.

Bug 200646929

Change-Id: Iff780a7edf98ca457ace10079149925adf06189d
Signed-off-by: Mantravadi Karthik <mkarthik@nvidia.com>
Reviewed-on: https://git-master.nvidia.com/r/c/linux-nvidia/+/2369412
Tested-by: Rajkumar Kasirajan <rkasirajan@nvidia.com>
Tested-by: mobile promotions <svcmobile_promotions@nvidia.com>
Reviewed-by: Rajkumar Kasirajan <rkasirajan@nvidia.com>
Reviewed-by: Bibek Basu <bbasu@nvidia.com>
Reviewed-by: Sandipan Patra <spatra@nvidia.com>
Reviewed-by: mobile promotions <svcmobile_promotions@nvidia.com>
GVS: Gerrit_Virtual_Submit
Thermal: support feature: pwm_period independent with fan_pwm_max 2019-05-29T20:44:11+00:00 Taylor Xiao txiao@nvidia.com 2019-05-27T07:42:45+00:00 8a113ad5ac552c8e34f650a7a5fd4904aeffd25d Pwm_period needn't keep the same with fan_pwm_max now, precision_multiplier multiply with constant 100 and divide by constant 100 when caculating pwm duty. Bug 200519087 Change-Id: Ibc684289479ee850171ef8860b577457077e7b2b Signed-off-by: Taylor Xiao <txiao@nvidia.com> Reviewed-on: https://git-master.nvidia.com/r/2125786 GVS: Gerrit_Virtual_Submit Reviewed-by: Martin Gao <marting@nvidia.com> Reviewed-by: Daniel Fu <danifu@nvidia.com> Reviewed-by: mobile promotions <svcmobile_promotions@nvidia.com> Tested-by: mobile promotions <svcmobile_promotions@nvidia.com> 
Pwm_period needn't keep the same with fan_pwm_max now, precision_multiplier
multiply with constant 100 and divide by constant 100 when caculating pwm duty.

Bug 200519087

Change-Id: Ibc684289479ee850171ef8860b577457077e7b2b
Signed-off-by: Taylor Xiao <txiao@nvidia.com>
Reviewed-on: https://git-master.nvidia.com/r/2125786
GVS: Gerrit_Virtual_Submit
Reviewed-by: Martin Gao <marting@nvidia.com>
Reviewed-by: Daniel Fu <danifu@nvidia.com>
Reviewed-by: mobile promotions <svcmobile_promotions@nvidia.com>
Tested-by: mobile promotions <svcmobile_promotions@nvidia.com>
Thermal: pwm-fan: support continuous fan control feature 2019-05-09T21:43:39+00:00 Taylor Xiao txiao@nvidia.com 2019-03-21T16:45:53+00:00 13e45af50923eca40d2ccb207003b32742e51508 Update for pwm-fan: Cooling device ops "set_cur_state" will set its second parameter as target pwm directly, because continuous fan pwm dont ramp step by step but point to point smoothly. Bug 2540031 Change-Id: I2f5bbddb4ea82ab655f18067812705696f7f7601 Signed-off-by: Taylor Xiao <txiao@nvidia.com> Reviewed-on: https://git-master.nvidia.com/r/2113583 Reviewed-by: Daniel Fu <danifu@nvidia.com> Reviewed-by: mobile promotions <svcmobile_promotions@nvidia.com> Tested-by: mobile promotions <svcmobile_promotions@nvidia.com> 
Update for pwm-fan:
Cooling device ops "set_cur_state" will set its second parameter
as target pwm directly, because continuous fan pwm dont ramp step
by step but point to point smoothly.

Bug 2540031

Change-Id: I2f5bbddb4ea82ab655f18067812705696f7f7601
Signed-off-by: Taylor Xiao <txiao@nvidia.com>
Reviewed-on: https://git-master.nvidia.com/r/2113583
Reviewed-by: Daniel Fu <danifu@nvidia.com>
Reviewed-by: mobile promotions <svcmobile_promotions@nvidia.com>
Tested-by: mobile promotions <svcmobile_promotions@nvidia.com>
include: therm_est: remove thermal_sensors.h 2018-06-27T14:30:52+00:00 Wei Ni wni@nvidia.com 2018-06-25T10:46:28+00:00 c58a1702dc63d2bf1c2cecd1c4846f16ea445b05 Remove including thermal_sensors.h, because we no longer use it. Bug 2111573 Change-Id: I457872ca167e30d1a090384fd9b3c5b2e4a0d1f5 Signed-off-by: Wei Ni <wni@nvidia.com> Reviewed-on: https://git-master.nvidia.com/r/1760492 GVS: Gerrit_Virtual_Submit Reviewed-by: Terry Wang <terwang@nvidia.com> Reviewed-by: Srikar Srimath Tirumala <srikars@nvidia.com> Reviewed-by: Bitan Biswas <bbiswas@nvidia.com> Reviewed-by: mobile promotions <svcmobile_promotions@nvidia.com> Tested-by: mobile promotions <svcmobile_promotions@nvidia.com> 
Remove including thermal_sensors.h, because we
no longer use it.

Bug 2111573

Change-Id: I457872ca167e30d1a090384fd9b3c5b2e4a0d1f5
Signed-off-by: Wei Ni <wni@nvidia.com>
Reviewed-on: https://git-master.nvidia.com/r/1760492
GVS: Gerrit_Virtual_Submit
Reviewed-by: Terry Wang <terwang@nvidia.com>
Reviewed-by: Srikar Srimath Tirumala <srikars@nvidia.com>
Reviewed-by: Bitan Biswas <bbiswas@nvidia.com>
Reviewed-by: mobile promotions <svcmobile_promotions@nvidia.com>
Tested-by: mobile promotions <svcmobile_promotions@nvidia.com>