[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <2114579.IN6EpqPdMv@wuerfel>
Date: Thu, 09 Oct 2014 14:06:54 +0200
From: Arnd Bergmann <arnd@...db.de>
To: Ankit Jindal <ankit.jindal@...aro.org>
Cc: "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"Hans J. Koch" <hjk@...sjkoch.de>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
"patches@....com" <patches@....com>,
"linux-arm-kernel@...ts.infradead.org"
<linux-arm-kernel@...ts.infradead.org>,
Rob Herring <robh+dt@...nel.org>,
Tushar Jagad <tushar.jagad@...aro.org>,
Russell King - ARM Linux <linux@....linux.org.uk>,
"devicetree@...r.kernel.org" <devicetree@...r.kernel.org>
Subject: Re: [PATCH v2 0/6] UIO driver for APM X-Gene QMTM
On Thursday 09 October 2014 14:14:33 Ankit Jindal wrote:
> On 30 September 2014 09:56, Ankit Jindal <ankit.jindal@...aro.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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists