sync_wedge: Remove deprecated clock gate - #359
Conversation
|
@fischeti can you quickly think this through as well? I think it is correct since the gated clock only goes to the register and that one already has an enable. |
|
I am a bit confused about the use of the clock gating cell here. Shouldn't the behaviour be that when |
|
I am not sure but my suspicion is that the previous module was a bit broken. The one in the CLINT makes more sense to me, which does not have a clock gating cell and also no enable. Because I am not sure the |
|
We can change the functionality for v2 and I tend to agree that the current implementation is very odd. |
|
Yes, I agree. I would drop the clock gating and enable signal alltogether, now that we have the opportunity to change the behaviour. The clear signal might be a bit tricky, because we cannot clear the |
|
Re clear signal, we already made the decision to exclude it from clock domain crossings and similar things so we can easily also remove it here. |
Continuously track the synchronized input so edge outputs are single-cycle pulses. Keep the deprecated enable port for source compatibility while delegating behavior to the active cell.
20d6f24 to
cfed869
Compare
Addresses #353
The clock gate is not functional since we have a
FFLARNCregister and it is always gated by the enable there.