public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: Stephen Boyd <sboyd@kernel.org>
To: "Dave Stevenson" <dave.stevenson@raspberrypi.com>,
	"Dom Cobley" <popcornmix@gmail.com>,
	"Florian Fainelli" <florian.fainelli@broadcom.com>,
	"Iago Toral Quiroga" <itoral@igalia.com>,
	"Maxime Ripard" <mripard@kernel.org>,
	"Maíra Canal" <mcanal@igalia.com>,
	"Melissa Wen" <mwen@igalia.com>,
	"Michael Turquette" <mturquette@baylibre.com>,
	"Nicolas Saenz Julienne" <nsaenz@kernel.org>,
	"Philipp Zabel" <p.zabel@pengutronix.de>,
	"Stefan Wahren" <wahrenst@gmx.net>
Cc: linux-clk@vger.kernel.org, linux-rpi-kernel@lists.infradead.org,
	linux-arm-kernel@lists.infradead.org,
	dri-devel@lists.freedesktop.org,
	"Broadcom internal kernel review list"
	<bcm-kernel-feedback-list@broadcom.com>,
	kernel-dev@igalia.com, "Maíra Canal" <mcanal@igalia.com>
Subject: Re: [PATCH v2 3/5] clk: bcm: rpi: Maximize V3D clock
Date: Sun, 21 Sep 2025 09:25:21 -0700	[thread overview]
Message-ID: <175847192183.4354.13711226446879462833@lazor> (raw)
In-Reply-To: <20250731-v3d-power-management-v2-3-032d56b01964@igalia.com>

Quoting Maíra Canal (2025-07-31 14:06:19)
> Although minimizing the clock rate is the best for most scenarios, as
> stated in commit 4d85abb0fb8e ("clk: bcm: rpi: Enable minimize for all
> firmware clocks"), when it comes to the GPU, it's ideal to have the
> maximum rate allowed.
> 
> Add an option to maximize a firmware clock's rate when the clock is
> enabled and set this option for V3D.
> 
> Signed-off-by: Maíra Canal <mcanal@igalia.com>
> ---

Applied to clk-next


  reply	other threads:[~2025-09-21 16:25 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-31 21:06 [PATCH v2 0/5] Power Management for Raspberry Pi V3D GPU Maíra Canal
2025-07-31 21:06 ` [PATCH v2 1/5] clk: bcm: rpi: Add missing logs if firmware fails Maíra Canal
2025-09-21 16:25   ` Stephen Boyd
2025-07-31 21:06 ` [PATCH v2 2/5] clk: bcm: rpi: Turn firmware clock on/off when preparing/unpreparing Maíra Canal
2025-08-18 10:51   ` Stefan Wahren
2025-09-21 16:25   ` Stephen Boyd
2025-09-25  7:57   ` Marek Szyprowski
2025-09-25 16:48     ` Stefan Wahren
2025-09-26  7:27       ` Marek Szyprowski
2025-09-26 10:36         ` Stefan Wahren
2025-10-01 20:50           ` Melissa Wen
2025-10-02  6:59             ` Marek Szyprowski
2025-10-02 14:52             ` Stefan Wahren
2025-07-31 21:06 ` [PATCH v2 3/5] clk: bcm: rpi: Maximize V3D clock Maíra Canal
2025-09-21 16:25   ` Stephen Boyd [this message]
2025-07-31 21:06 ` [PATCH v2 4/5] drm/v3d: Allocate all resources before enabling the clock Maíra Canal
2025-08-01  6:53   ` Philipp Zabel
2025-07-31 21:06 ` [PATCH v2 5/5] drm/v3d: Introduce Runtime Power Management Maíra Canal

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=175847192183.4354.13711226446879462833@lazor \
    --to=sboyd@kernel.org \
    --cc=bcm-kernel-feedback-list@broadcom.com \
    --cc=dave.stevenson@raspberrypi.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=florian.fainelli@broadcom.com \
    --cc=itoral@igalia.com \
    --cc=kernel-dev@igalia.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-clk@vger.kernel.org \
    --cc=linux-rpi-kernel@lists.infradead.org \
    --cc=mcanal@igalia.com \
    --cc=mripard@kernel.org \
    --cc=mturquette@baylibre.com \
    --cc=mwen@igalia.com \
    --cc=nsaenz@kernel.org \
    --cc=p.zabel@pengutronix.de \
    --cc=popcornmix@gmail.com \
    --cc=wahrenst@gmx.net \
    /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