-
Notifications
You must be signed in to change notification settings - Fork 6.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
PCA9685 PWM driver is broken #18608
Comments
@tbursztyka I think this driver was added for an x86 platform that we have since removed. Are you wanting to use this on some other board? Curious how you are hitting this. |
@galak PCA9685 is an i2c slave device. There is no board using it yet, but what about zephyr user that would wire such device on a board? |
There are expansion boards with PCA9685, for example https://www.adafruit.com/product/815 |
Hi, Thanks sarvg |
Hi @vagotec if an overlay was written for the PCA9685 the following sample could be used: |
This issue has been marked as stale because it has been open (more than) 60 days with no activity. Remove the stale label or add a comment saying that you would like to have the label removed otherwise this issue will automatically be closed in 14 days. Note, that you can always re-open a closed issue at any time. |
Remove DW and PCA9685 PWM controller drivers as they are unmaintained and broken. Both drivers lack support for the pwm_get_cycles_per_sec_t API function which was introduced in commit 56e0b53 in 2016. Fixes zephyrproject-rtos#18607, zephyrproject-rtos#18608 Signed-off-by: Henrik Brix Andersen <[email protected]>
Remove DW and PCA9685 PWM controller drivers as they are unmaintained and broken. Both drivers lack support for the pwm_get_cycles_per_sec_t API function which was introduced in commit 56e0b53 in 2016. Fixes #18607, #18608 Signed-off-by: Henrik Brix Andersen <[email protected]>
It misses the API function get_cycles_per_sec() which is mandatory to get pwm.h public function to work.
So currently this driver just does not work at all due to that.
The text was updated successfully, but these errors were encountered: