From: anup.patel@broadcom.com (Anup Patel)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 3/8] uio: Add new UIO_MEM_DEVICE type for mem regions
Date: Fri, 15 Jul 2016 14:33:58 +0530 [thread overview]
Message-ID: <1468573443-4670-4-git-send-email-anup.patel@broadcom.com> (raw)
In-Reply-To: <1468573443-4670-1-git-send-email-anup.patel@broadcom.com>
On ARM64, the MMU supports special memory attributes for device
memory/registers. Due to this we have pgprot_device() provided
by asm/pgtable.h of arch/arm64.
On architectures that do not have special MMU attribute for device
memory/registers, the asm-generic/pgtable.h maps pgprot_device()
to pgprot_noncached().
This patch introduces a new UIO mem region type UIO_MEM_DEVICE to
represent device registers/memory. The UIO device drivers should
prefer this new UIO mem region type for memory mapped device registers.
Signed-off-by: Anup Patel <anup.patel@broadcom.com>
---
drivers/uio/uio.c | 4 ++++
include/linux/uio_driver.h | 1 +
2 files changed, 5 insertions(+)
diff --git a/drivers/uio/uio.c b/drivers/uio/uio.c
index 0e53076..a00990c 100644
--- a/drivers/uio/uio.c
+++ b/drivers/uio/uio.c
@@ -663,6 +663,9 @@ static int uio_mmap_physical(struct vm_area_struct *vma, int memtype)
case UIO_MEM_PHYS_CACHE:
/* Do nothing. */
break;
+ case UIO_MEM_DEVICE:
+ vma->vm_page_prot = pgprot_device(vma->vm_page_prot);
+ break;
default:
return -EINVAL;
}
@@ -714,6 +717,7 @@ static int uio_mmap(struct file *filep, struct vm_area_struct *vma)
switch (idev->info->mem[mi].memtype) {
case UIO_MEM_PHYS:
case UIO_MEM_PHYS_CACHE:
+ case UIO_MEM_DEVICE:
return uio_mmap_physical(vma, idev->info->mem[mi].memtype);
case UIO_MEM_LOGICAL:
case UIO_MEM_VIRTUAL:
diff --git a/include/linux/uio_driver.h b/include/linux/uio_driver.h
index 31359aee..7349f95 100644
--- a/include/linux/uio_driver.h
+++ b/include/linux/uio_driver.h
@@ -129,6 +129,7 @@ extern void uio_event_notify(struct uio_info *info);
#define UIO_MEM_LOGICAL 2
#define UIO_MEM_VIRTUAL 3
#define UIO_MEM_PHYS_CACHE 4
+#define UIO_MEM_DEVICE 5
/* defines for uio_port->porttype */
#define UIO_PORT_NONE 0
--
1.9.1
next prev parent reply other threads:[~2016-07-15 9:03 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-15 9:03 [PATCH 0/8] Cache-coherent DMA access using UIO Anup Patel
2016-07-15 9:03 ` [PATCH 1/8] uio: code style cleanup Anup Patel
2016-07-15 9:03 ` [PATCH 2/8] uio: Add new UIO_MEM_PHYS_CACHE type for mem regions Anup Patel
2016-07-15 9:03 ` Anup Patel [this message]
2016-07-15 9:03 ` [PATCH 4/8] Documentation: Update documentation for UIO_MEM_PHYS_CACHE and UIO_MEM_DEVICE Anup Patel
2016-07-15 9:04 ` [PATCH 5/8] uio: fix dmem_region_start computation Anup Patel
2016-07-15 11:32 ` Greg Kroah-Hartman
2016-07-15 12:02 ` Jan Viktorin
2016-07-15 9:04 ` [PATCH 6/8] uio: UIO_IRQ_NONE is a valid option for uioinfo->irq Anup Patel
2016-07-15 9:04 ` [PATCH 7/8] uio: bind uio_dmem_genirq via OF Anup Patel
2016-07-15 9:45 ` Russell King - ARM Linux
2016-07-15 10:47 ` Anup Patel
2016-07-15 13:28 ` Mark Rutland
2016-07-15 16:27 ` Anup Patel
2016-07-15 16:52 ` Mark Rutland
2016-07-18 3:17 ` Anup Patel
2016-07-15 9:04 ` [PATCH 8/8] uio: Use new memtypes in uio_dmem_genirq Anup Patel
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=1468573443-4670-4-git-send-email-anup.patel@broadcom.com \
--to=anup.patel@broadcom.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;
as well as URLs for NNTP newsgroup(s).