From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Alex Deucher <alexdeucher@gmail.com>,
Bjorn Helgaas <bhelgaas@google.com>
Cc: linuxppc-dev@ozlabs.org, Dave Airlie <airlied@linux.ie>,
linux-pci@vger.kernel.org, Anton Blanchard <anton@au1.ibm.com>,
Yijing Wang <wangyijing@huawei.com>, Takashi Iwai <tiwai@suse.de>,
Brian King <brking@linux.vnet.ibm.com>
Subject: [PATCH 4/4] sounds/hda/radeon: Disable 64-bit DMA on radeon
Date: Wed, 01 Oct 2014 12:09:53 +1000 [thread overview]
Message-ID: <1412129393.4285.195.camel@pasglop> (raw)
The chipset has a limitation in the number of address bits it
can generate. The graphics portion uses a specific mask of
40 or 48 bits depending on the generation. For audio, it's a bit
less of an issue, so just mark them as no-64bit for now.
Without this, it crashes on POWER machines which can use high bits
in the DMA address to distinguish between DMA windows.
Signed-off-by: Benjamin Herrenschmidt <benh@kernel.crashing.org>
CC: <stable@vger.kernel.org>
---
sound/pci/hda/hda_intel.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/sound/pci/hda/hda_intel.c b/sound/pci/hda/hda_intel.c
index 3e6d22d..2b679d5 100644
--- a/sound/pci/hda/hda_intel.c
+++ b/sound/pci/hda/hda_intel.c
@@ -297,7 +297,7 @@ enum {
/* quirks for ATI/AMD HDMI */
#define AZX_DCAPS_PRESET_ATI_HDMI \
(AZX_DCAPS_NO_TCSEL | AZX_DCAPS_SYNC_WRITE | AZX_DCAPS_POSFIX_LPIB|\
- AZX_DCAPS_NO_MSI64)
+ AZX_DCAPS_NO_MSI64 | AZX_DCAPS_NO_64BIT)
/* quirks for Nvidia */
#define AZX_DCAPS_PRESET_NVIDIA \
next reply other threads:[~2014-10-01 2:33 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-01 2:09 Benjamin Herrenschmidt [this message]
2014-10-01 7:38 ` [PATCH 4/4] sounds/hda/radeon: Disable 64-bit DMA on radeon Takashi Iwai
2014-10-01 7:41 ` Benjamin Herrenschmidt
2014-10-01 7:48 ` Benjamin Herrenschmidt
2014-10-01 8:09 ` Takashi Iwai
2014-10-01 8:30 ` Takashi Iwai
2014-10-01 17:58 ` Alex Deucher
2014-10-01 22:08 ` Benjamin Herrenschmidt
2014-10-02 0:15 ` Benjamin Herrenschmidt
2014-10-02 1:19 ` Alex Deucher
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=1412129393.4285.195.camel@pasglop \
--to=benh@kernel.crashing.org \
--cc=airlied@linux.ie \
--cc=alexdeucher@gmail.com \
--cc=anton@au1.ibm.com \
--cc=bhelgaas@google.com \
--cc=brking@linux.vnet.ibm.com \
--cc=linux-pci@vger.kernel.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=tiwai@suse.de \
--cc=wangyijing@huawei.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;
as well as URLs for NNTP newsgroup(s).