From: George Stark <gnstark@salutedevices.com>
To: <u.kleine-koenig@pengutronix.de>, <neil.armstrong@linaro.org>,
<khilman@baylibre.com>, <jbrunet@baylibre.com>,
<martin.blumenstingl@googlemail.com>
Cc: <linux-pwm@vger.kernel.org>, <linux-amlogic@lists.infradead.org>,
<linux-arm-kernel@lists.infradead.org>,
<linux-kernel@vger.kernel.org>, <kernel@salutedevices.com>,
George Stark <gnstark@salutedevices.com>
Subject: [PATCH 0/3] pwm: meson: Support constant and polarity bits
Date: Mon, 7 Oct 2024 22:32:00 +0300 [thread overview]
Message-ID: <20241007193203.1753326-1-gnstark@salutedevices.com> (raw)
This patch series add suppot for amlogic's newer PWM IPs hardware features:
constant and polarity bits.
Using polarity bit for inverting output signal allows to identify inversion
in .get_state() callback which can only rely on data read from registers.
Using constant bit allows to have steady output level when duty sycle is zero or
equal to period. Without this bit there will always be single-clock spikes on output.
Those bits are supported in axg, g12 and newer SoC familes like s4, a1 etc.
Tested on g12, a1.
George Stark (3):
pwm: meson: Support constant and polarity bits
pwm: meson: Use separate chip data struct for g12a-ee-pwm
pwm: meson: Enable constant and polarity features for g12, axg, s4
drivers/pwm/pwm-meson.c | 94 ++++++++++++++++++++++++++++++++++++++---
1 file changed, 87 insertions(+), 7 deletions(-)
--
2.25.1
next reply other threads:[~2024-10-07 19:37 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-07 19:32 George Stark [this message]
2024-10-07 19:32 ` [PATCH 1/3] pwm: meson: Support constant and polarity bits George Stark
2024-10-08 7:30 ` neil.armstrong
2024-10-07 19:32 ` [PATCH 2/3] pwm: meson: Use separate chip data struct for g12a-ee-pwm George Stark
2024-10-08 7:30 ` neil.armstrong
2024-10-07 19:32 ` [PATCH 3/3] pwm: meson: Enable constant and polarity features for g12, axg, s4 George Stark
2024-10-08 7:31 ` neil.armstrong
2024-10-08 12:37 ` Jerome Brunet
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=20241007193203.1753326-1-gnstark@salutedevices.com \
--to=gnstark@salutedevices.com \
--cc=jbrunet@baylibre.com \
--cc=kernel@salutedevices.com \
--cc=khilman@baylibre.com \
--cc=linux-amlogic@lists.infradead.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.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