Skip to content

Conversation

@jilaypandya
Copy link
Member

following the approach of transceiver.h in can driver subsystem, refactoring stepper_drv apis to stepper_drv.h

@jilaypandya jilaypandya force-pushed the refactor/stepper_drv.h branch from a1dc6fc to dc289da Compare December 14, 2025 12:33
Copy link
Member

@henrikbrixandersen henrikbrixandersen left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is nothing like what the CAN driver subsystem does (or any other driver subsystem for that matter).

What's the rationale behind this?

@jilaypandya
Copy link
Member Author

jilaypandya commented Dec 15, 2025

Ahh okay, i found the recent split that we introduced in Stepper driver subsystem i.e. Stepper (Stepper Controller) and Stepper-DRV (Stepper driver) highly analogous to how CAN Controller and CAN Transceiver APIs are structured. But maybe i am missing out on something :)

following the approach of transceiver.h in can driver subsystem,
refactoring stepper_drv apis to stepper_drv.h

Signed-off-by: Jilay Pandya <[email protected]>
@jilaypandya jilaypandya force-pushed the refactor/stepper_drv.h branch from dc289da to aa14231 Compare December 15, 2025 06:36
@sonarqubecloud
Copy link

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.

2 participants