From: Neil Armstrong <neil.armstrong@linaro.org>
To: linux-amlogic@lists.infradead.org
Subject: Re: [PATCH v4 0/4] pwm: meson: make full use of common clock framework
Date: Mon, 17 Apr 2023 09:19:24 +0200 [thread overview]
Message-ID: <9a384508-4645-6cfc-3e27-8a896b73a26b@linaro.org> (raw)
In-Reply-To: <9faca2e6-b7a1-4748-7eb0-48f8064e323e@gmail.com>
Hi Heiner,
On 13/04/2023 07:48, Heiner Kallweit wrote:
> Newer versions of the PWM block use a core clock with external mux,
> divider, and gate. These components either don't exist any longer in
> the PWM block, or they are bypassed.
> To minimize needed changes for supporting the new version, the internal
> divider and gate should be handled by CCF too.
>
> I didn't see a good way to split the patch, therefore it's somewhat
> bigger. What it does:
>
> - The internal mux is handled by CCF already. Register also internal
> divider and gate with CCF, so that we have one representation of the
> input clock: [mux] parent of [divider] parent of [gate]
>
> - Now that CCF selects an appropriate mux parent, we don't need the
> DT-provided default parent any longer. Accordingly we can also omit
> setting the mux parent directly in the driver.
>
> - Instead of manually handling the pre-div divider value, let CCF
> set the input clock. Targeted input clock frequency is
> 0xffff * 1/period for best precision.
>
> - For the "inverted pwm disabled" scenario target an input clock
> frequency of 1GHz. This ensures that the remaining low pulses
> have minimum length.
>
> I don't have hw with the old PWM block, therefore I couldn't test this
> patch. With the not yet included extension for the new PWM block
> (channel->clock directly coming from get_clk(external_clk)) I didn't
> notice any problem. My system uses PWM for the CPU voltage regulator
> and for the SDIO 32kHz clock.
Don't you have any GXBB, GXL, GXM, G12A, SM1 or G12B boards to test on ?
Anyway, I'd like to see a complete test on those SoCs on the actually
used function (mainly 32k output clock for wifi) before seeing this merges
since it's a big change.
>
> Note: The clock gate in the old PWM block is permanently disabled.
> This seems to indicate that it's not used by the new PWM block.
>
> Changes to RFT/RFC version:
> - use parent_hws instead of parent_names for div/gate clock
> - use devm_clk_hw_register where the struct clk * returned by
> devm_clk_register isn't needed
>
> v2:
> - add patch 1
> - add patch 3
> - switch to using clk_parent_data in all relevant places
>
> v3:
> - patch 1: move setting mux parent data out of the loop
> - patch 4: add flag CLK_IGNORE_UNUSED
>
> v4:
> - patch 2: improve commit message
> - patch 4: remove variable tmp in meson_pwm_get_state
> - patch 4: don't use deprecated function devm_clk_register
>
> Heiner Kallweit (4):
> pwm: meson: switch to using struct clk_parent_data for mux parents
> pwm: meson: don't use hdmi/video clock as mux parent
> pwm: meson: change clk/pwm gate from mask to bit
> pwm: meson: make full use of common clock framework
>
> drivers/pwm/pwm-meson.c | 201 +++++++++++++++++++++-------------------
> 1 file changed, 107 insertions(+), 94 deletions(-)
>
_______________________________________________
linux-amlogic mailing list
linux-amlogic@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-amlogic
prev parent reply other threads:[~2023-04-17 7:19 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-13 5:48 Heiner Kallweit
2023-04-13 5:49 ` [PATCH v4 1/4] pwm: meson: switch to using struct clk_parent_data for mux parents Heiner Kallweit
2023-04-13 5:50 ` [PATCH v4 2/4] pwm: meson: don't use hdmi/video clock as mux parent Heiner Kallweit
2023-04-13 5:51 ` [PATCH v4 3/4] pwm: meson: change clk/pwm gate from mask to bit Heiner Kallweit
2023-04-13 5:54 ` [PATCH v4 4/4] pwm: meson: make full use of common clock framework Heiner Kallweit
2023-04-14 19:39 ` Martin Blumenstingl
2023-04-15 6:39 ` Heiner Kallweit
2023-04-16 19:26 ` Martin Blumenstingl
2023-04-16 21:34 ` Heiner Kallweit
2023-04-23 20:55 ` Martin Blumenstingl
2023-04-17 7:23 ` Neil Armstrong
2023-04-17 9:17 ` Thierry Reding
2023-04-17 9:53 ` Heiner Kallweit
2023-04-17 9:59 ` neil.armstrong
2023-04-17 10:36 ` Heiner Kallweit
2023-04-17 12:21 ` neil.armstrong
2023-04-19 19:58 ` Heiner Kallweit
2023-04-21 7:39 ` neil.armstrong
2023-04-23 20:58 ` Martin Blumenstingl
2023-05-01 13:39 ` Heiner Kallweit
2023-05-19 15:30 ` Dmitry Rokosov
2023-05-19 16:53 ` Heiner Kallweit
2023-05-22 13:37 ` Dmitry Rokosov
2023-05-22 20:10 ` Heiner Kallweit
2023-05-23 10:28 ` Dmitry Rokosov
2023-05-23 19:22 ` Heiner Kallweit
2023-04-17 7:19 ` Neil Armstrong [this message]
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=9a384508-4645-6cfc-3e27-8a896b73a26b@linaro.org \
--to=neil.armstrong@linaro.org \
--cc=linux-amlogic@lists.infradead.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®