public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Stephen Boyd <sboyd@kernel.org>
To: Luca Ceresoli <luca.ceresoli@bootlin.com>,
	Michael Turquette <mturquette@baylibre.com>,
	Peng Fan (OSS) <peng.fan@oss.nxp.com>,
	Rob Herring <robh@kernel.org>,
	Saravana Kannan <saravanak@google.com>
Cc: devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-clk@vger.kernel.org, Peng Fan <peng.fan@nxp.com>
Subject: Re: [PATCH v4 2/2] clk: clk-conf: support assigned-clock-rates-u64
Date: Thu, 08 Aug 2024 12:45:58 -0700	[thread overview]
Message-ID: <6bc191590c1a5b7fa3ef991d6b7e327b.sboyd@kernel.org> (raw)
In-Reply-To: <20240804-clk-u64-v4-2-8e55569f39a4@nxp.com>

Quoting Peng Fan (OSS) (2024-08-04 05:32:56)
> From: Peng Fan <peng.fan@nxp.com>
> 
> i.MX95 System Management Control Firmware(SCMI) manages the clock
> function, it exposes PLL VCO which could support up to 5GHz rate that
> exceeds UINT32_MAX. So add assigned-clock-rates-u64 support
> to set rate that exceeds UINT32_MAX.
> 
> Signed-off-by: Peng Fan <peng.fan@nxp.com>
> ---
>  drivers/clk/clk-conf.c | 42 +++++++++++++++++++++++++++++++++++++-----
>  1 file changed, 37 insertions(+), 5 deletions(-)

Thanks. I'd like to have a DT overlay KUnit test for this as well.
Either you can write it, or I'll write it next week.

  reply	other threads:[~2024-08-08 19:46 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-04 12:32 [PATCH v4 0/2] clk: add assigned-clock-rates-u64 Peng Fan (OSS)
2024-08-04 12:32 ` [PATCH v4 1/2] of: property: add of_property_for_each_u64 Peng Fan (OSS)
2024-08-13 16:47   ` Rob Herring (Arm)
2024-08-04 12:32 ` [PATCH v4 2/2] clk: clk-conf: support assigned-clock-rates-u64 Peng Fan (OSS)
2024-08-08 19:45   ` Stephen Boyd [this message]
2024-08-09  3:19     ` Peng Fan
2024-08-16 22:21   ` Stephen Boyd
2024-08-17  3:04     ` Peng Fan

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=6bc191590c1a5b7fa3ef991d6b7e327b.sboyd@kernel.org \
    --to=sboyd@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=linux-clk@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=luca.ceresoli@bootlin.com \
    --cc=mturquette@baylibre.com \
    --cc=peng.fan@nxp.com \
    --cc=peng.fan@oss.nxp.com \
    --cc=robh@kernel.org \
    --cc=saravanak@google.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox