Add FTDI bit-bang GPIO output support#1931
Open
ozan956 wants to merge 5 commits into
Open
Conversation
2 tasks
Codecov Report❌ Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## master #1931 +/- ##
========================================
+ Coverage 61.0% 61.7% +0.6%
========================================
Files 182 184 +2
Lines 14881 15077 +196
========================================
+ Hits 9083 9308 +225
+ Misses 5798 5769 -29
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Harness. |
Add local and remote resources for FTDI data-bus GPIO lines exposed through asynchronous bit-bang mode. The resource models one output-capable bit on a selected FTDI interface and exports the USB identity, interface, index, and inversion metadata needed by the driver. Signed-off-by: Ozan Durgut <ozan.durgut@analog.com>
ozan956
force-pushed
the
driver/ftdi-bit-bang
branch
from
July 13, 2026 11:30
7399617 to
b99030c
Compare
Add FTDIGPIODriver and a labgrid agent for FTDI asynchronous bit-bang GPIO outputs. The agent opens the selected USB interface per operation, sets async bit-bang mode with the data bus configured as output, reads the current pin byte, and writes back only the requested bit change. Signed-off-by: Ozan Durgut <ozan.durgut@analog.com>
Allow labgrid-client io to create an FTDIGPIODriver for acquired NetworkFTDIGPIO resources. Signed-off-by: Ozan Durgut <ozan.durgut@analog.com>
Cover FTDI GPIO resource validation, supported USB IDs, driver set/get behavior, agent read-modify-write output handling, exporter parameters, and labgrid-client io integration. Signed-off-by: Ozan Durgut <ozan.durgut@analog.com>
Document FTDIGPIO and NetworkFTDIGPIO resources for FTDI asynchronous bit-bang data-bus outputs. Signed-off-by: Ozan Durgut <ozan.durgut@analog.com>
ozan956
force-pushed
the
driver/ftdi-bit-bang
branch
from
July 14, 2026 10:47
b99030c to
5ba2f44
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This adds
FTDIGPIOresource, anFTDIGPIODriver, and a small USB agent. The feature is intended for boards where FTDI data-bus pins are used as simple digital outputs, for example to control straps, enables, reset-like signals, or other board control lines during tests.This targets FTDI asynchronous bit-bang GPIO on the data bus pins. It does not target CBUS GPIO, EEPROM-configured ACBUS functions, or generic MPSSE GPIO.
Supported devices are:
0403:6010, interfaces1..20403:6011, interfaces1..40403:6014, interface1Each interface exposes an independent 8-bit data bus.
indexselects bit0..7on that interface.For writes, the agent first reads the current pin byte, modifies only the requested bit, and writes the byte back. This avoids unintentionally changing other bits on the same FTDI interface.
get()reads the current level of the configured output line.I also would like to support input pins with
directionfeature of those chips in future, so #1458 would be very helpful.I tested the driver with a FT232H device (
0403:6014).Checklist