From: Gokul Praveen <g-praveen@ti.com>
To: "Rafael V. Volkmer" <rafael.v.volkmer@gmail.com>, <ukleinek@kernel.org>
Cc: <j-keerthy@ti.com>, <linux-kernel@vger.kernel.org>,
<linux-pwm@vger.kernel.org>, <n-francis@ti.com>,
<u-kumar1@ti.com>, "Gokul Praveen" <g-praveen@ti.com>
Subject: Re: [PATCH v2] pwm: tiehrpwm: Enable EHRPWM controller before setting configuration
Date: Thu, 8 Jan 2026 12:10:35 +0530 [thread overview]
Message-ID: <60da27d5-5d85-4fbe-9b18-b7e74f9ab893@ti.com> (raw)
In-Reply-To: <20260107194802.3917-1-rafael.v.volkmer@gmail.com>
Hi Rafael,
On 08/01/26 01:17, Rafael V. Volkmer wrote:
> 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.
>
Yes, this is the reason why the configuration was taking effect for you
, Rafael, as the PWM was already enabled when setting the configuration
hence masking the effect of a put_sync/reset happening after configuration.
Best Regards
Gokul Praveen
> 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
next prev parent reply other threads:[~2026-01-08 6:40 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-07 5:53 Gokul Praveen
2026-01-07 9:51 ` Uwe Kleine-König
2026-01-07 10:23 ` Gokul Praveen
2026-01-07 19:47 ` Rafael V. Volkmer
2026-01-08 6:40 ` Gokul Praveen [this message]
2026-01-08 18:10 ` Uwe Kleine-König
2026-01-09 5:51 ` Gokul Praveen
2026-01-09 22:53 ` Uwe Kleine-König
2026-01-12 5:51 ` Gokul Praveen
2026-01-12 7:22 ` Uwe Kleine-König
2026-01-19 15:00 ` Kumar, Udit
2026-01-19 21:33 ` Uwe Kleine-König
2026-01-20 4:40 ` Kumar, Udit
2026-01-20 5:53 ` Gokul Praveen
2026-01-20 8:23 ` Uwe Kleine-König
2026-01-20 8:34 ` Gokul Praveen
2026-01-15 10:32 ` Gokul Praveen
2026-01-15 17:17 ` Uwe Kleine-König
2026-01-16 8:41 ` Gokul Praveen
2026-01-16 9:10 ` Gokul Praveen
2026-01-19 2:55 ` Rafael V. Volkmer
2026-01-19 6:48 ` Gokul Praveen
2026-01-15 5:20 ` Kumar, Udit
2026-01-15 6:14 ` Gokul Praveen
2026-01-15 7:46 ` Kumar, Udit
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=60da27d5-5d85-4fbe-9b18-b7e74f9ab893@ti.com \
--to=g-praveen@ti.com \
--cc=j-keerthy@ti.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pwm@vger.kernel.org \
--cc=n-francis@ti.com \
--cc=rafael.v.volkmer@gmail.com \
--cc=u-kumar1@ti.com \
--cc=ukleinek@kernel.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®