Discovery assumes that the input is coming from outside the clock domain and infers that the RateChange is an input. This is actually ambiguous but can be resolved by either defining the rates of the different I/O lines or by looking at other rate change nodes.
A workaround is to insert a dummy node in the clock domain that the input goes through before reaching the RateChange node.
Discovery assumes that the input is coming from outside the clock domain and infers that the RateChange is an input. This is actually ambiguous but can be resolved by either defining the rates of the different I/O lines or by looking at other rate change nodes.
A workaround is to insert a dummy node in the clock domain that the input goes through before reaching the RateChange node.