2009/12/28 Luca Tettamanti <kronos...@gmail.com>: > 2009/12/28 Alex Deucher <alexdeuc...@gmail.com>: >> On Mon, Dec 28, 2009 at 5:53 AM, Luca Tettamanti <kronos...@gmail.com> wrote: >>> On Sun, Dec 27, 2009 at 1:55 AM, Rafał Miłecki <zaj...@gmail.com> wrote: >>>> W dniu 26 grudnia 2009 20:08 użytkownik Alex Deucher >>>> <alexdeuc...@gmail.com> napisał: >>>>> It may be that the engine doesn't like to be reclocked while it's >>>>> running. Perhaps we should use the GUI idle interrupt rather than >>>>> vblanks to reclock the engine. >>>> >>>> Could you say something more about GUI idle interrupt, please? >>> >>> It's mentioned in the documentation of the IH (see r600.c); I guess >>> it's enabled by GUI_IDLE_INT_ENABLE. >>> >>>> What is this, do we already have code for that? >>> >>> Unless there are more subtleties all is needed it to enabled the >>> interrupt and catch it in r600_irq_process. >> >> That's pretty much it. Pre-r6xx asics have a GUI interrupt as well. >> I can look up the details for that if they are not already documented. > > I can't find a way to ack the interrupt; I see > RADEON_GUI_IDLE_INT_TEST_ACK but I think it's for pre-r6xx cards, > right?
You don't have to ACK it as the CP generates the interrupt in software; similar to the sw interrupts used for fences. Alex ------------------------------------------------------------------------------ This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev -- _______________________________________________ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
