Skip to content
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

keep time with external guidance but match retrigger start point #12

Open
1 task
wraybowling opened this issue Sep 2, 2020 · 0 comments
Open
1 task
Labels
Milestone

Comments

@wraybowling
Copy link
Member

Created from #5 This might be resolved with #9 or even with #11.

The idea was that the clock input might be coming from one module and that the user might want the behavior of the retrigger to be one of two modes

  • time is always kept with the incoming clock
  • time is kept with the retrigger

but if the incoming clock is not perfectly in sync, then the clock cannot reliably tell us when to trigger high. The retrigger offset would need to be added to that timestamp.

  • research if anyone would even want this
@wraybowling wraybowling added this to the The Clock milestone Sep 2, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant