Tco Constraints

Required is what you put in for the clock constraint. Required P2P is essentially the requirement between the registers. Essentially this is after clock skew. Actual is how long that was, and then the actual Fmax is how fast that path could run at according to the timing results. Right-click on a path, do a List Path, and analyze the detailed report, and most of this should come out. You won't fully understand timing analysis with relying heavily on that list path. The panels in the timing report are just summary level info on each path.

I believe a Tco can go through ripple clocks, i.e. where the incoming clock feeds a register, and that register's .Q pin feeds the .CLK port of the next register, and can ripple through multiple registers. It's not recommended, but it's doable. So if you have a Tco on the output pin, then you should see this full analysis. Again, analyze the List Path to see what is being analyzed and then determine if it's what you need, and if not, why?