Skip to content

drivers.Pin with function pointers example #774

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

Draft
wants to merge 1 commit into
base: drivers-pin-interface
Choose a base branch
from

Conversation

ysoldak
Copy link
Contributor

@ysoldak ysoldak commented Jul 6, 2025

This showcases how we can split drivers.Pin to smaller drivers.PinIn and drivers.PinOut interfaces AND use function pointer to .Set(bool) function in performance critical places, like softspi implementation.

This still breaks users though, as it is based on a PR #749 that mandates pins to be configured outside the drivers.


type PinOut interface {
High() // deprecated: use Set(true)
Low() // deprecated: use Set(false)
Copy link
Contributor Author

Choose a reason for hiding this comment

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

I'd prefer we do not have these in the interface and sweep and eradicate call to them everywhere in drivers.

ResetPin drivers.PinOut
DataPin drivers.PinOut
ChipSelectPin drivers.PinOut
BusyPin drivers.PinIn
Copy link
Contributor Author

Choose a reason for hiding this comment

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

Showcase use of PinOut and PinIn interfaces.

@soypat
Copy link
Contributor

soypat commented Jul 7, 2025

This is pulled from a PR we agreed to not continue with at the moment. The design of #753 leaves us open for this design in the future if we so desire to go on with it.

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