There is a write when ntt is done.

[batthineniatlubis]

The following scenario occurs when the ntt is set for one of the modes for example ct and the operation goes on until the done signal is asserted, which ideally considering done a very strong signal, because after done, we should be able to start another computation. In the current design its not feasible because there is a write even when the done is asserted and this means a new computation cannot be triggered until this is finished. This would be an issue if the ntt block is pulled and used for any another project where it needs back to back computations.