Details of effects caused by jetson_clocks.sh

When I ran jetson_clocks.sh, some configuration parameters stored in l4t_dfs.conf were changed. Can anyone explain what following 6 parameters indicate respectively?

/sys/module/qos/parameters/enable:Y -> N
/sys/kernel/debug/tegra_cpufreq/M_CLUSTER/cc3/enable:1 -> 0
/sys/kernel/debug/tegra_cpufreq/B_CLUSTER/cc3/enable:1 -> 0
/sys/devices/17000000.gp10b/devfreq/17000000.gp10b/min_freq:140250000 -> 1122000000
/sys/devices/17000000.gp10b/railgate_enable:0 -> 0 (no change)
/sys/kernel/debug/bpmp/debug/clk/emc/mrq_rate_locked:0 -> 1

Thanks.

tannoy,

This script is to fix cpu/gpu/emc clock to specific value, so those parameters are mostly for unlocking some limitation/power-state.

  1. cc3 is a cluster power-states and the script disable this state for higher cpu frequency.
  2. The 17000000.gp10b/min_freq is the minimum frequency of gpu glock and now the min is being pulled up.

3.As for railgate, for t186, we always keep this disabled, so this should be no change.

  1. The mrq lock for emc is disabled because we are going to disabled dfs and fix emc clock.

Hi WayneWWW,

Thank you for explanation.
Your answer #1 and #2 are clear.

On #3, Can you let me know what is the railgate for?
On #4, does the dfs stand for digital frequency synthesizer?
Does the qos stand for quality of service? And does it set priorities on processes?

Thanks.