60 | | The initiator activity corresponds to the boolean member '''m_activity''' that indicates if the initiator is currently active. |
61 | | This boolean variable is used by the arbitration threads i.e. '''true''', wants to participate in the arbitration in the interconnect) or inactive (i.e. '''false''', does not want |
62 | | to participate in the arbitration in the interconnect). The corresponding access functions are '''setActivity()''' and '''getActivity()'''. |
| 60 | The boolean member variable '''m_activity''' indicates if the initiator is currently active. |
| 61 | It is used by the arbitration threads contained in the '''vci_vgmn''' interconnect, as described in section E. |
| 62 | The corresponding access functions are '''setActivity()''' and '''getActivity()'''. |
74 | | This member variable represents the VCI initiator port. It has 3 template parameters, two of which are used to help |
75 | | connecting the response callback function ('''my_initiator''' in the example, first template parameter) to the port and |
76 | | defining the port type |
77 | | ('''soclib_vci_types''' in the following example, third template parameter). '''soclib_vci_types''' is indeed a C++ structure containing two |
78 | | typedef: the first typedef defines the payload type as VCI, and the other defines the TLM phase type. The phase type can either |
79 | | be '''TLMT_CMD''' (i.e. the transaction indicates the emission of a command by an initiator and its reception by a target), |
80 | | '''TLMT_RSP''' (i.e. the transaction indicates the emission of a response by a target and its reception by an initiator), |
81 | | or '''TLMT_INFO''' (i.e. a TLM-T transaction emitted by one side of a link (vci, irq or fifo) to get information such as time |
82 | | and activity on the other side of the link). |
| 73 | This member variable represents the VCI initiator port. |