From: "Christian König" <deathsimple@vodafone.de>
To: Parag Warudkar <parag.lkml@gmail.com>
Cc: "Michel Dänzer" <michel@daenzer.net>,
LKML <linux-kernel@vger.kernel.org>,
dri-devel@lists.freedesktop.org
Subject: Re: [PATCH] radeon: Allow disabling UVD
Date: Wed, 08 May 2013 11:32:04 +0200 [thread overview]
Message-ID: <518A1B94.6090001@vodafone.de> (raw)
In-Reply-To: <CAOULuObffavZs9+p-C_C5Y6y=6aJhnYVf_d0nXWXb9Zt2A7rBw@mail.gmail.com>
Am 07.05.2013 23:13, schrieb Parag Warudkar:
> On Tue, May 7, 2013 at 4:44 AM, Christian König <deathsimple@vodafone.de> wrote:
>
>> The patch shouldn't be necessary because just removing the firmware should
>> have pretty much the same effect.
> Soon distros will ship the UVD firmware by default and then users will
> need to manually remove it and then do the same with every update.
> Besides, I just discovered that when UVD is enabled suspend resume
> breaks - tried 3 times with SUMO_uvd loaded - machine suspends but
> resumes instantly.
> Without SUMO_uvd.bin - suspends fine and only wakes up when I want it to.
Hui? Wait a second, the firmware doesn't work but still causes an
instant resume on suspend? Very strange.
>> The only case where we indeed seems to have a problem are Macs with
>> integrated cards, and we can always just blacklist those if the problem
>> doesn't seems to be solvable.
> I happen to have the problematic card in my iMac - I'd be glad to
> provide any info or try any patches. Just let me know.
> For now I will remove the firmware - I reboot /suspend-resume often
> and it is a bit annoying to have to go through those mdelays only to
> fail.
Yeah, perfectly understandable.
My best guess is that it has something todo with a different clock
routing on Macs, but without access to the hardware (or precise
documentation from Apple what the heck they did different) I don't
really see a chance to solve that problem.
If you want to hack a bit on it you could try commenting out the calls
to "radeon_set_uvd_clocks" in radeon_uvd.c. That should give you the
default clocks of 100Mhz, not enough for usable decoding, but on SUMO
based UVD blocks a very failsafe default.
Whatever it is, please send me an output of lspci, so I can blacklist
the offending chip.
Christian.
> Thanks,
> Parag
>
next prev parent reply other threads:[~2013-05-08 9:32 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-06 23:11 [PATCH] radeon: Allow disabling UVD Parag Warudkar
2013-05-07 7:02 ` Michel Dänzer
2013-05-07 8:44 ` Christian König
2013-05-07 21:13 ` Parag Warudkar
2013-05-08 9:32 ` Christian König [this message]
2013-05-08 21:39 ` Parag Warudkar
2013-05-11 3:07 ` Parag Warudkar
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=518A1B94.6090001@vodafone.de \
--to=deathsimple@vodafone.de \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=michel@daenzer.net \
--cc=parag.lkml@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox