From: "Maciej W. Rozycki" <macro@linux-mips.org>
To: Ralf Baechle <ralf@linux-mips.org>, Paul Burton <paul.burton@mips.com>
Cc: Christoph Hellwig <hch@lst.de>,
linux-mips@linux-mips.org, linux-kernel@vger.kernel.org
Subject: [PATCH 0/2] MIPS: SiByte: Handle PCI DMA with 64-bit memory addressing
Date: Wed, 7 Nov 2018 00:08:16 +0000 (GMT) [thread overview]
Message-ID: <alpine.LFD.2.21.1811050350070.20378@eddie.linux-mips.org> (raw)
Hi,
This mini patch series enables correct support for DMA in the presence of
memory outside the 32-bit address range with the Broadcom SiByte SOCs and
the relevant development boards.
There is a quirk in the BCM1250, BCM1125 and BCM1125H SOCs in that their
onchip 32-bit PCI host bridge does not support DAC, however the HT link
(where available) does support 40-bit addressing as per the HT spec.
Therefore the first patch sets the bus mask accordingly, and then the
second patch enables swiotlb. See individual change descriptions for
additional details; there's also a further discussion alongside.
This has been verified with a Broadcom SWARM board equipped with 3200MiB
of RAM (2176MiB of which the address decoder in the SOC maps above 4GiB),
a pair of DEFPA FDDI adapters and an XHCI USB adapter. There were also
some other PCI and PCIe devices present in the system, though not actively
used beyond being probed at boot, and none has shown any symptoms of
breakage.
Thanks to Christoph for making this change so easy with his recent work!
Please apply.
Maciej
next reply other threads:[~2018-11-07 0:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-07 0:08 Maciej W. Rozycki [this message]
2018-11-07 0:08 ` [PATCH 1/2] MIPS: SiByte: Set 32-bit bus mask for BCM1250 PCI Maciej W. Rozycki
2018-11-07 7:58 ` Christoph Hellwig
2018-11-07 11:08 ` Maciej W. Rozycki
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=alpine.LFD.2.21.1811050350070.20378@eddie.linux-mips.org \
--to=macro@linux-mips.org \
--cc=hch@lst.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@linux-mips.org \
--cc=paul.burton@mips.com \
--cc=ralf@linux-mips.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