Skip to content

Commit

Permalink
ftdi: document potential use of different latency value
Browse files Browse the repository at this point in the history
  • Loading branch information
maruel committed May 29, 2021
1 parent 88a2d4f commit 37d3270
Showing 1 changed file with 9 additions and 1 deletion.
10 changes: 9 additions & 1 deletion ftdi/handle.go
Original file line number Diff line number Diff line change
Expand Up @@ -117,7 +117,15 @@ func (h *handle) Init() error {
if e := h.h.SetChars(0, false, 0, false); e != 0 {
return toErr("SetChars", e)
}
// Not sure: Latency timer at 1ms.
// TODO(maruel): Set latency timer at 255ms in MPSSE mode? The rationale is
// that for FT232H, the MPSSE command 'flush' should consistently used
// whenever needed and we want this to be apparent. Investigate the effect
// for FT232R so potentially move to InitNonMPSSE and InitMPSSE with
// different values.
//
// The documentation recommends to use at least 2ms as 1ms is the frame
// length. It doesn't make sense to me, as we should only want to read what
// was already pushed.
if e := h.h.SetLatencyTimer(1); e != 0 {
return toErr("SetLatencyTimer", e)
}
Expand Down

0 comments on commit 37d3270

Please sign in to comment.