lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Thu, 13 Jun 2019 08:58:54 +0530 From: Viresh Kumar <viresh.kumar@...aro.org> To: Nicolas Saenz Julienne <nsaenzjulienne@...e.de> Cc: stefan.wahren@...e.com, "Rafael J. Wysocki" <rjw@...ysocki.net>, mbrugger@...e.de, sboyd@...nel.org, eric@...olt.net, f.fainelli@...il.com, bcm-kernel-feedback-list@...adcom.com, ptesarik@...e.com, linux-rpi-kernel@...ts.infradead.org, ssuloev@...altech.com, linux-clk@...r.kernel.org, linux-arm-kernel@...ts.infradead.org, mturquette@...libre.com, linux-pm@...r.kernel.org, linux-kernel@...r.kernel.org Subject: Re: [PATCH v4 4/7] cpufreq: add driver for Raspberry Pi On 12-06-19, 20:24, Nicolas Saenz Julienne wrote: > 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@...e.de> > Acked-by: Eric Anholt <eric@...olt.net> > Reviewed-by: Stephen Boyd <sboyd@...nel.org> Applied. Thanks. -- viresh
Powered by blists - more mailing lists