On 30 August 2016 08:41:18 BST, Matt Ranostay <mranostay@xxxxxxxxx> wrote: >On Mon, Aug 29, 2016 at 10:03 AM, Joshua Clayton ><stillcompiling@xxxxxxxxx> wrote: >> Jonathan, >> >> I have an out-of tree driver I am working on mainlining. >> >> The device is a sensor that gets phase and amplitude (x and y) data >> >> on multiple physical and/or time multiplexed channels. >> >> It also has up to 4 optical encoders to get physical location. >> >> The existing driver bundles x and y together with a snapshot >> >> of the encoder sums at that moment. >> >> >> This seems like a good fit for iio, but one item is bothering me. >> >> How is synchronization between streams usually handled with >> >> iio drivers? Timing can be important. > >Wouldn't the trigger buffer framework be good enough for this? Perhaps you could describe your usecase a little more? Is the interesting bit that you want to sync streams with different sampling frequencies? Are those encoders better represented by a separate driver? (In which case I have some thoughts on simple additions to IIO trigger handling that might help - basically a hold off on triggers until all relevant devices are attached) > >> >> Joshua Clayton >> >> >> -- >> To unsubscribe from this list: send the line "unsubscribe linux-iio" >in >> the body of a message to majordomo@xxxxxxxxxxxxxxx >> More majordomo info at http://vger.kernel.org/majordomo-info.html -- Sent from my Android device with K-9 Mail. Please excuse my brevity. -- To unsubscribe from this list: send the line "unsubscribe linux-iio" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
