From: Jesse Barnes <jbarnes@virtuousgeek.org>
To: Alex Deucher <alexdeucher@gmail.com>
Cc: Clemens Ladisch <clemens@ladisch.de>,
linux-pci@vger.kernel.org, dri-devel@lists.sourceforge.net,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] PCI quirks: RS780/RS880: work around missing MSI initialization
Date: Mon, 22 Mar 2010 09:32:05 -0700 [thread overview]
Message-ID: <20100322093205.5edc3f6a@jbarnes-piketon> (raw)
In-Reply-To: <a728f9f91003220928t4655180djabe16e36c3389a05@mail.gmail.com>
On Mon, 22 Mar 2010 12:28:00 -0400
Alex Deucher <alexdeucher@gmail.com> wrote:
> On Mon, Mar 22, 2010 at 4:52 AM, Clemens Ladisch <clemens@ladisch.de> wrote:
> > AMD says in section 2.5.4 (GFX MSI Enable) of #43291 (AMD 780G Family
> > Register Programming Requirements):
> >
> > The SBIOS must enable internal graphics MSI capability in GCCFG by
> > setting the following: NBCFG.NB_CNTL.STRAP_MSI_ENABLE='1'
> >
> > Quite a few BIOS writers misinterpret this sentence and think that
> > enabling MSI is an optional feature. However, clearing that bit just
> > prevents delivery of MSI messages but does not remove the MSI PCI
> > capabilities registers, and so leaves these devices unusable for any
> > driver that attempts to use MSI.
> >
> > Setting that bit is not possible after the BIOS has locked down the
> > configuration registers, so we have to manually disable MSI for the
> > affected devices.
> >
> > This fixes the codec communication errors in the HDA driver when
> > accessing the HDMI audio device, and allows us to get rid of the
> > overcautious quirk in radeon_irq_kms.c.
>
> Looks good. This works properly on my rs780.
>
> Tested-by: Alex Deucher <alexdeucher@gamil.com>
Great, applied to my for-linus branch. I'll send it over to Linus this
week.
--
Jesse Barnes, Intel Open Source Technology Center
prev parent reply other threads:[~2010-03-22 16:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-22 8:52 Clemens Ladisch
2010-03-22 16:28 ` Alex Deucher
2010-03-22 16:32 ` Jesse Barnes [this message]
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=20100322093205.5edc3f6a@jbarnes-piketon \
--to=jbarnes@virtuousgeek.org \
--cc=alexdeucher@gmail.com \
--cc=clemens@ladisch.de \
--cc=dri-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
/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
all inboxes | Powered by JetHome®