It would seem that if I let PSELx stay at its existing value at the end of a transaction, rather than unconditionally setting it to 0, it would reduce power consumption, since PSELx wouldn't have to change when the next transaction selects the same PSELx.This is certainly an advantage.
Nevertheless, why does the APB spec. require PSELx to be set to 0 at the end of a transaction?
I should add that you can use the APB protocol with combinatorial logic, using PSELx & ! PENABLE to open a latch to sample PADDR during the "setup" phase (so PADDR would be valid as the latch closes), and the PSELx & PENABLE to then enable data latching or driving during the "access" phase.
However virtually all designs nowadays use synchronous logic, so it would be the registering signals on PCLK rising edges that would be the standard solution.
Ah, that explains it, I see now.Thank you for your response !!