Deprecate and remove support for uncommon options in output_pin #6458
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.
Over the last few years the
output_pin
module has gained a handful of options that have made it harder to maintain the the low-level backend code. This PR simplifies the output_pin module. The main changes are:static_value
parameter is deprecated. This option has little impact - it only saves a few bytes in the micro-controller. Going forward it is simple enough to just not specify it.maximum_mcu_duration
parameter is deprecated. Thepwm_tool
module is a better choice for tools that require this capability. It should be straight forward for users to change their configs from[output_pin mypin]
to[pwm_tool mypin]
.SET_PIN CYCLE_TIME=x
g-code command for[output_pin mypin]
config sections has been removed. Users can convert to a new[pwm_cycle_time mypin]
config as a replacement. This change is setup to take effect immediately (no deprecation period).This is the last PR as part of the
pwm_tool
series of changes (eg, #6369, #6410, #6420).@Cirromulus - fyi.
-Kevin