Skip to content

refactor(driver): move Flysky gimbal sync into board-level ADC callbacks#7263

Open
raphaelcoeffic wants to merge 1 commit intomainfrom
fs-gimbal-cleanup
Open

refactor(driver): move Flysky gimbal sync into board-level ADC callbacks#7263
raphaelcoeffic wants to merge 1 commit intomainfrom
fs-gimbal-cleanup

Conversation

@raphaelcoeffic
Copy link
Copy Markdown
Member

Flysky gimbal synchronization (HALL_SYNC GPIO for V1, command-based start_read/wait_completion for V2) was scattered across the HAL layer (adc_driver.cpp) and mixer task (mixer_task.cpp). This moves it into the board-level ADC callbacks in analog_inputs.cpp, matching the existing ADS79xx SPI ADC integration pattern.

The gimbal driver now owns all its synchronization: GPIO init, HALL_SYNC assert/deassert, and V2 command sequencing. No hardware-specific code remains in hal/ or tasks/.

Flysky gimbal synchronization (HALL_SYNC GPIO for V1, command-based
start_read/wait_completion for V2) was scattered across the HAL layer
(adc_driver.cpp) and mixer task (mixer_task.cpp). This moves it into
the board-level ADC callbacks in analog_inputs.cpp, matching the
existing ADS79xx SPI ADC integration pattern.

The gimbal driver now owns all its synchronization: GPIO init, HALL_SYNC
assert/deassert, and V2 command sequencing. No hardware-specific code
remains in hal/ or tasks/.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
@raphaelcoeffic raphaelcoeffic added this to the 3.0 milestone Apr 5, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant