Add GPIO pullup configurations and fix PWM Segfault on kernel 4.1+ #119
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Add fix to no longer ignore GPIO pullup configurations in GPIO.setup by using ocp pinmux
Move PWM disable code for Kernel 4.1x to prevent segfault caused by writing to closed file handle
Added check in c_pinmux to handle bonescript format pin names eg P8_8, convert to P8_08 for ocp pinmux.
Call pinmux in py_setup_channel when setting up an input to allow configuration of pullup.
Add pinmux into GPIO compilation in setup.py
Moved the BBBVERSION41 section in pwm_disable to inside the loop checking for open pwm handles. Running stop without start resulted in a segfault from seeking/writing to a closed or non-existant enable_fd
Known Limitations
Tested only with Kernel 4.4 on bone-debian-8.4-iot build 2015-05-13
Changes were made with consideration of kernel < 4.1 but not tested