Andreas Kurth

> Just a heads up, the changes for the `xbar_pipeline` are required for the LLC. There is a bypass for uncached memory accesses using both an `axi_demux` and `axi_mux`. The...

> > A crossbar with multiple slave and master ports would contain in its inputs and outputs: > > ```systemverilog > > // Slave Ports > > input slv_ports_axi_req_t [NumSlvPorts-1:0]...

> Should we change that to "If a `parameter` only applies to one port, its name MUST start with the prefix of the port (converted to the casing dictated above...

Any other change requests or objections? If not, I would add this to our [Contribution Guidelines](https://github.com/pulp-platform/axi/blob/master/CONTRIBUTING.md) and start accepting PRs that implement these changes.

> > * A request type MUST end with `X_req_t`. > > * A response type MUST end with `X_rsp_t`. > > Would it make sense to use `X_resp_t` for...

@WRoenninger: What do you think?

> However this should probably be done after #157 as there is the whole config struct replacement going on. Okay, I agree. > I am wondering if it would be...

> Thanks for the help! Upon further debugging, we found that the additional cycles were not in fact from the crossbar in our case. There were two-stage synchronization modules before...

Is this issue a question, a bug report, or an enhancement proposal? If question: The [`axi_demux` documentation](https://github.com/pulp-platform/axi/blob/master/doc/axi_demux.md#ordering-and-stalls) states > When the demultiplexer receives two transactions with the same ID and...

I agree that there can be situations where the performance of the demux can be improved by letting it issue requests with the same ID to multiple master ports. Due...