From: "Uwe Kleine-König" <ukleinek@kernel.org>
To: "A. Sverdlin" <alexander.sverdlin@siemens.com>
Cc: linux-pwm@vger.kernel.org, "Philip,
Avinash" <avinashphilip@ti.com>,
Thierry Reding <thierry.reding@avionic-design.de>,
linux-kernel@vger.kernel.org, stable@vger.kernel.org
Subject: Re: [PATCH] pwm: tiehrpwm: Clear period on disable to allow reconfiguration
Date: Wed, 30 Sep 2026 08:29:52 +0200 [thread overview]
Message-ID: <aryop_9K29U4i5Sy@monoceros> (raw)
In-Reply-To: <20260929120806.2790355-1-alexander.sverdlin@siemens.com>
[-- Attachment #1: Type: text/plain, Size: 2098 bytes --]
Hello Alexander,
On Tue, Sep 29, 2026 at 02:08:02PM +0200, A. Sverdlin wrote:
> From: Alexander Sverdlin <alexander.sverdlin@siemens.com>
>
> Both channels share one period register, so ehrpwm_pwm_config() rejects a
> period differing from the sibling's period_cycles[]. That value was cleared
> only in .free(), not in .disable(), so a stopped channel kept blocking the
> sibling from switching to a new frequency. Clear it in .disable() too.
>
> Testcase:
>
> cd /sys/class/pwm/pwmchip0; echo 0 > export; echo 1 > export
> for p in pwm0 pwm1; do
> echo 1000000 > $p/period; echo 500000 > $p/duty_cycle
> echo 1 > $p/enable; echo 0 > $p/enable; echo 2000000 > $p/period
> done
> echo 1 > pwm0/enable # before: -EINVAL, after: succeeds
>
> Fixes: 01b2d4536f02 ("pwm: pwm-tiehrpwm: Fix conflicting channel period setting")
> Cc: stable@vger.kernel.org
> Signed-off-by: Alexander Sverdlin <alexander.sverdlin@siemens.com>
> ---
> drivers/pwm/pwm-tiehrpwm.c | 3 +++
> 1 file changed, 3 insertions(+)
>
> diff --git a/drivers/pwm/pwm-tiehrpwm.c b/drivers/pwm/pwm-tiehrpwm.c
> index 3a53489f0b982..e3407d0a1f7fe 100644
> --- a/drivers/pwm/pwm-tiehrpwm.c
> +++ b/drivers/pwm/pwm-tiehrpwm.c
> @@ -358,6 +358,9 @@ static void ehrpwm_pwm_disable(struct pwm_chip *chip, struct pwm_device *pwm)
>
> /* Disable clock on PWM disable */
> pm_runtime_put_sync(pwmchip_parent(chip));
> +
> + /* A disabled channel must not constrain the sibling's period */
> + pc->period_cycles[pwm->hwpwm] = 0;
> }
>
> static void ehrpwm_pwm_free(struct pwm_chip *chip, struct pwm_device *pwm)
That looks right, applied to
https://git.kernel.org/pub/scm/linux/kernel/git/ukleinek/linux.git pwm/for-next
as merge window material.
Looking at the driver, the check for the sibling running could be
weakend a bit. So if the restriction by the other channel only results
in a smaller period, configuration could continue.
(But if you're looking for something to do, better invest the time and
convert the driver to waveform.)
Thanks,
Uwe
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
prev parent reply other threads:[~2026-09-30 6:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-29 12:08 A. Sverdlin
2026-09-30 6:29 ` Uwe Kleine-König [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=aryop_9K29U4i5Sy@monoceros \
--to=ukleinek@kernel.org \
--cc=alexander.sverdlin@siemens.com \
--cc=avinashphilip@ti.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pwm@vger.kernel.org \
--cc=stable@vger.kernel.org \
--cc=thierry.reding@avionic-design.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®