<html>
    <head>
      <base href="https://bugs.freedesktop.org/" />
    </head>
    <body>
      <p>
        <div>
            <b><a class="bz_bug_link 
          bz_status_NEW "
   title="NEW --- - r600: linux 3.11RC isn't booting with radeon.dpm=1 option in grub"
   href="https://bugs.freedesktop.org/show_bug.cgi?id=66963#c7">Comment # 7</a>
              on <a class="bz_bug_link 
          bz_status_NEW "
   title="NEW --- - r600: linux 3.11RC isn't booting with radeon.dpm=1 option in grub"
   href="https://bugs.freedesktop.org/show_bug.cgi?id=66963">bug 66963</a>
              from <span class="vcard"><a class="email" href="mailto:orbitgray@ukr.net" title="Sergey <orbitgray@ukr.net>"> <span class="fn">Sergey</span></a>
</span></b>
        <pre>Some findings:

The actual hand happens in
drivers/gpu/drm/radeon/rv6xx_dpm.c:
int rv6xx_dpm_enable(struct radeon_device *rdev)
on 'r600_start_dpm(rdev)' call.
Makes sense that configurations are harmless before actual dpm is enabled.

>From this function it looks like we disable sclk and mclk do pll configuration,
then enable clocks back. But even if I leave:
void r600_start_dpm(struct radeon_device *rdev)
{
        r600_enable_sclk_control(rdev, false);
        r600_enable_mclk_control(rdev, false);

        r600_enable_sclk_control(rdev, true);
        r600_enable_mclk_control(rdev, true);
}
System still fails with black screen.

There is also peace of code in r600_start_dpm() that is duplicated:
         r600_enable_spll_bypass(rdev, true);
         r600_wait_for_spll_change(rdev);
         r600_enable_spll_bypass(rdev, false);
         r600_wait_for_spll_change(rdev);

         r600_enable_spll_bypass(rdev, true);
         r600_wait_for_spll_change(rdev);
         r600_enable_spll_bypass(rdev, false);
         r600_wait_for_spll_change(rdev);
(probably this intentional, just checking)

Sorry if it doesn't make any sense, I'm new with radeon driver and don't know
how 'dpm' is supposed to work for this HW.</pre>
        </div>
      </p>
      <hr>
      <span>You are receiving this mail because:</span>
      
      <ul>
          <li>You are the assignee for the bug.</li>
      </ul>
    </body>
</html>