summaryrefslogtreecommitdiffstats
path: root/tools
diff options
context:
space:
mode:
authorSpencer E. Olson <olsonse@umich.edu>2018-09-19 10:51:03 -0600
committerGreg Kroah-Hartman <gregkh@linuxfoundation.org>2018-10-09 15:27:47 +0200
commit832f33366c771855951313a9bab4926f2a0d37a1 (patch)
treea19bafeeef43d6dc0f5ef8ed3d52a7486531d5af /tools
parent20438d93d4304c0fc6e063c0e1f8d6580e88a29b (diff)
downloadlinux-stable-832f33366c771855951313a9bab4926f2a0d37a1.tar.gz
linux-stable-832f33366c771855951313a9bab4926f2a0d37a1.tar.bz2
linux-stable-832f33366c771855951313a9bab4926f2a0d37a1.zip
staging: comedi: add facility to directly query subdevice timing constraints
Adds facility to directly query the hardware speed limits of subdevices, in particular for scan_begin and convert signals. This information can be critical for integrating comedi with other hardware modules, and also comedi modules together with software where software requires specific timing capabilities in order to properly coordinate multiple devices. Currently, comedi_command_test almost satisfies this need, but really only for when *_src == TRIG_TIMER. For *_src == TRIG_EXT, comedi_command_test does not help at all. For many subdevices, one might simply use *_src==TRIG_TIMER in command_test in order to determine these limits. For other subdevices, this tactic does not work since *_src == TRIG_TIMER might not be valid. There is also the possibility that the timing limits are different between the TRIG_TIMER and TRIG_EXT modes. Signed-off-by: Spencer E. Olson <olsonse@umich.edu> Reviewed-by: Ian Abbott <abbotti@mev.co.uk> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Diffstat (limited to 'tools')
0 files changed, 0 insertions, 0 deletions