From: linux@armlinux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: Creating kernel mappings for memory initially marked with bootmem NOMAP?
Date: Wed, 8 Mar 2017 19:26:53 +0000 [thread overview]
Message-ID: <20170308192653.GB21222@n2100.armlinux.org.uk> (raw)
In-Reply-To: <c17b0a16-fde5-9254-f84a-418972201eae@gmail.com>
On Wed, Mar 08, 2017 at 11:03:43AM -0800, Florian Fainelli wrote:
> Now, we have some peripherals that want large chunks of physically and
> virtually contiguous memory that belong to these memblock NOMAP ranges.
> I have no problems using mmap() against this memory, because the kernel
> will do what is necessary for a process to map it for me. The struggle
> is for a kernel driver which specifies a range of physical memory and
> size, and expects a virtually contiguous mapping in return (not using
> DMA-API, because reasons).
Will vm_iomap_memory() do the job?
--
RMK's Patch system: http://www.armlinux.org.uk/developer/patches/
FTTC broadband for 0.8mile line: currently at 9.6Mbps down 400kbps up
according to speedtest.net.
next prev parent reply other threads:[~2017-03-08 19:26 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-08 19:03 Creating kernel mappings for memory initially marked with bootmem NOMAP? Florian Fainelli
2017-03-08 19:14 ` Ard Biesheuvel
2017-03-08 19:52 ` Florian Fainelli
2017-03-08 22:06 ` Ard Biesheuvel
2017-03-08 22:10 ` Florian Fainelli
2017-03-16 19:04 ` Florian Fainelli
2017-03-16 20:00 ` Russell King - ARM Linux
2017-03-08 19:26 ` Russell King - ARM Linux [this message]
2017-03-08 19:29 ` Russell King - ARM Linux
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=20170308192653.GB21222@n2100.armlinux.org.uk \
--to=linux@armlinux.org.uk \
--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