Felipe Balbi <balbi@xxxxxx> writes: > Hi, > > On Sat, Feb 16, 2013 at 11:31:21AM +0530, Santosh Shilimkar wrote: >> >>The main goal is to avoid duplicating data both in hwmod and DT. >> >>That's pretty much solved as we can have the driver probe populate >> >>the common data for hwmod from DT as Santosh has already demonstrated. >> >> >> >>Then we also want the driver specific idle and reset code to be done >> >>in the drivers rather than in hwmod and glue it together with hwmod >> >>using runtime PM. The biggest issue there is how do we reset and idle >> >>some piece of hardware for PM purposes when there's no driver loaded. >> > >> >right, this will be a tough nut to crack. >> > >> >I guess the only way would be reset all IPs early in the boot process, >> >before even creating the platform-devices. Can we do that ? I mean, from >> >omap_device_build_from_dt() we have access to address space of all >> >devices, through ti,hwmods we can figure out which hwmods are linked to >> >that particular device, so whenever you build a device, you could just >> >call _reset(). >> > >> Thats what we do today and it works perfectly. As per Tony's suggestion, >> we need to move the non-probed devices reset and idle setup to late_init >> which is also doable. >> >> In that case when probed driver calls runtime_get(), we reset that >> device and setup the idle settings. And remainder of the devices >> are managed in late_init(). > > what's the point in moving it to late_initcall() ? It makes no > difference, if no driver binds to that device it will stay in reset > anyway. Maybe what we're missing is properly idling (not exactly) all > devices before driver probe kicks in. > >> >The only problem is that now omap_device_build_from_dt() is called after >> >we notify that a new device/driver pair has been registered with the >> >platform_bus, right ? So we would still need a way to call _reset() for >> >those which are on DTS but don't have a driver bound to them... >> > >> The only special requirement for reset remains(which today handled by >> hwmod function calls) is for devices which needs specific reset >> sequence. And this one can be handled through a runtime_reset() >> kind of hook. >> >> Does that sound reasonable ? > > Depends on Rafael. If he says no to the ->runtime_reset() I suggested > earlier, another aproach needs to be found. In any case, > ->runtime_reset() is only for devices which actually have a driver, so > it matters little. Has somone tried this to see if it works on devices with the custom reset hooks? It should be relatively easy to add a ->runtime_reset hook, and hook it up to omap_device_shutdown() at the PM domain level. If we have a patch, showing how we use it in some drivers and making the case for why it is needed in some drivers, it will be easier to take this to Rafael and make a case for it. > The difficult part is handling special reset requirements for devices > without drivers as there'd be no ->runtime_reset() to call. IMO, this should not be difficult, as omap_device_shutdown() -> omap_hwmod_shutdown() does the heavy lifting here. Also, We already track whether omap_devices have drivers bound, so adding support to reset/shutdown unbound drivers in late init will be straight forward. Kevin -- 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
