nvidia-tegra-modules.git/drivers/misc, branch gpu-paging NVIDIA's kernel modules to support tegra chips (used in Jetson boards) misc: eventlib: fix building kernel with gcc 11 2021-11-30T18:09:24+00:00 Igor Nabirushkin inabirushkin@nvidia.com 2021-11-16T07:52:51+00:00 6e0deb8f01a2102a4fb7384e79142e989eddab1f Eventlib: Add local implementation of __sync_fetch_and_or and __sync_fetch_and_and builtin functions. This fixes eventlib build errors with GCC 11. Bug 3375927 Change-Id: I1a8ed9dcc383242a5fa125df3cfb220c867adaf3 Signed-off-by: Igor Nabirushkin <inabirushkin@nvidia.com> Reviewed-on: https://git-master.nvidia.com/r/c/linux-nvidia/+/2629717 Reviewed-by: Bibek Basu <bbasu@nvidia.com> Reviewed-by: mobile promotions <svcmobile_promotions@nvidia.com> GVS: Gerrit_Virtual_Submit Tested-by: mobile promotions <svcmobile_promotions@nvidia.com> 
Eventlib: Add local implementation of __sync_fetch_and_or and
__sync_fetch_and_and builtin functions.
This fixes eventlib build errors with GCC 11.

Bug 3375927

Change-Id: I1a8ed9dcc383242a5fa125df3cfb220c867adaf3
Signed-off-by: Igor Nabirushkin <inabirushkin@nvidia.com>
Reviewed-on: https://git-master.nvidia.com/r/c/linux-nvidia/+/2629717
Reviewed-by: Bibek Basu <bbasu@nvidia.com>
Reviewed-by: mobile promotions <svcmobile_promotions@nvidia.com>
GVS: Gerrit_Virtual_Submit
Tested-by: mobile promotions <svcmobile_promotions@nvidia.com>
nct1008: Check return value. 2021-08-13T20:10:57+00:00 Achal Verma achalv@nvidia.com 2021-04-15T05:31:06+00:00 22418a46a5076dd13268c85620b403397d3d0878 Check return value of sscanf and let the user know if he entered invalid value. This fixes coverity issue : 10055695, 10055711 Bug 200741055 Change-Id: I8a8a8dd1887d9ebc75598848bd40449c11a95a31 Signed-off-by: Achal Verma <achalv@nvidia.com> Reviewed-on: https://git-master.nvidia.com/r/c/linux-nvidia/+/2575318 Reviewed-by: svc-mobile-coverity <svc-mobile-coverity@nvidia.com> Reviewed-by: Phoenix Jung <pjung@nvidia.com> Reviewed-by: mobile promotions <svcmobile_promotions@nvidia.com> GVS: Gerrit_Virtual_Submit Tested-by: mobile promotions <svcmobile_promotions@nvidia.com> 
Check return value of sscanf and let the user
know if he entered invalid value.

This fixes coverity issue : 10055695, 10055711

Bug 200741055

Change-Id: I8a8a8dd1887d9ebc75598848bd40449c11a95a31
Signed-off-by: Achal Verma <achalv@nvidia.com>
Reviewed-on: https://git-master.nvidia.com/r/c/linux-nvidia/+/2575318
Reviewed-by: svc-mobile-coverity <svc-mobile-coverity@nvidia.com>
Reviewed-by: Phoenix Jung <pjung@nvidia.com>
Reviewed-by: mobile promotions <svcmobile_promotions@nvidia.com>
GVS: Gerrit_Virtual_Submit
Tested-by: mobile promotions <svcmobile_promotions@nvidia.com>
drivers: use overlay instead of relative path 2021-05-04T15:10:02+00:00 Ankit Patel anpatel@nvidia.com 2021-04-27T15:43:17+00:00 9f1623fb5112ad33e7432fe2303a8d789b37364c Modified misc/tegra-cec and video/tegra/dc NVIDIA git repo Makefile, Now overlay macro will be used instead of relative path from kernel source tree, to find the included header file. Bug 200606454 Signed-off-by: Ankit Patel <anpatel@nvidia.com> Change-Id: I684388e9c81be94915c05db3cdae8b6100c6db91 (cherry picked from commit cc443ca25e19811feb0fba17e4ce7c2b6fcd6962) Reviewed-on: https://git-master.nvidia.com/r/c/linux-nvidia/+/2522483 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: mobile promotions <svcmobile_promotions@nvidia.com> 
Modified misc/tegra-cec and video/tegra/dc NVIDIA git repo Makefile, Now
overlay macro will be used instead of relative path from kernel source
tree, to find the included header file.

