On Thursday 12 April 2012 06:45 PM, Jonathan Cameron wrote:SAMP_FREQ is fine internally.On 4/12/2012 1:38 PM, Laxman Dewangan wrote:Adding channel info IIO_CHAN_INFO_SAMP_FREQ to selectTo match with the existing devices can we not use the abrieviation
different sampling frequency per channel wise.
Signed-off-by: Laxman Dewangan<ldewangan@xxxxxxxxxx>
---
As per discussion on previous patch, adding channel info
for selecting sampling freqeuncy.
for the attribute naming.
Sorry..I did not get it completely.
Is it like we should have IIO_CHAN_INFO_SAMPLING_FREQUENCY in place of IIO_CHAN_INFO_SAMP_FREQ?
Yup, that's the one that is (in the general all channels case) already in the abi docs...
@@ -90,6 +90,7 @@ static const char * const iio_chan_info_postfix[] = {"sampling_frequency"
[IIO_CHAN_INFO_AVERAGE_RAW] = "mean_raw",
[IIO_CHAN_INFO_LOW_PASS_FILTER_3DB_FREQUENCY]
= "filter_low_pass_3db_frequency",
+ [IIO_CHAN_INFO_SAMP_FREQ] = "samp_freq",
and then change here as "sampling_frequency"?
--
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