5a9a743cfc
This patch classifies all ports in Python as either Master or Slave and enforces a binding of master to slave. Conceptually, a master (such as a CPU or DMA port) issues requests, and receives responses, and conversely, a slave (such as a memory or a PIO device) receives requests and sends back responses. Currently there is no differentiation between coherent and non-coherent masters and slaves. The classification as master/slave also involves splitting the dual role port of the bus into a master and slave port and updating all the system assembly scripts to use the appropriate port. Similarly, the interrupt devices have to have their int_port split into a master and slave port. The intdev and its children have minimal changes to facilitate the extra port. Note that this patch does not enforce any port typing in the C++ world, it merely ensures that the Python objects have a notion of the port roles and are connected in an appropriate manner. This check is carried when two ports are connected, e.g. bus.master = memory.port. The following patches will make use of the classifications and specialise the C++ ports into masters and slaves. |
||
---|---|---|
.. | ||
inorder-timing.py | ||
memtest-ruby.py | ||
memtest.py | ||
o3-timing-mp-ruby.py | ||
o3-timing-mp.py | ||
o3-timing-ruby.py | ||
o3-timing.py | ||
pc-o3-timing.py | ||
pc-simple-atomic.py | ||
pc-simple-timing.py | ||
realview-o3-dual.py | ||
realview-o3.py | ||
realview-simple-atomic-dual.py | ||
realview-simple-atomic.py | ||
realview-simple-timing-dual.py | ||
realview-simple-timing.py | ||
rubytest-ruby.py | ||
simple-atomic-mp-ruby.py | ||
simple-atomic-mp.py | ||
simple-atomic.py | ||
simple-timing-mp-ruby.py | ||
simple-timing-mp.py | ||
simple-timing-ruby.py | ||
simple-timing.py | ||
t1000-simple-atomic.py | ||
tsunami-inorder.py | ||
tsunami-o3-dual.py | ||
tsunami-o3.py | ||
tsunami-simple-atomic-dual.py | ||
tsunami-simple-atomic.py | ||
tsunami-simple-timing-dual.py | ||
tsunami-simple-timing.py | ||
twosys-tsunami-simple-atomic.py |