Skip to content

Commit

Permalink
Merge pull request pulp-platform#96 from pulp-platform/clarify-master…
Browse files Browse the repository at this point in the history
…-atop

README: Clarify requirements on `aw_atop`
  • Loading branch information
andreaskurth authored Apr 23, 2020
2 parents 57604bf + fd7e0ce commit a9bddae
Showing 1 changed file with 4 additions and 2 deletions.
6 changes: 4 additions & 2 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -43,8 +43,10 @@ This is the implementation of the AMBA AXI protocol developed as part of the PUL

AXI4+ATOPs means the full AXI4 specification plus atomic operations (ATOPs) as defined in Section E2.1 of the AMBA5 specification. This has the following implications for modules that do not implement ATOPs and systems that include such modules:

- Masters that do not issue ATOPs can simply permanently set `aw_atop` to `0`.
- Masters that do not issue ATOPs must set `aw_atop` to `'0`.
- Slaves that do not support ATOPs must specify this in their interface documentation and can ignore the `aw_atop` signal.
- System designers are responsible for ensuring that slaves that do not support ATOPs are behind an [`axi_atop_filter`](src/axi_atop_filter.sv) if any master could issue an ATOP to such slaves.
- System designers are responsible for ensuring that
1. slaves that do not support ATOPs are behind an [`axi_atop_filter`](src/axi_atop_filter.sv) if any master could issue an ATOP to such slaves and
2. the `aw_atop` signal is well-defined at the input of any (non-AXI4-Lite) module in this repository.

Masters and slaves that do support ATOPs must adhere to Section E2.1 of the AMBA5 specification.

0 comments on commit a9bddae

Please sign in to comment.