From: "Russell King (Oracle)" <linux@armlinux.org.uk>
To: Jayesh Choudhary <j-choudhary@ti.com>
Cc: mturquette@baylibre.com, sboyd@kernel.org,
linux-clk@vger.kernel.org, devarsht@ti.com,
linux-kernel@vger.kernel.org, tomi.valkeinen@ideasonboard.com
Subject: Re: [PATCH] clk: Add clk_determine_rate function call
Date: Tue, 17 Jun 2025 23:28:06 +0100 [thread overview]
Message-ID: <aFHr9sVnU3Nx6yh0@shell.armlinux.org.uk> (raw)
In-Reply-To: <20250616103527.509999-1-j-choudhary@ti.com>
On Mon, Jun 16, 2025 at 04:05:27PM +0530, Jayesh Choudhary wrote:
> Add a function to determine if a particular rate can be set for a clock
> with its argument being the clock and the desired rate so that it could
> be exposed to other peripherals.
> For example, the display controllers typically has to perform multiple
> checks for supported display resolutions including those related to
> clock rates. The controller has to check this way before it actually
> enables the clock and has to do it multiple times (typically for each
> mode), and therefore using the clk_set_rate when its not needed, does
> not make sense.
So what's up with using clk_round_rate(), which returns the clock rate
that one would actually get if one calls clk_set_rate() with the the
value passed into clk_round_rate() ?
Why is clk_round_rate() not sufficient?
--
RMK's Patch system: https://www.armlinux.org.uk/developer/patches/
FTTP is here! 80Mbps down 10Mbps up. Decent connectivity at last!
next prev parent reply other threads:[~2025-06-17 22:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-16 10:35 [PATCH] clk: Add clk_determine_rate function call Jayesh Choudhary
2025-06-17 20:03 ` Brian Masney
2025-06-18 8:10 ` Jayesh Choudhary
2025-06-17 22:28 ` Russell King (Oracle) [this message]
2025-06-18 8:07 ` Jayesh Choudhary
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=aFHr9sVnU3Nx6yh0@shell.armlinux.org.uk \
--to=linux@armlinux.org.uk \
--cc=devarsht@ti.com \
--cc=j-choudhary@ti.com \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mturquette@baylibre.com \
--cc=sboyd@kernel.org \
--cc=tomi.valkeinen@ideasonboard.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.