Bug 200606454

Signed-off-by: Ankit Patel <anpatel@nvidia.com>
Change-Id: I684388e9c81be94915c05db3cdae8b6100c6db91
(cherry picked from commit cc443ca25e19811feb0fba17e4ce7c2b6fcd6962)
Reviewed-on: https://git-master.nvidia.com/r/c/linux-nvidia/+/2522483
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: mobile promotions <svcmobile_promotions@nvidia.com>
misc: tegra-profiler: add unique identifier 2021-01-16T02:40:09+00:00 Igor Nabirushkin inabirushkin@nvidia.com 2020-12-29T23:02:32+00:00 6e44f66b704c7fd41dcf2944b8132c0140f5cf28 Add unique identifier seqid (sequence number) for samples. Bug 3216659 Signed-off-by: Igor Nabirushkin <inabirushkin@nvidia.com> Change-Id: I84b595f976f1f1955ecb278ababaf45591cdf5e0 Reviewed-on: https://git-master.nvidia.com/r/c/linux-nvidia/+/2464500 (cherry picked from commit ec284fc0b7b94871565c612358ea9e78e9ae4731) Reviewed-on: https://git-master.nvidia.com/r/c/linux-nvidia/+/2469351 Reviewed-by: Roman Rybalko <rrybalko@nvidia.com> Reviewed-by: Bibek Basu <bbasu@nvidia.com> Reviewed-by: mobile promotions <svcmobile_promotions@nvidia.com> GVS: Gerrit_Virtual_Submit Tested-by: mobile promotions <svcmobile_promotions@nvidia.com> 
Add unique identifier seqid (sequence number) for samples.

Bug 3216659

Signed-off-by: Igor Nabirushkin <inabirushkin@nvidia.com>
Change-Id: I84b595f976f1f1955ecb278ababaf45591cdf5e0
Reviewed-on: https://git-master.nvidia.com/r/c/linux-nvidia/+/2464500
(cherry picked from commit ec284fc0b7b94871565c612358ea9e78e9ae4731)
Reviewed-on: https://git-master.nvidia.com/r/c/linux-nvidia/+/2469351
Reviewed-by: Roman Rybalko <rrybalko@nvidia.com>
Reviewed-by: Bibek Basu <bbasu@nvidia.com>
Reviewed-by: mobile promotions <svcmobile_promotions@nvidia.com>
GVS: Gerrit_Virtual_Submit
Tested-by: mobile promotions <svcmobile_promotions@nvidia.com>
misc: tegra-profiler: fix build errors on k5.9 2021-01-16T02:40:03+00:00 Igor Nabirushkin inabirushkin@nvidia.com 2020-09-18T20:23:49+00:00 9e4c5eaa0ac9682d9da9e882f5a7aab508fc15a7 A few tegra-profiler changes to be compatible with kernel-5.9. Bug 3127567 Change-Id: I8cdfe325e4293d23d41c1065d5be5e9a723f5be2 Signed-off-by: Igor Nabirushkin <inabirushkin@nvidia.com> Reviewed-on: https://git-master.nvidia.com/r/c/linux-nvidia/+/2416859 (cherry picked from commit 243ad0e26488e8b150551a490d6fedcce25d65a4) Reviewed-on: https://git-master.nvidia.com/r/c/linux-nvidia/+/2469350 Reviewed-by: Roman Rybalko <rrybalko@nvidia.com> Reviewed-by: Bibek Basu <bbasu@nvidia.com> Reviewed-by: mobile promotions <svcmobile_promotions@nvidia.com> GVS: Gerrit_Virtual_Submit Tested-by: mobile promotions <svcmobile_promotions@nvidia.com> 
A few tegra-profiler changes to be compatible with kernel-5.9.

Bug 3127567

