This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

Accessing a module which's clock is not enabled

Hi, I was doing some power on/off test of the High-Speed USB OTG Controller, when I disable the controller's clock and try to read some of its registers I got the following error:

DisableDeviceClocks OMAP_DEVICE_HSOTGUSB.
CM_ICLKEN1_CORE = 0x02006042.
CM_ICLKEN1_CORE = 0x7FFFFEC1.

reading some register of the controller got the following exception:

Exception 'Data Abort' (4): Thread-Id=0580000e(pth=829aa120), Proc-Id=00400002(pprc=81e82308) 'NK.EXE', VM-active=05640016(pprc=829aa390) 'OTG_DEBUGGER.exe'
PC=d3842ca8(omap_musbotg.dll+0x00002ca8) RA=d3842c9c(omap_musbotg.dll+0x00002c9c) SP=d209fa08, BVA=00000000
Exception 'Raised Exception' (-1): Thread-Id=0580000e(pth=829aa120), Proc-Id=00400002(pprc=81e82308) 'NK.EXE', VM-active=05640016(pprc=829aa390) 'OTG_DEBUGGER.exe'
PC=c006ba5c(k.coredll.dll+0x0001ba5c) RA=80033520(kernel.dll+0x00006520) SP=d209f298, BVA=ffffffff

and I enable the controller's clock again:

EnableDeviceClocks OMAP_DEVICE_HSOTGUSB.
CM_ICLKEN1_CORE = 0x02006052.
CM_ICLKEN1_CORE = 0x7FFFFEC1.

but  accessing the controller's register still got the same exception,  can't we recover from that exception ??