[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20190729090735.GA897@onstation.org>
Date: Mon, 29 Jul 2019 05:07:35 -0400
From: Brian Masney <masneyb@...tation.org>
To: Amit Kucheria <amit.kucheria@...aro.org>
Cc: LKML <linux-kernel@...r.kernel.org>,
linux-arm-msm <linux-arm-msm@...r.kernel.org>,
Bjorn Andersson <bjorn.andersson@...aro.org>,
Eduardo Valentin <edubezval@...il.com>,
Andy Gross <andy.gross@...aro.org>,
Andy Gross <agross@...nel.org>,
Daniel Lezcano <daniel.lezcano@...aro.org>,
Mark Rutland <mark.rutland@....com>,
Rob Herring <robh+dt@...nel.org>,
Zhang Rui <rui.zhang@...el.com>,
Marc Gonzalez <marc.w.gonzalez@...e.fr>,
"open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS"
<devicetree@...r.kernel.org>,
Linux PM list <linux-pm@...r.kernel.org>
Subject: Re: [PATCH 00/15] thermal: qcom: tsens: Add interrupt support
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@...tation.org> 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
Powered by blists - more mailing lists