Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756315AbbGFNuM (ORCPT ); Mon, 6 Jul 2015 09:50:12 -0400 Received: from mail-wi0-f169.google.com ([209.85.212.169]:34432 "EHLO mail-wi0-f169.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755313AbbGFNuJ (ORCPT ); Mon, 6 Jul 2015 09:50:09 -0400 MIME-Version: 1.0 In-Reply-To: <559A8117.4060701@ge.com> References: <1432814833-5320-1-git-send-email-dmitry.kalinkin@gmail.com> <1432814833-5320-9-git-send-email-dmitry.kalinkin@gmail.com> <20150613002807.GA17459@kroah.com> <559A8117.4060701@ge.com> Date: Mon, 6 Jul 2015 16:50:08 +0300 Message-ID: Subject: Re: [PATCHv3 08/16] staging: vme_user: provide DMA functionality From: Dmitry Kalinkin To: Martyn Welch Cc: Greg Kroah-Hartman , linux-kernel@vger.kernel.org, devel@driverdev.osuosl.org, Manohar Vanga , Igor Alekseev Content-Type: text/plain; charset=UTF-8 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1002 Lines: 21 On Mon, Jul 6, 2015 at 4:22 PM, Martyn Welch 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@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/