From: Stephen Boyd <sboyd@kernel.org>
To: Lars-Peter Clausen <lars@metafoo.de>,
Michael Turquette <mturquette@baylibre.com>
Cc: Luca Ceresoli <luca.ceresoli@bootlin.com>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
linux-clk@vger.kernel.org, devicetree@vger.kernel.org,
Lars-Peter Clausen <lars@metafoo.de>
Subject: Re: [PATCH 2/3] clk: vc5: Add support for 5P49V60
Date: Wed, 18 Jan 2023 10:57:22 -0800 [thread overview]
Message-ID: <4121e6f0d8c0cb71df9736daa5ddaaee.sboyd@kernel.org> (raw)
In-Reply-To: <20230114233500.3294789-2-lars@metafoo.de>
Quoting Lars-Peter Clausen (2023-01-14 15:34:59)
> The 5P49V60 is very similar to the existing supported clock chips of the
> versaclock5 driver and uses the same register map layout. But its maximum
> VCO frequency is 2.7 GHz instead of 3 GHz for the other supported devices.
>
> Add a vco_max field to the chip info field to allow to specify a per device
> variant maximum VCO frequency.
>
> Signed-off-by: Lars-Peter Clausen <lars@metafoo.de>
> ---
Applied to clk-next
next prev parent reply other threads:[~2023-01-18 18:57 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-14 23:34 [PATCH 1/3] clk: vc5: Use `clamp()` to restrict PLL range Lars-Peter Clausen
2023-01-14 23:34 ` [PATCH 2/3] clk: vc5: Add support for 5P49V60 Lars-Peter Clausen
2023-01-16 8:15 ` Luca Ceresoli
2023-01-18 18:57 ` Stephen Boyd [this message]
2023-01-14 23:35 ` [PATCH 3/3] dt-bindings: clock: versaclock5: Document 5P49V60 compatible string Lars-Peter Clausen
2023-01-15 14:55 ` Krzysztof Kozlowski
2023-01-16 8:15 ` Luca Ceresoli
2023-01-18 18:57 ` Stephen Boyd
2023-01-16 8:15 ` [PATCH 1/3] clk: vc5: Use `clamp()` to restrict PLL range Luca Ceresoli
2023-01-18 18:57 ` Stephen Boyd
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=4121e6f0d8c0cb71df9736daa5ddaaee.sboyd@kernel.org \
--to=sboyd@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=lars@metafoo.de \
--cc=linux-clk@vger.kernel.org \
--cc=luca.ceresoli@bootlin.com \
--cc=mturquette@baylibre.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 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.