Harmony v2.03b I2C驱动程序动态中断

我正在尝试使用这个驱动程序（这是在Alpha发行注释中标注为alpha），所以这对我的智慧来说并不多。到目前为止，它的工作方式是多方面的。然而，回调函数上的文档（DrimeRealReaveSeV111的第424页）似乎表明我可以使用上下文并在回调上下文中拥有它。当调用EvEnthDrand函数时，参数的值将被传递回客户端。它可以用来标识任何客户端特定的数据对象，该对象标识客户端模块的实例（例如，它可能是指向客户端模块的状态结构的指针）。但是，无论我用BuffReEvEnthDeleLSET发送到上下文中，都在回调上下文＝0x00中。在驱动状态机中快速查看，我注意到这看起来像在不包含上下文的情况下触发回调……但是它对我来说很神秘，所以我可以解释它是错误的。有人知道这件事吗？更新：看起来，如果你改变了看起来像上面ToT的线条使上下文特征工作。那么我想我正在得到alpha’d。也许有人应该解决这个问题，或者我可能在文档中漏掉了，因为它说它没有实现。



      以下为原文

    I am trying to use this driver (which is labeled Alpha in the HARMony release notes so this doesn't say much for my wisdom). It is working in most ways so far. However, the documentation (page 424 of DriverLibraries_v111) on the callback function seems to indicate I can use the context and have it in the callback.

context The value of parameter will be passed back to the client unchanged, when the eventHandler function is called. It can be used to identify any client specific data object that identifies the instance of the client module (for example, it may be a pointer to the client module's state structure).

void DRV_I2C_BufferEventHandlerSet (
const DRV_HANDLE handle,
const DRV_I2C_BUFFER_EVENT_HANDLER eventHandler,
const uintptr_t context )

But whatever I send into context using BufferEventHandlerSet, inside the callback context = 0x00. A quick look in the driver state machine and I noticed this
                                /* Give an indication to the higher layer upon successful transmission */
                                _DRV_I2C_CLIENT_OBJ(((DRV_I2C_CLIENT_OBJ *)lBufferObj->clientHandle), callback)
                                      ( DRV_I2C_BUFFER_EVENT_COMPLETE, (DRV_I2C_BUFFER_HANDLE)lBufferObj, 0x00 );

Which looks like firing the callback without including the context...but it's pretty cryptic to me so I could be interpreting it wrong.  Anybody know anything about this?

UPDATE:
Looks like if you change the lines that look like the above to
                    /* Give an indication to the higher layer upon successful transmission */
                    _DRV_I2C_CLIENT_OBJ(((DRV_I2C_CLIENT_OBJ *)lBufferObj->clientHandle), callback)
                    ( _DRV_I2C_CLIENT_OBJ(lBufferObj, status), (DRV_I2C_BUFFER_HANDLE)lBufferObj, ((DRV_I2C_CLIENT_OBJ *)lBufferObj->clientHandle)->context);

It makes the context feature work.

So I guess I am getting Alpha'd.  Probably somebody important should fix this or possibly I missed in the documentation where it says it is unimplemented.