Hers's the 5LP Registers document ilnk.
You'll find the description of DSI register controls. It's quite a big document!
You mind find it useful to use Creator to map out a couple of output pins. Then, look at the source code generated by Creator and use that knowledge to create the 32 to 32 mux.
BTW, which doc did you see DSI output to pin logic as a 4 to 4 mux? Just curious.
First, 4 to 4 mux is at the DSI output section (18.104.22.168 p158) of the PSoC5LP Architecture TRM.
I checked before the Registers TRM that you sent but It's not clear which DSI register does which connection/function.
If the structure of the DSI connection map is unknown, playing with the DSI registers is too risky because hardware may be damaged I think.
And reliability is another concern.
To commutate 32 input lines to the 32 outputs, one would require a matrix if 32x32=1024 transistor switches (P-terms in PSoC terminology). The PSoC5 has only 384 P-terms, which is, apparently, not enough. The 16x16 matrix uses 256 P-terms, which one can observe in the Design Resources meter (272=256+16, where 16 went for Control Registers).
P-Terms are UDB resources. PSoC creator routes UDB-to-pin by DSI without using UDB resources.
May not be routable each UDB output to each pin. But if we know the limits we can do something.
I have 32 digital output signals connected to 32 pins and I want to swap between each other when needed.
I think PSoC5LP capable of this but I can not do this without DSI routing info.
DSI routing is provided for limited configuration during design time and it is not possible to configure an application like the one mentioned for 32 different routings on the controller.
Thanks and regards