GPIF2 Designer指南特殊功能模糊

我想澄清在GPIF 2设计师指南，关于“特殊功能”信号OE，我们，DLE，DACK和DRQ的一些含糊不清。
他们的主要文件，在用户指南，第16页，也有讨论在第51页，也在AN8216P13。
1。结合所有这些页面的信息，据我所知，OE和我们做同样的事情。如果这不是真的，那么他们做什么不同呢？
2a。对于信号DLE，UG-P16表示DLE用于将数据锁存到输入级。如果是这样的话，既然它和我们一样，那么这应该是我们和OE之间的区别吧？GPIO 18（W/DLE）执行输入数据捕获和输出驱动器启用/禁用，而GPIOY19仅执行驱动器禁用？
但是，假设UG-P51和AN8216P13是矛盾的，我们知道DLE不是用来捕获输入数据本身，而是为了扩展输入数据保持时间。那是什么？数据捕获，还是扩展输入数据保持时间？
2c，我们和/或DLE与iNi数据动作之间的关系是什么，它似乎能够完全基于其他输入信号捕获输入数据。
三。DRQ和DACK：DOC将DRQ描述为DMA请求（从FX3到外部设备），这似乎很好。但是DOCS将DACK（DMA确认）描述为“用于控制DRQ信号的行为的输入”。这个解释对我来说似乎无关紧要。
DACK的目的当然不是控制DRQ本身。DRQ和DACK肯定一起工作来操作FX3侧状态机，并与外部设备侧的DMA设施交互，以便FX3从外部设备获取数据或发送数据到外部设备。
3A，不清楚DRQ/DACK信号是否直接与FX3内部DMA设备相关，或者是一个单独的机制，可能是为了与外部设备的DMA设施一起工作？
3B。DRQ/DACK如何或不涉及DMANYADE和…水印信号还不清楚。
3C。目前还不清楚DRQ/DACK是否与GPIF状态机分开运行。如果它们需要GPIF状态机，那么这些信号在特定引脚上的意义是什么，因为大概GPIF状态机可以在任何GPIOS上实现这些功能吗？
还有一些其他的含糊不清和差距，但是让我们从这些开始。——Graham



     以下为原文
  I would like to get clarified some ambiguities in the GPIF 2 Designer Guide, regarding "special function" signals OE, WE, DLE, DACK and DRQ.

Their primary documentation, is in User Guide, on page 16, and there's also discussion on page 51, and also in AN87216 p13.

1. Combining info on all those pages, so far as I can tell, OE and WE do the same thing. If this is not true, then what do they do different?

2a. For signal DLE, UG-p16 says that DLE is used to latch the data into the input stage. If that's the case, and since it's on the same pin as WE, perhaps that's supposed to be the difference between WE and OE?  GPIO 18 (WE/DLE) performs input data capture and output driver enable/disable, while GPIO_19 performs only driver disable?

2b. But that supposition is contradicted by UG-p51 and AN87216 p13 where we learn that DLE is not for capturing the input data per se, but rather just to extend the input data hold time. So which is it? Data capture, or extending input data hold time?

2c. And what is the relationship of WE and/or DLE to the IN_DATA action, which seems able to capture input data based on some other input signals altogether?

3. DRQ and DACK: Docs describe DRQ as DMA Request (from FX3 to external device), which seems fine. But then docs describe DACK (DMA Acknowledge) as "an input that is used to control the behavior of the DRQ signal".  This explanation seems nonsensical to me.

The purpose of DACK is surely not to control DRQ per se.  DRQ and DACK surely work together to operate an FX3-side state machine, and interact with the external-device-side's DMA facility, in order for the FX3 to fetch data from, or send data to, the external device.

3a. It's not clear whether the DRQ/DACK signals relate directly to FX3 internal DMA apparatus, or are a separate mechanism, perhaps intended to work with the DMA facility of the external device?

3b. It's not clear how DRQ/DACK do or don't relate to DMAn_Ready and ...Watermark signals.

3c. It's not clear whether DRQ/DACK operate separately from the GPIF state machine. If they require the GPIF state machine, then what is the significance of these signals being on specific pins, since presumably the GPIF state machine could implement these functions on any GPIOs?

There are some other ambiguities and gaps, but let's start with these please.  -- Graham