From: Thierry Reding <thierry.reding@gmail.com>
To: "Jerome Brunet" <jbrunet@baylibre.com>,
"Martin Blumenstingl" <martin.blumenstingl@googlemail.com>,
"Kevin Hilman" <khilman@baylibre.com>,
"Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>,
"Neil Armstrong" <neil.armstrong@linaro.org>,
"Heiner Kallweit" <hkallweit1@gmail.com>
Cc: linux-arm-kernel@lists.infradead.org,
"open list:ARM/Amlogic Meson..."
<linux-amlogic@lists.infradead.org>,
linux-pwm@vger.kernel.org,
Dmitry Rokosov <ddrokosov@sberdevices.ru>
Subject: Re: [PATCH v5 0/6] pwm: meson: make full use of common clock framework
Date: Fri, 23 Jun 2023 16:51:35 +0200 [thread overview]
Message-ID: <168753171964.1191890.9331410157279790777.b4-ty@gmail.com> (raw)
In-Reply-To: <aa498590-261c-4ada-63ff-8d7aaeec0932@gmail.com>
On Wed, 24 May 2023 21:45:55 +0200, 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:
>
> [...]
Applied, thanks!
[1/6] pwm: meson: modify and simplify calculation in meson_pwm_get_state
commit: 6b9352f3f8a1a35faf0efc1ad1807ee303467796
[2/6] pwm: meson: fix handling of period/duty if greater than UINT_MAX
commit: 87a2cbf02d7701255f9fcca7e5bd864a7bb397cf
[3/6] pwm: meson: remove not needed check in meson_pwm_calc
commit: bafa23b6c07caac63a9637e83a605c26771b43ee
[4/6] pwm: meson: switch to using struct clk_parent_data for mux parents
commit: ed73300326ec67d2a0c35fb7f911314cc6d7d918
[5/6] pwm: meson: don't use hdmi/video clock as mux parent
commit: 3bddf73285d578a1798189e0eed2e7f82ebf0e11
[6/6] pwm: meson: make full use of common clock framework
commit: 329db102a26da0ba876974dbe04308d08acfad94
Best regards,
--
Thierry Reding <thierry.reding@gmail.com>
_______________________________________________
linux-amlogic mailing list
linux-amlogic@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-amlogic
prev parent reply other threads:[~2023-06-23 14:52 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-24 19:45 Heiner Kallweit
2023-05-24 19:47 ` [PATCH v5 RESEND 1/6] pwm: meson: modify and simplify calculation in meson_pwm_get_state Heiner Kallweit
2023-05-24 19:48 ` [PATCH v5 RESEND 2/6] pwm: meson: fix handling of period/duty if greater than UINT_MAX Heiner Kallweit
2023-05-24 19:49 ` [PATCH v5 RESEND 3/6] pwm: meson: remove not needed check in meson_pwm_calc Heiner Kallweit
2023-05-24 19:50 ` [PATCH v5 4/6] pwm: meson: switch to using struct clk_parent_data for mux parents Heiner Kallweit
2023-05-24 19:51 ` [PATCH v5 5/6] pwm: meson: don't use hdmi/video clock as mux parent Heiner Kallweit
2023-05-24 19:52 ` [PATCH v5 6/6] pwm: meson: make full use of common clock framework Heiner Kallweit
2023-06-23 14:51 ` Thierry Reding [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=168753171964.1191890.9331410157279790777.b4-ty@gmail.com \
--to=thierry.reding@gmail.com \
--cc=ddrokosov@sberdevices.ru \
--cc=hkallweit1@gmail.com \
--cc=jbrunet@baylibre.com \
--cc=khilman@baylibre.com \
--cc=linux-amlogic@lists.infradead.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-pwm@vger.kernel.org \
--cc=martin.blumenstingl@googlemail.com \
--cc=neil.armstrong@linaro.org \
--cc=u.kleine-koenig@pengutronix.de \
/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®