Skip to content
Projects
Groups
Snippets
Help
Loading...
Help
Support
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in / Register
Toggle navigation
L
litex
Project overview
Project overview
Details
Activity
Releases
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Issues
0
Issues
0
List
Boards
Labels
Milestones
Merge Requests
1
Merge Requests
1
Analytics
Analytics
Repository
Value Stream
Wiki
Wiki
Snippets
Snippets
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Create a new issue
Commits
Issue Boards
Open sidebar
Jonathan Currier
litex
Commits
40cbe3a9
Commit
40cbe3a9
authored
Jun 02, 2019
by
Ilia Sergachev
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
fix interrupt_name
parent
b300c321
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
2 additions
and
2 deletions
+2
-2
litex/soc/integration/soc_core.py
litex/soc/integration/soc_core.py
+2
-2
No files found.
litex/soc/integration/soc_core.py
View file @
40cbe3a9
...
...
@@ -361,7 +361,7 @@ class SoCCore(Module):
# check that interrupt_id is in range
if
interrupt_id
is
not
None
and
interrupt_id
>=
32
:
raise
ValueError
(
"{} Interrupt ID out of range ({}, max=31)"
.
format
(
interrupt_name
name
,
interrupt_id
))
interrupt_name
,
interrupt_id
))
# interrupt_id not provided: allocate interrupt to the first available id
if
interrupt_id
is
None
:
...
...
@@ -369,7 +369,7 @@ class SoCCore(Module):
if
n
not
in
self
.
soc_interrupt_map
.
values
():
self
.
soc_interrupt_map
.
update
({
interrupt_name
:
n
})
return
raise
ValueError
(
"No more space to allocate {} interrupt"
.
format
(
name
))
raise
ValueError
(
"No more space to allocate {} interrupt"
.
format
(
interrupt_
name
))
# interrupt_id provided: check that interrupt_id is not already used and add interrupt
else
:
for
_name
,
_id
in
self
.
soc_interrupt_map
.
items
():
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment