Skip to contentSkip to conversation

What did omap2_disp_get_dss morph into?

DISCUSSION [email protected] 2 participants 2 messages Mar 10, 2009 – Mar 11, 2009

lore
Share & tools
lore
#0 lore raw

I am trying to get the TI accelerated video driver to build against the current DSS2 kernel image, and I think I am this close || to getting it to go, but I am missing a pair of functions: omap2_disp_get_dss and omap2_disp_put_dss.

Obviously, they've changed into something else - what did they morph into?

#1 lore raw

Hi David,

You must be having "struct omap_display" pointer populated in your driver during probe, you just need to stick with display->enable and Display->disable function call. These functions in turn enables and disables clocks and save/restores the context.

If you provide some more details about your use case, then I would be able to understand better.

One more thing I just wanted to share, there some bugs we found during our release cycle in save and restore context path which I will be publishing soon. So please let me know if you are facing some issues, I can assist you with this.

Thanks,
Vaibhav Hiremath
Platform Support Products
Texas Instruments Inc
Ph: +91-80-25099927

Quoted 23 lines

-----Original Message-----
From: [email protected] [mailto:linux-omap- [email protected]] On Behalf Of [email protected]
Sent: Wednesday, March 11, 2009 2:02 AM
To: [email protected]
Subject: What did omap2_disp_get_dss morph into?

I am trying to get the TI accelerated video driver to build against the
current DSS2 kernel image, and I think I am this close || to getting it to
go, but I am missing a pair of functions: omap2_disp_get_dss and omap2_disp_put_dss.

Obviously, they've changed into something else - what did they morph into?

--
To unsubscribe from this list: send the line "unsubscribe linux- omap" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html