nvidia-tegra-modules.git/drivers/devfreq/governor_wmark_active.c, branch rtss22-ae

devfreq: wmark: active: set interrupt_driven

2020-09-25T16:39:57+00:00

Set interrupt_driven to 1 thus cancel_delayed_work_sync() won't be
called in devfreq_monitor_suspend() when handling DEVFREQ_GOV_SUSPEND
event. This will avoid below warning prints when runtime PM is enabled.

[ 22.121071] INFO: trying to register non-static key.
[ 22.126030] the code is fine but needs lockdep annotation.
[ 22.131501] turning off the locking correctness validator.

The backstrace:
[    9.322855] [] flush_work+0x1fc/0x208
[    9.322858] [] __cancel_work_timer+0xa0/0x188
[    9.322862] [] cancel_delayed_work_sync+0x24/0x30
[    9.322867] [] devfreq_monitor_suspend+0x4c/0x80
[    9.322871] [] devfreq_watermark_event_handler+0x3b4/0x458
[    9.322874] [] devfreq_suspend_device+0x60/0x98
[    9.322878] [] nvhost_module_runtime_suspend+0x64/0x160
[    9.322883] [] pm_generic_runtime_suspend+0x3c/0x58
[    9.322887] [] genpd_runtime_suspend+0x98/0x230
[    9.322890] [] __rpm_callback+0x74/0xa0
[    9.322893] [] rpm_callback+0x34/0x98
[    9.322896] [] rpm_suspend+0x100/0x5f0
[    9.322899] [] pm_runtime_work+0x80/0xb8
[    9.322902] [] process_one_work+0x1e4/0x4b0
[    9.322904] [] worker_thread+0x50/0x4c8
[    9.322908] [] kthread+0xec/0xf0
[    9.322911] [] ret_from_fork+0x10/0x30

Bug 3128395

Change-Id: I15116cd452a062620c01e91f71eecba7d68cde17
Signed-off-by: Ken Chang 
Reviewed-on: https://git-master.nvidia.com/r/c/linux-nvidia/+/2418831
Reviewed-by: automaticguardword 
Reviewed-by: Aaron Tian 
Reviewed-by: Bibek Basu 
Reviewed-by: mobile promotions 
GVS: Gerrit_Virtual_Submit
Tested-by: mobile promotions

devfreq: wmark: active: config params by sysfs

2020-01-03T14:39:22+00:00

Configure governor parameters through sysfs instead of
debugfs, add add spinlock for concurrency protection.

Bug 200501949

Change-Id: I0131e6ab0d3befe380ef4774eb4d6193d2266011
Signed-off-by: Aaron Tian 
Reviewed-on: https://git-master.nvidia.com/r/2267338
Reviewed-by: Automatic_Commit_Validation_User
Reviewed-by: Mikko Perttunen 
Reviewed-by: mobile promotions 
Tested-by: mobile promotions

devfreq: wmark: active: introduce freq_boost_en knob

2019-12-12T03:55:59+00:00

There is a freq. boost mechanism in wmark_active governor,
when current loading exceed load_max, directly set target
freq. to fmax.

Introduce 'freq_boost_en' knob to support enable/disable
freq. boost. If performance does not regressed, freq. boost
can be disabled to let DFS smoothly and save power.

Bug 200501949

Change-Id: I6ec7b7079a22a8d974743d766cfd0cc7d0e2dcd4
Signed-off-by: Aaron Tian 
Reviewed-on: https://git-master.nvidia.com/r/2255082
GVS: Gerrit_Virtual_Submit
Reviewed-by: Mikko Perttunen 
Reviewed-by: mobile promotions 
Tested-by: mobile promotions

video: tegra: host: update T186 VIC actmon driver

2019-10-10T20:41:15+00:00

Modify T186/T210 VIC actmon driver and wmark_active governor
to address the following issues:

1. To let VIC actmon reports accurate VIC active
   cycle counts, set static WEIGHT_COUNT in both
   VIC actmon and VIC IP block. It ensures
   VIC actmon can capture all activity signal
   toggle event from VIC.

   The value of WEIGHT_COUNT are equal to:

   4 * (max VIC freq / VIC_actmon freq)
       = 4 * (1024 / 19.2)
      ~= 213

2. Since VIC actmon reports active "VIC clock
   cycle" instead of "VIC actmon clock cycle",
   "relative loading translation" should consider
   current VIC clock freq.

   E.g.,
     - sample_period = 80 us, VIC freq = 115.2 Mhz
     - 9216 cycles represents 100% loading
       (115.2 * 80)

3. Update upper/lower wmark settings after VIC
   clock scaled completed, to ensure wmark settings
   are equil to 0 ~ 100% loading of current freq.
   - Register 'get_dev_status' instance in
     devfreq_dev_profile, to let wmark active
     governor can query current device freq.
   - Register devfreq transition notifier in
     wmark_active governor. It will query current
     device freq. and update corresponding wmark
     value after VIC freq. changed.

Bug 200501949

Change-Id: Ic159eb93fddc37d55b0c9649a3afcb50ed82cac2
Signed-off-by: Aaron Tian 
Reviewed-on: https://git-master.nvidia.com/r/2200520
GVS: Gerrit_Virtual_Submit
Reviewed-by: Arto Merilainen 
Reviewed-by: Mikko Perttunen 
Reviewed-by: mobile promotions 
Tested-by: mobile promotions

devfreq: wmark: active: add GPL module license

2018-07-05T16:59:13+00:00

Add GPL module license to able to use the symbols that are exported by
"EXPORT_SYMBOL_GPL".

Bug 200299507

