On Wed, Aug 24, 2016 at 9:43 AM, Tony Lindgren <tony@xxxxxxxxxxx> wrote: > * Suman Anna <s-anna@xxxxxx> [160823 09:42]: >> On 08/19/2016 06:39 PM, Tony Lindgren wrote: >> > * Adam Ford <aford173@xxxxxxxxx> [160818 12:20]: >> >> >> >> Does anyone have any suggestions on the best way to approach? >> > >> > In the long run we should have drivers/drm just manage these >> > devices using PM runtime and then just load firmware for the >> > sgx if available. Not sure what all needs to change for that >> > to happen though.. >> >> Unfortunately, the omap_hwmod code alone can't deal with PRCM reset >> lines, so you would still require the drivers to have to call some API >> for managing the resets, or if it is one-time boot-time setup thing, can >> do what was done for DRA7 PCIe (see commit 1c96bee4df19). > It appears as if the SGX driver is trying to figure out how to deassert reset. From what I can tell by the TRM, I just need to write a 1 to the bit which should do that. What isn't clear to me how to do that with the mechanism we have. > Yeah that makes sense to me. Then when we have a reset driver in > place we can switch to using that. I would love to help with getting a reset driver, but I am having a hard time following all the abstraction. If there are tasks I can help or code people want to test, I'd love to help. > > Regards, > > Tony -- 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
