From: Christoph Hellwig <hch@lst.de>
To: Robin Murphy <robin.murphy@arm.com>
Cc: "Roger Quadros" <rogerq@ti.com>, "Christoph Hellwig" <hch@lst.de>,
"Péter Ujfalusi" <peter.ujfalusi@ti.com>,
"Murali Karicheri" <m-karicheri2@ti.com>,
"Nori, Sekhar" <nsekhar@ti.com>, "Anna, Suman" <s-anna@ti.com>,
stefan.wahren@i2se.com, afaerber@suse.de, hverkuil@xs4all.nl,
"Rob Herring" <robh+dt@kernel.org>,
devicetree@vger.kernel.org,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"Nishanth Menon" <nm@ti.com>,
"hdegoede@redhat.com" <hdegoede@redhat.com>
Subject: Re: dma_mask limited to 32-bits with OF platform device
Date: Wed, 12 Feb 2020 18:57:56 +0100 [thread overview]
Message-ID: <20200212175756.GA6034@lst.de> (raw)
In-Reply-To: <9bd83815-6f54-2efb-9398-42064f73ab1c@arm.com>
On Wed, Feb 12, 2020 at 02:04:31PM +0000, Robin Murphy wrote:
>> For now, let's say that we limit dma-ranges to 4GB size. with "dma-ranges
>> = <0x00000000 0x00000000 0x1 0x00000000>;"
>> Then, dma_bus_limit is set correctly to 0xffffffff, SATA driver sets masks
>> to 64-bit as IP supports that.
>>
>> [ 13.306847] ahci 4a140000.sata: dma_mask 0xffffffffffffffff,
>> coherent_mask 0xffffffffffffffff, dma_bus_limit 0xffffffff
>>
>> However, the SATA controller still tries to do DMA above 32-bits.
>> dma_alloc() doesn't seem to be taking dma_bus_limit into account?
>
> Yay ARM LPAE... Peter and Christoph have already been playing whack-a-mole
> with other bugs under that config - is this with or without SWIOTLB? (and
> whichever way, does the other work any better?)
Hmm. ARM LPAE still uses the arm legacy dma alloc coherent, and that
might not be taking the dma_bus_limit into account. Let me check..
next prev parent reply other threads:[~2020-02-12 17:58 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-12 10:49 dma_mask limited to 32-bits with OF platform device Roger Quadros
2020-02-12 11:37 ` Robin Murphy
2020-02-12 12:33 ` Roger Quadros
2020-02-12 14:04 ` Robin Murphy
2020-02-12 17:57 ` Christoph Hellwig [this message]
2020-02-17 13:21 ` Christoph Hellwig
2020-02-17 14:54 ` Peter Ujfalusi
2020-02-18 7:26 ` Peter Ujfalusi
2020-02-18 8:28 ` Roger Quadros
2020-02-18 17:22 ` Rob Herring
2020-02-19 14:29 ` Roger Quadros
2020-02-19 15:25 ` Robin Murphy
2020-02-19 15:40 ` Roger Quadros
2020-02-26 11:33 ` Roger Quadros
2020-03-03 8:27 ` Roger Quadros
2020-03-03 14:06 ` Robin Murphy
2020-03-03 19:26 ` Rob Herring
2020-03-04 8:28 ` Roger Quadros
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=20200212175756.GA6034@lst.de \
--to=hch@lst.de \
--cc=afaerber@suse.de \
--cc=devicetree@vger.kernel.org \
--cc=hdegoede@redhat.com \
--cc=hverkuil@xs4all.nl \
--cc=linux-kernel@vger.kernel.org \
--cc=m-karicheri2@ti.com \
--cc=nm@ti.com \
--cc=nsekhar@ti.com \
--cc=peter.ujfalusi@ti.com \
--cc=robh+dt@kernel.org \
--cc=robin.murphy@arm.com \
--cc=rogerq@ti.com \
--cc=s-anna@ti.com \
--cc=stefan.wahren@i2se.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.