Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752241AbaKDSJU (ORCPT ); Tue, 4 Nov 2014 13:09:20 -0500 Received: from smtp113.iad3a.emailsrvr.com ([173.203.187.113]:58501 "EHLO smtp113.iad3a.emailsrvr.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751848AbaKDSJT (ORCPT ); Tue, 4 Nov 2014 13:09:19 -0500 X-Sender-Id: abbotti@mev.co.uk From: Ian Abbott To: Cc: Greg Kroah-Hartman , Ian Abbott , H Hartley Sweeten , Subject: [PATCH 0/2] staging: comedi: per-file read/write subdevice choice Date: Tue, 4 Nov 2014 18:08:59 +0000 Message-Id: <1415124541-13648-1-git-send-email-abbotti@mev.co.uk> X-Mailer: git-send-email 2.1.1 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org This series of patches adds a couple of ioctl codes to the Comedi core to allow the current "read" and "write" subdevice to be changed after opening the comedi device. The current read and write subdevice information is stored in file private data allocated for the lifetime of the file object, so the notion of current "read" and "write" subdevice is local to the file object and does not alter anything in the main control structure for the comedi device. An extra level of indirection is now required to access the main control structure. I've tested the multiple "read" subdevice case using a modified version of the "comedi_test" module (modifying it to clone the existing AI subdevice), and a modified version of the "comedi_test" application (part of the "comedilib" installation) modified to use the new ioctls. There isn't any support in comedilib itself yet. 1) staging: comedi: prepare support for per-file read and write subdevices 2) staging: comedi: add ioctls to set per-file read and write subdevice drivers/staging/comedi/comedi.h | 2 + drivers/staging/comedi/comedi_compat32.c | 2 + drivers/staging/comedi/comedi_fops.c | 217 +++++++++++++++++++++++++++---- 3 files changed, 196 insertions(+), 25 deletions(-) -- 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/