This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

About IPC v3.0



Hi,

I recently noticed the major update of IPC was released (IPC 3.0). It looks like IPC including SysLink functionality.
I briefly checked it out and found that the implementation of HLOS side driver had already been changed drastically and now MessageQ looks like the main and only communication interface between HLOS and BIOS. No RingIO and FrameQ is supported.

So, do you have any plan to support RingIO/FrameQ as a component of IPC in the future ?
To me, RingIO was good interface especially.

Best Regards,
Kawada 

  • Hi Ti guys,

    Do you have any comments on this ?

    Regards,
    Kawada 

  • Hi, Kawada.

    There are no current plans for adding high-level frameworks like RingIO or FrameQ to IPC 3.x.  Those APIs in particular have historically been very complex and difficult to support (you can read that as buggy).  Further, their actual usage has been quite limited (you can read that as not worth the support cost).

    Our approach for RingIO (and frameworks like it) is to provide core services in IPC (e.g. MessageQ, GateMP, etc) but not provide RingIO directly.  I do know of some internal projects within TI that are building RingIO on top of IPC 3.x.  I don't know if we'll ultimately be providing RingIO as an independent API or not, but I think we're waiting to see if there's interest/need.

    If you don't mind sharing, what type of application and device families are you interested in using RingIO with?

    Finally, if you haven't already seen it, this article provides more details about IPC 3.x you may find helpful:
         
    http://processors.wiki.ti.com/index.php/IPC_3.x

    Chris

  • Hi Chris,

    Thank you for your response. As for URL, I have already checked it. 
    As you said, supporting RingIO/FrameQ for the logical connection between HLOS and SYS/BIOS may be too much and its task can be moved to the middle ware at HLOS side. But I think it would be great if you support RingIO/FrameQ as the components of SYS/BIOS or IPC. For example, Data Flow Model is still being used on Keystone and single core platform with SYS/BIOS operating system and in this case, RingIO/FrameQ can be a logical bridge between each functional software modules. Also, thanks to RingIO/FrameQ, the dependencies between the software components can be abstracted. It means user can develop more reusable and scaleable software components.

    Hope you consider such use case.

    Regards,
    Kawada