Feature: FTDI structure clarity & documentation #1627
Merged
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.
Detailed description
This PR sets out to clean up the FTDI port state structure, document it, document where to find the MPSSE protocol and command documentation, and clean up the use of that structure.
This was spurred on when helping @lethalbit figure out how to describe the Kria SOM KV260's FTDI device pinout and getting caught up on what all the bits meant and did, resulting in us having to read the source and FTDI documentation to figure it out.
Tested against Tigard
Your checklist for this pull request
make PROBE_HOST=native
)make PROBE_HOST=hosted
)Closing issues