Change-Id: I8cdfe325e4293d23d41c1065d5be5e9a723f5be2
Signed-off-by: Igor Nabirushkin <inabirushkin@nvidia.com>
Reviewed-on: https://git-master.nvidia.com/r/c/linux-nvidia/+/2416859
(cherry picked from commit 243ad0e26488e8b150551a490d6fedcce25d65a4)
Reviewed-on: https://git-master.nvidia.com/r/c/linux-nvidia/+/2469350
Reviewed-by: Roman Rybalko <rrybalko@nvidia.com>
Reviewed-by: Bibek Basu <bbasu@nvidia.com>
Reviewed-by: mobile promotions <svcmobile_promotions@nvidia.com>
GVS: Gerrit_Virtual_Submit
Tested-by: mobile promotions <svcmobile_promotions@nvidia.com>
eqos: fix 'using uninitialized variable' 2021-01-16T02:39:46+00:00 Achal Verma achalv@nvidia.com 2021-01-07T03:31:21+00:00 fac39773b1e7eab097974085d0459efa7ff40f31 stack variable should be initailized before use. This fix coverity issue : 20629 Bug 200689436 Change-Id: I56e9096a581dfe2cc9d1e41bfcc1c599af5993d6 Signed-off-by: Achal Verma <achalv@nvidia.com> Reviewed-on: https://git-master.nvidia.com/r/c/linux-nvidia/+/2467801 Reviewed-by: Automatic_Commit_Validation_User Reviewed-by: svc-mobile-coverity <svc-mobile-coverity@nvidia.com> Reviewed-by: Phoenix Jung <pjung@nvidia.com> Reviewed-by: mobile promotions <svcmobile_promotions@nvidia.com> Tested-by: mobile promotions <svcmobile_promotions@nvidia.com> GVS: Gerrit_Virtual_Submit 
stack variable should be initailized before
use.

This fix coverity issue : 20629

Bug 200689436

Change-Id: I56e9096a581dfe2cc9d1e41bfcc1c599af5993d6
Signed-off-by: Achal Verma <achalv@nvidia.com>
Reviewed-on: https://git-master.nvidia.com/r/c/linux-nvidia/+/2467801
Reviewed-by: Automatic_Commit_Validation_User
Reviewed-by: svc-mobile-coverity <svc-mobile-coverity@nvidia.com>
Reviewed-by: Phoenix Jung <pjung@nvidia.com>
Reviewed-by: mobile promotions <svcmobile_promotions@nvidia.com>
Tested-by: mobile promotions <svcmobile_promotions@nvidia.com>
GVS: Gerrit_Virtual_Submit
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>
drivers: therm_fan_est: Add crit_temp update sysfs node 2021-01-06T09:09:24+00:00 Karthik Mantravadi mkarthik@nvidia.com 2020-12-18T08:36:35+00:00 36309cc6321684b5b77a4f26568eb9b1c301e02d Why? There can be cases where external drivers might be registering their thermal zones instead of thermal frameworks's thermal-zones dt node. In such cases the therm_fan_est probe fails to find the thermal zone in the registered list. We need to wait till all the thermal zones in the therm_fan_est subdevs list are registered, so that the therm_fan_est driver can register its own thermal zone. In case the user driver is built as a module, runtime crit_temp calculation logic needs to be added in therm_fan_est driver. How? Return defer probe if therm_fan_est probe does not find any of its sub-dev thermal zones registered. This does not add complications if all the thermal zones are registered via thermal framework's DT. The changes get applied if individual drivers register their thermal zones as part of their probe sequences. If the user-driver is built as a module, after inserting the kernel module, user needs to - echo 1 > /sys/devices/thermal-fan-est/update_subdevs_crit_temps - check if an errors while getting crit temp from the thermal zone. Bug 200646929 Change-Id: I87b02b26232abef3621b6af611ef97b23831ac45 Signed-off-by: Karthik Mantravadi <mkarthik@nvidia.com> Reviewed-on: https://git-master.nvidia.com/r/c/linux-nvidia/+/2461873 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> Tested-by: Rajkumar Kasirajan <rkasirajan@nvidia.com> Tested-by: mobile promotions <svcmobile_promotions@nvidia.com> 
Why?
There can be cases where external drivers might be registering their
thermal zones instead of thermal frameworks's thermal-zones dt node.
In such cases the therm_fan_est probe fails to find the thermal zone
in the registered list. We need to wait till all the thermal zones
in the therm_fan_est subdevs list are registered, so that the
therm_fan_est driver can register its own thermal zone. In case the
user driver is built as a module, runtime crit_temp calculation logic
needs to be added in therm_fan_est driver.

How?
Return defer probe if therm_fan_est probe does not find any of its
sub-dev thermal zones registered. This does not add complications if
all the thermal zones are registered via thermal framework's DT.
The changes get applied if individual drivers register their thermal
zones as part of their probe sequences. If the user-driver is built
as a module, after inserting the kernel module, user needs to
- echo 1 > /sys/devices/thermal-fan-est/update_subdevs_crit_temps
- check if an errors while getting crit temp from the thermal zone.

Bug 200646929

