Skip to content

Conversation

@raffarost
Copy link

@raffarost raffarost commented Dec 5, 2024

Reverts a change from #81198 regarding how the test checks the pulse output from a capture event. A pulse capture will produce a value that has the same polarity (and range) as programmed by pwm_capture(). Checking 'pulse_capture' against 'period - pulse' means expecting the driver to return a capture value that is not inverted as well, which would cause test cases to fail.

Reverts a change regarding how the test checks the pulse output
from a capture event. A pulse capture will produce a value that has
the same polarity (and range) as programmed by pwm_capture().
Checking 'pulse_capture' against 'period - pulse' means expecting
the driver to return a capture value that is not inverted as well,
which would cause test cases to fail.

Signed-off-by: Raffael Rostagno <[email protected]>
@sylvioalves
Copy link
Contributor

@ioannis-karachalios , as the owner of the reverted commit, can you take a look?

@kartben kartben merged commit 3054279 into zephyrproject-rtos:main Dec 18, 2024
21 checks passed
@raffarost raffarost deleted the fix/pwm_loopback branch December 18, 2024 17:06
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

area: PWM Pulse Width Modulation

Projects

None yet

Development

Successfully merging this pull request may close these issues.

7 participants