From: agraf@suse.de (Alexander Graf)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2] arm64: Allow for different DMA and CPU bus offsets
Date: Wed, 18 May 2016 16:34:12 +0200 [thread overview]
Message-ID: <573C7D64.5040206@suse.de> (raw)
In-Reply-To: <20160518142620.GA22354@localhost.localdomain>
On 05/18/2016 04:26 PM, Catalin Marinas wrote:
> On Wed, May 18, 2016 at 03:49:17PM +0200, Alexander Graf wrote:
>> On 05/18/2016 03:27 PM, Catalin Marinas wrote:
>>> On Wed, May 18, 2016 at 02:53:30PM +0200, Alexander Graf wrote:
>>>> On arm64, all SoCs we supported so far either have an IOMMU or have bus
>>>> addresses equal to CPU addresses.
>>>>
>>>> However, with the Raspberry Pi 3 coming up, this is no longer true. To
>>>> allow DMA to work with an AArch64 kernel on those devices, let's allow
>>>> devices to have DMA offsets again.
>>>>
>>>> Signed-off-by: Alexander Graf <agraf@suse.de>
>>> We were aware about this issue but we've been waiting for an actual use
>>> case. I'll queue this for 4.8 (given that RPi3 is not supported by the
>>> arm64 kernel, I don't see the rush to merge it earlier).
>> Sure, works for me. That way Eric can try to push the other few bits
>> necessary to run an arm64 kernel on the RPi3 towards 4.8 as well :).
> As long as the firmware is PSCI capable ;)
So spin tables won't work for you? IIRC we don't own EL3 on there.
Alex
next prev parent reply other threads:[~2016-05-18 14:34 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-18 12:53 [PATCH v2] arm64: Allow for different DMA and CPU bus offsets Alexander Graf
2016-05-18 13:05 ` Arnd Bergmann
2016-05-18 13:27 ` Catalin Marinas
2016-05-18 13:49 ` Alexander Graf
2016-05-18 14:26 ` Catalin Marinas
2016-05-18 14:34 ` Alexander Graf [this message]
2016-05-18 15:19 ` Catalin Marinas
2016-05-18 15:33 ` Alexander Graf
2016-05-18 16:08 ` Arnd Bergmann
2016-05-18 16:16 ` Alexander Graf
2016-05-18 17:18 ` Eric Anholt
2016-06-01 8:42 ` Catalin Marinas
2016-06-07 22:08 ` Eric Anholt
2016-05-18 18:59 ` Sinan Kaya
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=573C7D64.5040206@suse.de \
--to=agraf@suse.de \
--cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).