• State Not Answered
  • Locked Locked
  • Replies 4 replies
  • Subscribers 88 subscribers
  • Views 9254 views
  • Users 0 members are here
Options
Related
How was your experience today?
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

AXI protocol

neha004
Note: This was originally posted on 30th December 2007 at http://forums.arm.com

Can anyone tell me the exact explanation and differnce between out of order completion and write data interleaving  in detail...as i`m very confused with these terms
Parents
  • 0
    Note: This was originally posted on 9th January 2008 at http://forums.arm.com

    Hi,

    case1---same master different ID tag and interleaving depth is 1....


    If the interleaving depth is set to 1, it won't be able to interleave data regardless of the ID.

    case2...different master with different ID Tag


    If the slave is able to interleave data, and the interconnect is aware of this, then it could arrive at the slave in any order. This assumes that the interconnect is able to interleave data as well, and that the first items of write data have been received in the same order as the addresses were issued.

    case3...different master but same ID tag...


    If you have multiple masters, then you will have some kind of interconnect logic between these and the slave/s. I would expect the interconnect to add bits to the ID fields from these masters to enable routing on the non-address channels. So whilst both masters may issue a transaction with the same ID, the slave will actually see two different IDs. In this case, the slave could see the data in any order (assuming the interconnect can interleave data)

    HTH
Reply
  • 0
    Note: This was originally posted on 9th January 2008 at http://forums.arm.com

    Hi,

    case1---same master different ID tag and interleaving depth is 1....


    If the interleaving depth is set to 1, it won't be able to interleave data regardless of the ID.

    case2...different master with different ID Tag


    If the slave is able to interleave data, and the interconnect is aware of this, then it could arrive at the slave in any order. This assumes that the interconnect is able to interleave data as well, and that the first items of write data have been received in the same order as the addresses were issued.

    case3...different master but same ID tag...


    If you have multiple masters, then you will have some kind of interconnect logic between these and the slave/s. I would expect the interconnect to add bits to the ID fields from these masters to enable routing on the non-address channels. So whilst both masters may issue a transaction with the same ID, the slave will actually see two different IDs. In this case, the slave could see the data in any order (assuming the interconnect can interleave data)

    HTH
Children
No data