From: arnd@arndb.de (Arnd Bergmann)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 0/6] UIO driver for APM X-Gene QMTM
Date: Thu, 09 Oct 2014 14:06:54 +0200 [thread overview]
Message-ID: <2114579.IN6EpqPdMv@wuerfel> (raw)
In-Reply-To: <CAPTm99V-xyXa7WQG2jzDz19gotJ0aQRPk_rb5ukvUpdFyFabfw@mail.gmail.com>
On Thursday 09 October 2014 14:14:33 Ankit Jindal wrote:
> On 30 September 2014 09:56, Ankit Jindal <ankit.jindal@linaro.org> wrote:
> > This patchset enables user space access to APM X-Gene QMTM
> > using UIO framework.
> >
> > The patchset also introduces new type UIO_MEM_PHYS_CACHE
> > for mem regions because APM X-Gene QMTM device supports
> > cache coherency with CPU caches.
>
I haven't been able to review the patch in detail yet, but I have
a very high-level question: how do you decide which driver to use?
I understand that the normal use case is for the QMTM to be used by
the kernel directly rather than being exported to user space, and
that the network driver will just use it if it is there.
Arnd
next prev parent reply other threads:[~2014-10-09 12:06 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-30 4:26 [PATCH v2 0/6] UIO driver for APM X-Gene QMTM Ankit Jindal
2014-09-30 4:26 ` [PATCH v2 1/6] uio: code style cleanup Ankit Jindal
2014-09-30 4:26 ` [PATCH v2 2/6] uio: Add new UIO_MEM_PHYS_CACHE type for mem regions Ankit Jindal
2014-09-30 4:26 ` [PATCH v2 3/6] Documentation: Update documentation for UIO_MEM_PHYS_CACHE Ankit Jindal
2014-09-30 4:26 ` [PATCH v2 4/6] drivers: uio: Add X-Gene QMTM UIO driver Ankit Jindal
2014-09-30 6:05 ` Varka Bhadram
2014-10-21 5:52 ` Ankit Jindal
2014-09-30 4:26 ` [PATCH v2 5/6] Documentation: dt-bindings: Add binding info for " Ankit Jindal
2014-09-30 4:26 ` [PATCH v2 6/6] MAINTAINERS: Add entry for APM " Ankit Jindal
2014-10-09 8:44 ` [PATCH v2 0/6] UIO driver for APM X-Gene QMTM Ankit Jindal
2014-10-09 12:06 ` Arnd Bergmann [this message]
2014-10-09 12:17 ` Ankit Jindal
2014-10-09 12:22 ` Richard Weinberger
2014-10-09 12:30 ` Ankit Jindal
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=2114579.IN6EpqPdMv@wuerfel \
--to=arnd@arndb.de \
--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