Wing Li has uploaded this change for review. ( https://gem5-review.googlesource.com/c/public/gem5/+/55363 )

Change subject: dev: define VectorIntSourcePin type
......................................................................

dev: define VectorIntSourcePin type

Change-Id: Ic457593cefb4f82794d3fe4c8c91931c1bf76a63
---
M src/dev/IntPin.py
1 file changed, 20 insertions(+), 0 deletions(-)



diff --git a/src/dev/IntPin.py b/src/dev/IntPin.py
index a6851cc..80618ce 100644
--- a/src/dev/IntPin.py
+++ b/src/dev/IntPin.py
@@ -35,6 +35,17 @@
     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):

--
To view, visit https://gem5-review.googlesource.com/c/public/gem5/+/55363
To unsubscribe, or for help writing mail filters, visit https://gem5-review.googlesource.com/settings

Gerrit-Project: public/gem5
Gerrit-Branch: develop
Gerrit-Change-Id: Ic457593cefb4f82794d3fe4c8c91931c1bf76a63
Gerrit-Change-Number: 55363
Gerrit-PatchSet: 1
Gerrit-Owner: Wing Li <wing...@google.com>
Gerrit-MessageType: newchange
_______________________________________________
gem5-dev mailing list -- gem5-dev@gem5.org
To unsubscribe send an email to gem5-dev-le...@gem5.org
%(web_page_url)slistinfo%(cgiext)s/%(_internal_name)s

Reply via email to