+1
−0
drivers/cpufreq/raspberrypi-cpufreq.c
0 → 100644
+97
−0
Loading
Gitlab 现已全面支持 git over ssh 与 git over https。通过 HTTPS 访问请配置带有 read_repository / write_repository 权限的 Personal access token。通过 SSH 端口访问请使用 22 端口或 13389 端口。如果使用CAS注册了账户但不知道密码,可以自行至设置中更改;如有其他问题,请发邮件至 service@cra.moe 寻求协助。
Raspberry Pi's firmware offers and interface though which update it's performance requirements. It allows us to request for specific runtime frequencies, which the firmware might or might not respect, depending on the firmware configuration and thermals. As the maximum and minimum frequencies are configurable in the firmware there is no way to know in advance their values. So the Raspberry Pi cpufreq driver queries them, builds an opp frequency table to then launch cpufreq-dt. Also, as the firmware interface might be configured as a module, making the cpu clock unavailable during init, this implements a full fledged driver, as opposed to most drivers registering cpufreq-dt, which only make use of an init routine. Signed-off-by:Nicolas Saenz Julienne <nsaenzjulienne@suse.de> Acked-by:
Eric Anholt <eric@anholt.net> Reviewed-by:
Stephen Boyd <sboyd@kernel.org> Acked-by:
Stefan Wahren <stefan.wahren@i2se.com> Signed-off-by:
Viresh Kumar <viresh.kumar@linaro.org>
CRA Git | Maintained and supported by SUSTech CRA and CCSE