derek/gem5
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

dev: define VectorIntSourcePin type

Browse Source 
Change-Id: Ic457593cefb4f82794d3fe4c8c91931c1bf76a63
Reviewed-on: https://gem5-review.googlesource.com/c/public/gem5/+/55363
Reviewed-by: Jason Lowe-Power <power.jg@gmail.com>
Maintainer: Jason Lowe-Power <power.jg@gmail.com>
Reviewed-by: Gabe Black <gabe.black@gmail.com>
Tested-by: kokoro <noreply+kokoro@google.com>
This commit is contained in:
Wing Li
2022-01-10 15:43:05 -08:00
parent cd9fc30d92
commit 301ddefa28
1 changed files with 11 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

11
src/dev/IntPin.py
View File

@@ -35,6 +35,17 @@ class IntSourcePin(VectorPort):
def __init__(self, desc):
super().__init__(INT_SOURCE_ROLE, desc, is_source=True)
# A vector of source pins which might represent a bank of physical pins. Unlike
# IntSourcePin, each source pin in VectorIntSourcePin can only connect to a
# single sink pin. VectorIntSourcePin has the same definition as IntSourcePin
# right now, but will likely be implemented differently in the future.
# VectorIntSourcePin is defined as its own separate type to differentiate it
# from IntSourcePin and make it clear to the user how it should be interpreted
# and used.
class VectorIntSourcePin(VectorPort):
def __init__(self, desc):
super().__init__(INT_SOURCE_ROLE, desc, is_source=True)
# Each "physical" pin can be driven by a single source pin since there are no
# provisions for resolving competing signals running to the same pin.
class IntSinkPin(Port):