--- Quote Start ---
@kaz, thanks.
my problem is that: data-arrival reported by timequest is clock-path-delay+data-path-delay = 3.9 + 7 = 10.9
clock period itself is 7.5, so data path by itself is meeting setup. But the additional clock path delay is now causing the violation.
clock path delay shouldn't be there in the arrival report (or it should be reported the same in arrival and required) if its compensated.
how should i find out more bout this
--- Quote End ---
I see. I just tried some work on PLL and it turned out that the tool does not actually report physical delay but it reports delay after compensation so you should not get 3.9 ns (I got about 0.3 ns in compensation mode but 3.2 ns without compensation and was reported as such).
Now the question is back why do you get 3.9 ns? are you looking at right path? Do you actually pass timing after setting set_input_delay and how much slack do you get?