From: "Hans J. Koch" <hjk@hansjkoch.de>
To: Damian Hobson-Garcia <dhobsong@igel.co.jp>
Cc: horms@verge.net.au, magnus.damm@gmail.com, hjk@hansjkoch.de,
linux-sh@vger.kernel.org, hdk@igel.co.jp,
linux-kernel@vger.kernel.org,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Subject: Re: [RFC PATCH 0/2] Add UIO device supporting dynamic memory allocation
Date: Wed, 12 Sep 2012 22:11:16 +0000 [thread overview]
Message-ID: <20120912221116.GB5097@local> (raw)
In-Reply-To: <1347427785-9767-1-git-send-email-dhobsong@igel.co.jp>
On Wed, Sep 12, 2012 at 02:29:43PM +0900, Damian Hobson-Garcia wrote:
> Reposting: I realized that this series should have gone out to a broader list.
You forgot GregKH, I added him.
> My apologies to those who those who will recieve a duplicate post.
>
> Hello all,
>
> I've been using this UIO driver for allocation/deallocation
> of memory regions through an IOMMU via the dma-mapping API, but
> it seems that it would be more generally useful for userspace drivers
> to access CMA memory regions. I don't know if it's useful to try to add
> this functionality into the core uio driver or not, so for now I've kept
> all dynamic memory handling in the specific device driver.
>
> The number and size of the dynamically allocatable regions is defined
> statically in the device platform data, and the actually memory is
> allocated and deallocated when the device is opened/closed.
>
> Details of the dynamically allocated regions are available from sysfs in
> exactly the same was as for static regions. The total number of
> dynamic and static regions combined cannot exceed MAX_UIO_MAPS.
>
> Any comments, especially with regard to exposing the dma-mapping API to
> userspace in this way, would be greatly appreciated.
>
> Damian Hobson-Garcia (2):
> Add new uio device for dynamic memory allocation
> ARM: shmobile: sh7372: Change VPU UIO to uio_dmem_genirq
>
> arch/arm/mach-shmobile/setup-sh7372.c | 19 +-
> drivers/uio/Kconfig | 16 ++
> drivers/uio/Makefile | 1 +
> drivers/uio/uio_dmem_genirq.c | 356 +++++++++++++++++++++++++
> include/linux/platform_data/uio_dmem_genirq.h | 26 ++
> 5 files changed, 413 insertions(+), 5 deletions(-)
> create mode 100644 drivers/uio/uio_dmem_genirq.c
> create mode 100644 include/linux/platform_data/uio_dmem_genirq.h
Please add a third patch with a few words for Documentation/DocBook/uio-howto.tmpl
since this driver could be useful for other people, too.
Otherwise, looks good to me.
Thanks,
Hans
prev parent reply other threads:[~2012-09-12 22:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-10 10:30 [RFC PATCH 0/2] Add UIO device supporting dynamic memory allocation Damian Hobson-Garcia
2012-09-12 5:29 ` Damian Hobson-Garcia
2012-09-12 5:29 ` [RFC PATCH 1/2] Add new uio device for " Damian Hobson-Garcia
2012-09-12 5:29 ` [RFC PATCH 2/2] ARM: shmobile: sh7372: Change VPU UIO to uio_dmem_genirq Damian Hobson-Garcia
2012-09-12 22:11 ` Hans J. Koch [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=20120912221116.GB5097@local \
--to=hjk@hansjkoch.de \
--cc=dhobsong@igel.co.jp \
--cc=gregkh@linuxfoundation.org \
--cc=hdk@igel.co.jp \
--cc=horms@verge.net.au \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sh@vger.kernel.org \
--cc=magnus.damm@gmail.com \
/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).