All of lore.kernel.org
 help / color / mirror / Atom feed
From: Linus Walleij <linus.walleij@linaro.org>
To: Maxime Ripard <maxime@cerno.tech>
Cc: Mike Turquette <mturquette@baylibre.com>,
	Stephen Boyd <sboyd@kernel.org>,
	linux-clk <linux-clk@vger.kernel.org>,
	Dave Stevenson <dave.stevenson@raspberrypi.com>,
	Phil Elwell <phil@raspberrypi.com>,
	Tim Gover <tim.gover@raspberrypi.com>,
	Dom Cobley <dom@raspberrypi.com>
Subject: Re: Scaling back down a shared clock
Date: Thu, 25 Mar 2021 09:01:31 +0100	[thread overview]
Message-ID: <CACRpkdar4tNTLLd9NFV-nG3kQnq-cLhLDB10EcLyN_Sew+uRAA@mail.gmail.com> (raw)
In-Reply-To: <20210319150355.xzw7ikwdaga2dwhv@gilmour>

On Fri, Mar 19, 2021 at 4:04 PM Maxime Ripard <maxime@cerno.tech> wrote:

> How could we put some kind of downward pressure on the clock rate to
> make it run at its minimum all the time? It looks like the PM QoS
> framework implements something similar for the bus bandwidth, except
> that it's not really a bus that have this requirement here.

Unsolicited comment: this is similar to what _regulator_do_set_voltage()
is doing with voltages that can be expressed as linear intervals or
selectors (fixed voltage steps) when a consumer calls
regulator_set_voltage().

Yours,
Linus Walleij

  parent reply	other threads:[~2021-03-25  8:02 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-19 15:03 Scaling back down a shared clock Maxime Ripard
2021-03-19 19:58 ` Michael Turquette
2021-03-24 10:24   ` Maxime Ripard
2021-03-25  8:01 ` Linus Walleij [this message]
2021-03-25 16:09   ` Maxime Ripard
2021-03-25  9:58 ` Abel Vesa
2021-03-25 16:10   ` Maxime Ripard

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=CACRpkdar4tNTLLd9NFV-nG3kQnq-cLhLDB10EcLyN_Sew+uRAA@mail.gmail.com \
    --to=linus.walleij@linaro.org \
    --cc=dave.stevenson@raspberrypi.com \
    --cc=dom@raspberrypi.com \
    --cc=linux-clk@vger.kernel.org \
    --cc=maxime@cerno.tech \
    --cc=mturquette@baylibre.com \
    --cc=phil@raspberrypi.com \
    --cc=sboyd@kernel.org \
    --cc=tim.gover@raspberrypi.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.