[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20260107194802.3917-1-rafael.v.volkmer@gmail.com>
Date: Wed, 7 Jan 2026 16:47:58 -0300
From: "Rafael V. Volkmer" <rafael.v.volkmer@...il.com>
To: ukleinek@...nel.org
Cc: g-praveen@...com,
j-keerthy@...com,
linux-kernel@...r.kernel.org,
linux-pwm@...r.kernel.org,
n-francis@...com,
rafael.v.volkmer@...il.com,
u-kumar1@...com
Subject: Re: [PATCH v2] pwm: tiehrpwm: Enable EHRPWM controller before setting configuration
Hi Uwe, Gokul,
Thanks for CC'ing me on this thread.
On 07/01/26 15:21, Uwe Kleine-König wrote:
> Hello,
>
> adding Rafael to Cc: who sent a patch series for this driver that I
> didn't come around to review yet. Given that neither he nor me noticed
> the problem addressed in this patch I wonder if it applies to all
> hardware variants.
>
I also didn't observe the issue described here in my testing: duty cycle and
period changes always appeared to take effect as expected.
My tests were done on an AM623 EVM.
One possible explanation is that my test flow mostly exercised configuration
while the PWM was already enabled/active, which could mask the effect of a
put_sync/reset happening after configuration.
Regarding my pending patch series for this driver: it should not
conflict this change, as it's largely preparatory refactoring for a
follow-up series.
Best regards,
Rafael V. Volkmer
Powered by blists - more mailing lists