From: nikita.yoush@cogentembedded.com (Nikita Yushchenko)
To: linux-arm-kernel@lists.infradead.org
Subject: arm64: mm: bug around swiotlb_dma_ops
Date: Fri, 23 Dec 2016 16:07:49 +0300 [thread overview]
Message-ID: <63639fa4-240b-0f7b-1adb-b79b2f33bef8@cogentembedded.com> (raw)
In-Reply-To: <549c88f2-4a17-1b92-4478-e58aa0dd104f@cogentembedded.com>
> If trying to avoid big changes and only fixing particular problem with
> particular device not working on arm64, I think best way is to
> alter__swiotlb_dma_supported() in arch/arm64/mm/dma-mapping.c to detect
> and decline (with -EIO) mask that is unsupported by device connection.
> This will cover both dma_mask and coherent_dma_mask.
>
> This has to be combined with some way to explicitly extract information
> about limitations. Checking device parent's dma masks won't work unless
> somebody bothers to populate them.
I'm trying to bring together a patch doing this, will post that when ready
prev parent reply other threads:[~2016-12-23 13:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-15 16:20 arm64: mm: bug around swiotlb_dma_ops Nikita Yushchenko
2016-12-15 19:07 ` Arnd Bergmann
2016-12-23 13:03 ` Nikita Yushchenko
2016-12-23 13:07 ` Nikita Yushchenko [this message]
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=63639fa4-240b-0f7b-1adb-b79b2f33bef8@cogentembedded.com \
--to=nikita.yoush@cogentembedded.com \
--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