[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAM41TOuvhRVf=0MSe=xYg8sgeY6EQfMd9W4EGV0P9m5yyHUcMg@mail.gmail.com>
Date: Mon, 6 Jul 2015 16:50:08 +0300
From: Dmitry Kalinkin <dmitry.kalinkin@...il.com>
To: Martyn Welch <martyn.welch@...com>
Cc: Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
linux-kernel@...r.kernel.org, devel@...verdev.osuosl.org,
Manohar Vanga <manohar.vanga@...il.com>,
Igor Alekseev <igor.alekseev@...p.ru>
Subject: Re: [PATCHv3 08/16] staging: vme_user: provide DMA functionality
On Mon, Jul 6, 2015 at 4:22 PM, Martyn Welch <martyn.welch@...com> wrote:
>
> Sorry about the *really* late reply, loads of emails some how missed my
> periodic search of the mailing list.
>
> I'm happy with the addition of DMA, just not sure whether it's worth adding
> an extra device file just to handle DMA. Could the user space application
> not just use the control device?
That would require an additional ioctl field for DMA channel id in case we want
to support both DMA channels on tsi148.
It would make sense to save that device minor if Documentation/devices.txt
was good.
But it has only 4 slave and 4 master windows whereas we would want to
make some parameters for vme_user to configure this allocation numbers up
to 8 slaves and 8 masters.
--
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