On 02/27/2013 07:28 PM, Jonathan Cameron wrote: > On 02/27/2013 05:36 PM, Chris Micali wrote: >> lars, >> >> I was under the impression that flag gets added automatically by iio_triggered_buffer_setup (industrialiio-triggers.c:77) - I actually am now able to enable the scan_element after changing my channel .channel and .scan_index to 0 (trying to match exactly the other drivers.) > Yea, you are right I missed the iio_triggered_buffer_setup part. > Strange, scan_index should have defaulted to zero and the .channel value shouldn't have mattered > for buffered reads (just effects naming). Might have caused issues with userspace expecting a channel 0 > though... I guess the scan_index had nothing to do with this, but I suggested to set scan_elements/in_voltage0_en to 1, so this clearly wouldn't have worked with .channel being 1. > >> When i run general_buffer (from the docs dir) with that scan element enabled it can no longer read the trigger (Could not open /trigger/current_trigger Failed to write current_trigger file) - this succeeds if that scan_element is not enabled. You can't change the trigger if the buffer is currently enabled. Make sure that he buffer is disabled (check the buffer/enable attribute). - Lars u -- 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
