From: mzoran@crowfest.net (Michael Zoran)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] arm64: dma-mapping: Fix dma_mapping_error() when bypassing SWIOTLB
Date: Wed, 25 Jan 2017 04:37:06 -0800 [thread overview]
Message-ID: <1485347826.2306.3.camel@crowfest.net> (raw)
In-Reply-To: <9e74b2f91b0b4b649a898db47225e5ea3b6a0417.1485345401.git.robin.murphy@arm.com>
On Wed, 2017-01-25 at 12:03 +0000, Robin Murphy wrote:
> hen bypassing SWIOTLB on small-memory systems, we need to avoid
> calling
> into swiotlb_dma_mapping_error() in exactly the same way as we avoid
> swiotlb_dma_supported(), because the former also relies on SWIOTLB
> state
> being initialised.
>
I didn't submit the initial ARM64 port of the RPI 3, so I don't know
much about this. But from a third personal point of view, this seems
to side step the main issue here.
>From an ARM64 subsystem point of view, what exactly is the
correct/recommended method for ensuring the mm subsystem is initialized
correctly?
WARNING: multiple messages have this Message-ID (diff)
From: Michael Zoran <mzoran@crowfest.net>
To: Robin Murphy <robin.murphy@arm.com>,
will.deacon@arm.com, catalin.marinas@arm.com
Cc: Jisheng Zhang <jszhang@marvell.com>,
arnd@arndb.de, konrad.wilk@oracle.com, aaro.koskinen@iki.fi,
stable@vger.kernel.org, linux-rpi-kernel@lists.infradead.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] arm64: dma-mapping: Fix dma_mapping_error() when bypassing SWIOTLB
Date: Wed, 25 Jan 2017 04:37:06 -0800 [thread overview]
Message-ID: <1485347826.2306.3.camel@crowfest.net> (raw)
In-Reply-To: <9e74b2f91b0b4b649a898db47225e5ea3b6a0417.1485345401.git.robin.murphy@arm.com>
On Wed, 2017-01-25 at 12:03 +0000, Robin Murphy wrote:
> hen bypassing SWIOTLB on small-memory systems, we need to avoid
> calling
> into swiotlb_dma_mapping_error() in exactly the same way as we avoid
> swiotlb_dma_supported(), because the former also relies on SWIOTLB
> state
> being initialised.
>
I didn't submit the initial ARM64 port of the RPI 3, so I don't know
much about this. But from a third personal point of view, this seems
to side step the main issue here.
>From an ARM64 subsystem point of view, what exactly is the
correct/recommended method for ensuring the mm subsystem is initialized
correctly?
next prev parent reply other threads:[~2017-01-25 12:37 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-24 22:52 USB/swiotlb failure on arm64/RPi3 Aaro Koskinen
2017-01-25 8:05 ` Stefan Wahren
2017-01-25 11:28 ` Arnd Bergmann
2017-01-25 12:03 ` [PATCH] arm64: dma-mapping: Fix dma_mapping_error() when bypassing SWIOTLB Robin Murphy
2017-01-25 12:03 ` Robin Murphy
2017-01-25 12:37 ` Michael Zoran [this message]
2017-01-25 12:37 ` Michael Zoran
2017-01-25 12:46 ` Robin Murphy
2017-01-25 12:46 ` Robin Murphy
2017-01-25 12:51 ` Arnd Bergmann
2017-01-25 12:51 ` Arnd Bergmann
2017-01-25 12:54 ` Robin Murphy
2017-01-25 12:54 ` Robin Murphy
2017-01-25 13:35 ` Michael Zoran
2017-01-25 13:35 ` Michael Zoran
2017-01-25 18:31 ` [PATCH v2] " Robin Murphy
2017-01-25 18:31 ` Robin Murphy
2017-01-25 19:14 ` Robin Murphy
2017-01-25 19:14 ` Robin Murphy
2017-01-25 19:31 ` Michael Zoran
2017-01-25 19:31 ` Michael Zoran
2017-01-25 21:49 ` Aaro Koskinen
2017-01-25 21:49 ` Aaro Koskinen
2017-01-26 12:52 ` Will Deacon
2017-01-26 12:52 ` Will Deacon
2017-01-26 13:04 ` Michael Zoran
2017-01-26 13:04 ` Michael Zoran
2017-01-26 15:20 ` Robin Murphy
2017-01-26 15:20 ` Robin Murphy
2017-01-26 20:35 ` Aaro Koskinen
2017-01-26 20:35 ` Aaro Koskinen
2017-01-27 9:53 ` Will Deacon
2017-01-27 9:53 ` Will Deacon
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=1485347826.2306.3.camel@crowfest.net \
--to=mzoran@crowfest.net \
--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 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.