From: henry.gomersall@smartacoustics.co.uk (Henry Gomersall)
To: kernelnewbies@lists.kernelnewbies.org
Subject: Customizing UIO mmap'ing
Date: Fri, 18 Dec 2015 12:05:58 +0000 [thread overview]
Message-ID: <5673F6A6.7090000@smartacoustics.co.uk> (raw)
In-Reply-To: <CAK7rcp9ewT=QzKu6pVkDJ5ydpLn0B0n9wkqBSuW5NvynNaRQfg@mail.gmail.com>
On 17/12/15 21:35, Kenneth Adam Miller wrote:
> Generally uio_dmem_genirq.c builds on top of uio.c, which provides a
> common module basis for isolating code common to the other specific
> modules. But for a specific purpose, uio_dmem_genirq.c has be either
> customized or extended in order that specific memory regions can be
> set as accessible. Most easily, this is done in a first come first
> serve approach by filling out the details (which exactly?) left
> missing in uio_dmem_genirq.c, and to start, that would be
> in uio_of_genirq_match
> <https://proxy-us.hide.me/go.php?u=zWvu%2Fc4k0RUgdQesK%2F26T4EuwcXktyOuOa%2F3x1F0nLo5r0d9WlQEzfN928BYniutwGWnnJXkaBWcsA6D&b=29>.
>
> Am I correct?
It's not always necessary to modify uio_dmem_genirq.
Certainly in cases where the hardware capability can be specified by a
device tree (e.g. ARM systems), it is possible to specify an address
space and an IRQ that can be immediately used from userspace with the
uio_dmem_genirq driver with no modifications.
Henry
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.kernelnewbies.org/pipermail/kernelnewbies/attachments/20151218/43ffd32f/attachment.html
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: OpenPGP digital signature
Url : http://lists.kernelnewbies.org/pipermail/kernelnewbies/attachments/20151218/43ffd32f/attachment.bin
next prev parent reply other threads:[~2015-12-18 12:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-17 21:35 Customizing UIO mmap'ing Kenneth Adam Miller
2015-12-18 12:05 ` Henry Gomersall [this message]
2015-12-18 14:15 ` Kenneth Adam Miller
2015-12-18 14:20 ` Henry Gomersall
2015-12-18 14:51 ` Kenneth Adam Miller
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=5673F6A6.7090000@smartacoustics.co.uk \
--to=henry.gomersall@smartacoustics.co.uk \
--cc=kernelnewbies@lists.kernelnewbies.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.