ID:35017 Partition port "<name>", driven by node "<name>", does not drive logic

CAUSE: The specified partition port has no fan-out. The implications are as follows:

If the specified partition port is an input port, no logic within the partition currently depends on it.
If the specified partition port is an output port, no logic outside the partition currently depends on it.

In either case, in order to preserve partition interface for subsequent incremental compilations, the Quartus Prime software cannot optimize away the logic leading to the specified port (for example, the specified node). Additionally, in order to preserve netlist legality, a virtual pin is connected in place of the partition port. This warning message reminds you of the potential area waste caused by the unused logic and the virtual pin. In general, the presence of this message indicates that the partitioning scheme in the current design has room for improvement. Having a high quality partitioning scheme is crucial to the successful use of incremental compilation. Altera recommends that you run the Incremental Compilation Advisor and/or consult the Quartus Prime Handbook chapter on incremental compilation.

ACTION: If you intend to connect the specified partition ports in a subsequent incremental compilation, no action is required. If you want to reclaim the wasted area, you may restructure the partitions such that the specified unused port is not at a partition boundary. You may also provide a wrapper module around an entity instance to hide its unused ports, and set the wrapper as a partition instead of the containing entity instance. You may use the Incremental Compilation Advisor to detect the presence of dangling partition ports, as well as other potential issues in the current design.