On 02/10/15 01:23, H Hartley Sweeten wrote:
According to the users manual, the conversion timing (scanrate) is fixed to 100, 50, or 25 kHz. The pacer clock is then used to trigger each scan. Currently this driver tries to fake other conversion speeds by always sampling the inputs at 100 kHz and using the pacer clock to trigger each conversion. It does this by setting the SCANLIST_START bit for each entry in the scan list. According to the users manual, this bit has to be set for the first (and ONLY the first) entry of the scan list.
I'm not sure. If you read the remainder of that paragraph in the manual, it says you can use that bit to chop the scan list into pieces, which is what I think the original code is doing.
I'd say it's safest to leave the timing alone, as presumably any existing users are happy with the way it is.
-- -=( Ian Abbott @ MEV Ltd. E-mail: <abbotti@xxxxxxxxx> )=- -=( Web: http://www.mev.co.uk/ )=- _______________________________________________ devel mailing list devel@xxxxxxxxxxxxxxxxxxxxxx http://driverdev.linuxdriverproject.org/mailman/listinfo/driverdev-devel
