Skip to content

Add an RFC for removing upwards propagation of clock domains #59

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

Merged
merged 1 commit into from
Mar 25, 2024

Conversation

wanda-phi
Copy link
Member

@wanda-phi wanda-phi commented Mar 17, 2024

@whitequark whitequark added meta:nominated Nominated for discussion on the next relevant meeting area:core RFC affecting APIs in amaranth-lang/amaranth labels Mar 17, 2024
@whitequark
Copy link
Member

More generally, since we have a pending full redesign of the system, we should probably not add functionality we might have to deprecate later, if it's avoidable.

@wanda-phi wanda-phi force-pushed the domain-prop branch 2 times, most recently from d3d2064 to a60620a Compare March 17, 2024 17:10
@whitequark whitequark changed the title RFC 59: Get rid of upwards propagation of clock domains. Add an RFC for removing upwards propagation of clock domains Mar 22, 2024
@whitequark whitequark removed the meta:nominated Nominated for discussion on the next relevant meeting label Mar 25, 2024
@whitequark
Copy link
Member

We have discussed this RFC on the 2024-03-25 weekly meeting. The disposition was to merge.

@whitequark whitequark merged commit 98600aa into amaranth-lang:main Mar 25, 2024
@wanda-phi wanda-phi deleted the domain-prop branch March 25, 2024 18:15
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area:core RFC affecting APIs in amaranth-lang/amaranth
Development

Successfully merging this pull request may close these issues.

2 participants