Coder Social home page Coder Social logo

Clock and reset domains about filament HOT 4 OPEN

rachitnigam avatar rachitnigam commented on July 17, 2024
Clock and reset domains

from filament.

Comments (4)

rachitnigam avatar rachitnigam commented on July 17, 2024

Clocks and parameters should probably go in the parameter list instead of the event list since, once a circuit is instantiated, it is only allowed to have one clock or reset signal (is that true?)

from filament.

sampsyo avatar sampsyo commented on July 17, 2024

Cool; this sounds like the essence of the matter:

Each event is explicitly tied to a particular clock domain and events from different domains are not allowed to reuse instances or interact with each other. However, if we can prove that the clock domains have some relationship to each other, then we can use timing information to implicitly synchronize them.

That is, if you invoke a single instance from one clock domain, by default you shouldn't be able to use it from any other clock domains, because we lose the ability to prove mutual exclusion. But there may be some other way (not a current Filament feature) to show that you have waited long enough and you can be sure no other invocations from other clock domains are using something anymore, which would make this possible again.

Clock domains that are multiples of each other are one such option, and another is some kind of dynamic clock synchronizer thingy.

Clocks and parameters should probably go in the parameter list instead of the event list since, once a circuit is instantiated, it is only allowed to have one clock or reset signal (is that true?)

Not sure about reset signals, but I think it makes sense for clock parameters to be at the type/event level (as in your example) rather than parameters? Otherwise, I don't quite see how you get to a point where a single hardware structure combines two different clock domains, which is where these interesting interactions happen.

from filament.

rachitnigam avatar rachitnigam commented on July 17, 2024

Oh interesting! I was thinking of synchronization of values between circuits running in different clock domains but you're talking about the very Filament-esque idea of safety of reuse among different clock domains. I think that might be cool to think about but not sure if anyone does it in practice.

from filament.

sampsyo avatar sampsyo commented on July 17, 2024

Good point! Yeah, the other thing is quite a bit more exotic…

from filament.

Related Issues (20)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.