On Mon, Jul 29, 2019 at 3:03 PM Luca Weiss <luca@xxxxxxxxx> wrote: > > On Montag, 29. Juli 2019 11:07:35 CEST Brian Masney wrote: > > On Sat, Jul 27, 2019 at 12:58:54PM +0530, Amit Kucheria wrote: > > > On Fri, Jul 26, 2019 at 4:59 PM Brian Masney <masneyb@xxxxxxxxxxxxx> wrote: > > > > On Fri, Jul 26, 2019 at 04:40:16PM +0530, Amit Kucheria wrote: > > > > > How well does cpufreq work on 8974? I haven't looked at it yet but > > > > > we'll need it for thermal throttling. > > > > > > > > I'm not sure how to tell if the frequency is dynamically changed during > > > > runtime on arm. x86-64 shows this information in /proc/cpuinfo. Here's > > > > > > > the /proc/cpuinfo on the Nexus 5: > > > Nah. /proc/cpuinfo won't show what we need. > > > > > > Try the following: > > > > > > $ grep "" /sys/devices/system/cpu/cpufreq/policy?/* > > > > > > More specifically, the following files have the information you need. > > > Run watch -n1 on them. > > > > > > $ grep "" /sys/devices/system/cpu/cpufreq/policy?/scaling_*_freq > > > > There's no cpufreq directory on msm8974: > > > > # ls -1 /sys/devices/system/cpu/ > > cpu0 > > cpu1 > > cpu2 > > cpu3 > > cpuidle > > hotplug > > isolated > > kernel_max > > modalias > > offline > > online > > possible > > power > > present > > smt > > uevent > > > > I'm using qcom_defconfig. > > > > Brian > > Hi Brian, > cpufreq isn't supported on msm8974 yet. > I have these patches [0] in my tree but I'm not sure they work correctly, but I haven't tested much with them. Feel free to try them on hammerhead. > > Luca > > [0] https://github.com/z3ntu/linux/compare/b0917f53ada0e929896a094b451219cd8091366e...6459ca6aff498c9d12acd35709b4903effc4c3f8 Niklas is working on refactoring some of the Krait code[1]. I'm not sure if he looked at 8974 directly as part of the refactor adding him here to get a better sense of the state of cpufreq on 8974. [1] https://lore.kernel.org/linux-arm-msm/20190726080823.xwhxagv5iuhudmic@vireshk-i7/T/#t
