[...] > > Thanks, I understand what you mean. > > I simply searched for the keyword "MMC_READ_MULTIPLE_BLOCK" in the > drivers/mmc/host folder, and found that in some SD/MMC host controller > driver codes such as alcor.c, cavium.c, ...etc, there are also > behaviors for monitoring the request in their driver. What's the > difference between theirs and ours? Those checks are there to allow the HWs to be supported properly. > > And if the code that monitors the requstes does not belong the driver, > where should I implement the code and how to add some functions only > for GL9763e in that place, in your opinion? Honestly, I am not sure what suits your use case best. So far we have used runtime PM with a default auto suspend timeout, in combination with dev PM Qos. In other words, run as fast as possible to complete the requests in the queue then go back to idle and enter a low power state. Clearly, that seems not to be sufficient for your use case, sorry. Kind regards Uffe
