+ Ohad
On 6/7/2012 12:52 PM, Paul Walmsley wrote:
On Thu, 7 Jun 2012, Cousson, Benoit wrote:
In fact we should delay the reset to the very last moment and
potentially reset the IPs not under driver control later after a couple
of second for example. It will avoid reseting every IP that will be
handled properly by drivers.
We discussed this a couple of years ago on the list and aligned on late
and lazy resets, from my recollection.
Indeed, what I did not mention is that potentially the whole device init
should be done ondemand as well. Meaning the whole hwmod setup phase
should be done only when the driver will probe the device.
The main reason why it wasn't
implemented was because there were some drivers that were not yet PM
runtime-converted. This would have caused crashes, since the core code
would have no idea that the non-PM-runtime drivers had initialized their
devices, and so the core just went ahead and reset those anyway.
It might actually be safe now to switch to the late reset arrangement,
depending on whether the rest of the drivers have been PM
runtime-converted by now.
Of course, it would all be moot if the reset is moved away from the hwmod
code into the drivers.
I do think that moving that to driver code seems much better since all
these customs reset code (I2C, DSS, USB...) does anyway require access
to the device itself. The is driver responsibility to do that.
So ideally it should not be in OMAP architecture code.
Regards,
Benoit
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
