While trying to continuously change the value of PADCONFIG MMR register, it is observed that the value is not updated properly once in while after running the test for few hours. 

From customers debug they figure out that there were two contending accesses to the PADCFG MMR registers, and in very rare timing scenarios, they would intersect with each other and lockout the LOCKx_KICKx registers.