From: David Lechner <david@lechnology.com>
To: Bartosz Golaszewski <brgl@bgdev.pl>, Sekhar Nori <nsekhar@ti.com>,
Kevin Hilman <khilman@kernel.org>,
Rob Herring <robh+dt@kernel.org>,
Mark Rutland <mark.rutland@arm.com>
Cc: linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org,
Bartosz Golaszewski <bgolaszewski@baylibre.com>
Subject: Re: [PATCH 0/4] ARM: da850: enable cpufreq in DT mode
Date: Thu, 21 Mar 2019 10:29:22 -0500 [thread overview]
Message-ID: <e4d51b63-bc07-c595-9d73-c4b09eb11341@lechnology.com> (raw)
In-Reply-To: <20190321141010.19612-1-brgl@bgdev.pl>
On 3/21/19 9:10 AM, Bartosz Golaszewski wrote:
> From: Bartosz Golaszewski <bgolaszewski@baylibre.com>
>
> This series adds cpufreq-dt operating points for da850 boards supported
> with device tree (da850-lcdk, da850-lego-ev3, da850-evm) and also
> includes a fix for the da850-evm boardfile which checks an unset variable
> to determine the highest available frequency for cpufreq.
I can't find any old threads about this, but I recall that there was a
problem with the USB OHCI controller breaking when switching frequencies.
It didn't happen all of the time, but often enough that it made using
cpufreq unusable for me. Is this still a problem?
Also, a big-picture question. On boards with fixed regulators, what is
the benefit of enabling frequency scaling? The power savings aspect
seems negligible (< 1% in my tests) since the voltage cannot be changed.
next prev parent reply other threads:[~2019-03-21 15:29 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-21 14:10 [PATCH 0/4] ARM: da850: enable cpufreq in DT mode Bartosz Golaszewski
2019-03-21 14:10 ` [PATCH 1/4] ARM: davinci: fix cpufreq registration on da850-evm Bartosz Golaszewski
2019-03-21 14:10 ` [PATCH 2/4] ARM: dts: da850: add cpu node and operating points to DT Bartosz Golaszewski
2019-03-21 15:56 ` David Lechner
2019-03-21 14:10 ` [PATCH 3/4] ARM: dts: da850-evm: enable cpufreq Bartosz Golaszewski
2019-03-21 15:53 ` David Lechner
2019-03-21 16:36 ` Bartosz Golaszewski
2019-03-21 16:43 ` Bartosz Golaszewski
2019-03-21 17:13 ` Bartosz Golaszewski
2019-03-21 14:10 ` [PATCH 4/4] ARM: davinci_all_defconfig: Enable CPUFREQ_DT Bartosz Golaszewski
2019-03-21 15:29 ` David Lechner [this message]
2019-03-21 15:40 ` [PATCH 0/4] ARM: da850: enable cpufreq in DT mode Bartosz Golaszewski
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=e4d51b63-bc07-c595-9d73-c4b09eb11341@lechnology.com \
--to=david@lechnology.com \
--cc=bgolaszewski@baylibre.com \
--cc=brgl@bgdev.pl \
--cc=devicetree@vger.kernel.org \
--cc=khilman@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=nsekhar@ti.com \
--cc=robh+dt@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).