Change-Id: I127507b86392ebc20f5d04a747c528e788d87294
Signed-off-by: Joseph Lo 
Reviewed-on: http://git-master/r/1478916
Reviewed-on: https://git-master.nvidia.com/r/1551729
(cherry picked from linux-4.9 commit aa85b2d73b55496faabf0deae896d021bda7d8c8)
Reviewed-on: https://git-master.nvidia.com/r/1770154
Reviewed-by: Mikko Perttunen 
GVS: Gerrit_Virtual_Submit
Reviewed-by: Timo Alho 
Tested-by: Timo Alho 
Reviewed-by: mobile promotions 
Tested-by: mobile promotions

Fix include paths for in-tree builds

2018-07-05T16:59:09+00:00

Some source files include header files using <> even though the header
file is not in a directory typically in the system include path. This
works when compiling the kernel with an O= option (which stores built
files outside the source tree) because the kernel adds various extra
source paths to the system include path. However, this doesn't happen when
building in-tree, so the source must be fixed to use "" for "local" files.

Similarly, fix one usage of "" where no path was specified in the ""
filename, whereas the header was in a relative directory to the source.
Again, with O= I believe this works because the kernel added the file's
location into the include path, but doesn't for in-tree builds.

Note: Parts of the original commit apply to source that has been moved
to linux-nvidia.git; see change Icf4f94b671e73c0a889bb996edc3f15d5fbde98b
for that part of the original rel-28 change.

Bug 1978388

Change-Id: I907c88a4822b309a33c031ec21dd215047ea3e94
Signed-off-by: Stephen Warren 
Reviewed-on: https://git-master.nvidia.com/r/1544318
Reviewed-on: https://git-master.nvidia.com/r/1545674
Reviewed-on: https://git-master.nvidia.com/r/1546976
(cherry picked from linux-4.9 commit cc6281afdbe059734d53f54020f1ead0b5cf3659)
Reviewed-on: https://git-master.nvidia.com/r/1770153
Reviewed-by: Mikko Perttunen 
GVS: Gerrit_Virtual_Submit
Reviewed-by: Timo Alho 
Tested-by: Timo Alho 
Reviewed-by: mobile promotions 
Tested-by: mobile promotions

devfreq: wmark: fix compilation on kernel 4.4

2018-07-05T16:58:36+00:00

The watermark devfreq governors were not building
on kernel 4.4 due to a missing include of module.h
Add the include.

JIRA HOSTX-50

Change-Id: Ieebf5cd0bf6a0737e501423c1f182de5838f31a3
Signed-off-by: Mikko Perttunen 
Reviewed-on: http://git-master/r/1189446
(cherry picked from linux-4.9 commit e397f5ebd40c9f5114efdd0f6da7e189e51203a6)
Reviewed-on: https://git-master.nvidia.com/r/1770144
GVS: Gerrit_Virtual_Submit
Reviewed-by: Timo Alho 
Tested-by: Timo Alho 
Reviewed-by: mobile promotions 
Tested-by: mobile promotions

devfreq: wmark: active: init average target freq

2018-07-05T16:58:31+00:00

- initializes average target freq parameter of active watermark
  governor parameter to current frequency set during start and
  resume from suspend.

Bug 200165367

Change-Id: I56b43ea371c77e95285944433615660400da94ea
Reviewed-on: http://git-master/r/936632
Signed-off-by: Shridhar Rasal 
Reviewed-on: http://git-master/r/1160862
(cherry picked from linux-4.9 commit 331b1f92e097209b3afd9ab92fe5337152c604e2)
Reviewed-on: https://git-master.nvidia.com/r/1770143
Reviewed-by: Mikko Perttunen 
GVS: Gerrit_Virtual_Submit
Reviewed-by: Timo Alho 
Tested-by: Timo Alho 
Reviewed-by: mobile promotions 
Tested-by: mobile promotions

devfreq: Improvements watermark active policy

2018-07-05T16:58:28+00:00

This patch modifies wmark active policy to...
- track average frequency requirement
- not scale too often - there is now 50ms hysteresis.

Bug 1625576

Change-Id: I18afc5249a4821f62a0a58cdccd163e11763c841
Signed-off-by: Arto Merilainen 
Reviewed-on: http://git-master/r/719594
Reviewed-on: http://git-master/r/1160010
(cherry picked from linux-4.9 commit d451a28402cfee5bf393b44674b4a50a4321a131)
Reviewed-on: https://git-master.nvidia.com/r/1770142
Reviewed-by: Mikko Perttunen 
GVS: Gerrit_Virtual_Submit
Reviewed-by: Timo Alho 
Tested-by: Timo Alho 
Reviewed-by: mobile promotions 
Tested-by: mobile promotions

devfreq: Improve wmark_active initialization

2018-07-05T16:58:24+00:00

The wmark_active governor initialization assumes that the device
frequency is the lowest possible frequency when the governor is
started or resumed. However, this may not be correct if the
governor was suspended/stopped before the clock had been slowed
down.

This patch modifies the governor to read the frequency during
governor initialization and resume.

Change-Id: I38d3256102b344bc8818c5623a015843678a8ce5
Signed-off-by: Arto Merilainen 
Reviewed-on: http://git-master/r/733007
Reviewed-on: http://git-master/r/1160009
(cherry picked from linux-4.9 commit 32e2561dffc5d7390fa4fd503651da9013403ecb)
Reviewed-on: https://git-master.nvidia.com/r/1770141
Reviewed-by: Mikko Perttunen 
GVS: Gerrit_Virtual_Submit
Reviewed-by: Timo Alho 
Tested-by: Timo Alho 
Reviewed-by: mobile promotions 
Tested-by: mobile promotions