-
Notifications
You must be signed in to change notification settings - Fork 56
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add top_layer/pg_pins_layers/stripe_pins flags to write_ilm for hierarchical flows #819
Conversation
Hm, can't we just set the stripe pins and top layer arguments based on the power straps pin_layer field? |
Is that general enough though for all use cases? For instance, If you have a power island in a block that instantiates its own bump, what would the flags to this command need to be? I figured there will frequently be cases where you'll need some specialized settings to achieve what you want. |
In the user guide: In a bottom-up flow (where the block was not created using the create_partition command), you normally create a simple LEF abstract that contains:
So, it seems like |
Ok, I'll change this then. |
Should we at least handle the case where manual power straps are used, in which case the |
No, I think if you're doing manual straps, you're already using hooks and being mindful of stripe pin layers. At most, add an additional comment for the |
Currently, this uses the auto-power-straps by_tracks pin_layers option to determine the top_layer and pg_pin_layers
4d8e681
to
9c120a0
Compare
Currently, this uses the auto-power-straps by_tracks pin_layers option to determine the top_layer and pg_pin_layers
Related PRs / Issues
Type of change:
Impact:
Contributor Checklist:
master
as the base branch?poetry.lock
file if you updated the requirements inpyproject.toml
?e2e/
if this feature depends on updated plugins?