Change-Id: I87b02b26232abef3621b6af611ef97b23831ac45
Signed-off-by: Karthik Mantravadi <mkarthik@nvidia.com>
Reviewed-on: https://git-master.nvidia.com/r/c/linux-nvidia/+/2461873
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>
Tested-by: Rajkumar Kasirajan <rkasirajan@nvidia.com>
Tested-by: mobile promotions <svcmobile_promotions@nvidia.com>
nct1008: set external temperature limit even when detected open 2020-12-30T07:54:11+00:00 Ole Bjørn Midtbø omidtbo@cisco.com 2020-11-06T03:17:56+00:00 0acdf7937f43a8f05d810f36564e3e0f7fca42c7 Sometimes the external sensor is detected open during boot. This is suspected to be due to D+ > V+ - 0.3V before V+ voltage has properly settled. Not setting the shutdown limit in this case will cause thermal shutdown to be triggered when the sensor later is switched to extended range since the default limit 0x6C is then only 46C. Moving the check for open sensor to after setting limits and adding retries. The loop also triggers conversions since the open flag is only updated during conversion (not in standby mode). Bug 3150208 Change-Id: If95f053e405946668669360fa11aa1a935e7d6e7 Signed-off-by: Ahung Cheng <ahcheng@nvidia.com> Reviewed-on: https://git-master.nvidia.com/r/c/linux-nvidia/+/2442149 Reviewed-by: automaticguardword <automaticguardword@nvidia.com> Reviewed-by: Srikar Srimath Tirumala <srikars@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> Tested-by: Rajkumar Kasirajan <rkasirajan@nvidia.com> Tested-by: mobile promotions <svcmobile_promotions@nvidia.com> GVS: Gerrit_Virtual_Submit 
Sometimes the external sensor is detected open during boot. This is
suspected to be due to D+ > V+ - 0.3V before V+ voltage has properly
settled. Not setting the shutdown limit in this case will cause thermal
shutdown to be triggered when the sensor later is switched to extended
range since the default limit 0x6C is then only 46C.

Moving the check for open sensor to after setting limits and adding
retries. The loop also triggers conversions since the open flag is only
updated during conversion (not in standby mode).

Bug 3150208

Change-Id: If95f053e405946668669360fa11aa1a935e7d6e7
Signed-off-by: Ahung Cheng <ahcheng@nvidia.com>
Reviewed-on: https://git-master.nvidia.com/r/c/linux-nvidia/+/2442149
Reviewed-by: automaticguardword <automaticguardword@nvidia.com>
Reviewed-by: Srikar Srimath Tirumala <srikars@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>
Tested-by: Rajkumar Kasirajan <rkasirajan@nvidia.com>
Tested-by: mobile promotions <svcmobile_promotions@nvidia.com>
GVS: Gerrit_Virtual_Submit
nct1008: use max conversion time for TMP451 2020-12-30T07:54:06+00:00 Ole Bjørn Midtbø omidtbo@cisco.com 2020-10-30T08:11:13+00:00 758fc9629b03a656b11e8f6dbe08f089e96aa598 Use max (34ms) rather than typical (31ms) to make sure conversion is done when reading result. Also rename variable from '_ns' to '_us' to match variable unit. Bug 3150208 Change-Id: Ie4ebd79800fc93ffc44da2a61e060be0c2fdcb9f Signed-off-by: Ahung Cheng <ahcheng@nvidia.com> Reviewed-on: https://git-master.nvidia.com/r/c/linux-nvidia/+/2442148 Reviewed-by: automaticguardword <automaticguardword@nvidia.com> Reviewed-by: Automatic_Commit_Validation_User Reviewed-by: Srikar Srimath Tirumala <srikars@nvidia.com> Reviewed-by: Bibek Basu <bbasu@nvidia.com> Reviewed-by: svc-mobile-coverity <svc-mobile-coverity@nvidia.com> Reviewed-by: Rajkumar Kasirajan <rkasirajan@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 
Use max (34ms) rather than typical (31ms) to make sure conversion is done
when reading result. Also rename variable from '_ns' to '_us' to match
variable unit.

Bug 3150208

Change-Id: Ie4ebd79800fc93ffc44da2a61e060be0c2fdcb9f
Signed-off-by: Ahung Cheng <ahcheng@nvidia.com>
Reviewed-on: https://git-master.nvidia.com/r/c/linux-nvidia/+/2442148
Reviewed-by: automaticguardword <automaticguardword@nvidia.com>
Reviewed-by: Automatic_Commit_Validation_User
Reviewed-by: Srikar Srimath Tirumala <srikars@nvidia.com>
Reviewed-by: Bibek Basu <bbasu@nvidia.com>
Reviewed-by: svc-mobile-coverity <svc-mobile-coverity@nvidia.com>
Reviewed-by: Rajkumar Kasirajan <rkasirajan@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