Currently none of the buffer implementations implements the enable() or
is_enable() nor does core code try to call these. So it is safe to remove them.

Acked-by: Jonathan Cameron <[email protected]>
Signed-off-by: Lars-Peter Clausen <[email protected]>
---
 drivers/staging/iio/Documentation/ring.txt |    4 ----
 drivers/staging/iio/buffer.h               |    5 -----
 2 files changed, 0 insertions(+), 9 deletions(-)

diff --git a/drivers/staging/iio/Documentation/ring.txt 
b/drivers/staging/iio/Documentation/ring.txt
index 7e99ef2..1b77aee 100644
--- a/drivers/staging/iio/Documentation/ring.txt
+++ b/drivers/staging/iio/Documentation/ring.txt
@@ -51,7 +51,3 @@ get_bytes_per_datum, set_bytes_per_datum
 get_length / set_length
   Get/set the number of complete scans that may be held by the buffer.
 
-is_enabled
-  Query if ring buffer is in use
-enable
-  Start the ring buffer.
diff --git a/drivers/staging/iio/buffer.h b/drivers/staging/iio/buffer.h
index eb4938c..b0e04df 100644
--- a/drivers/staging/iio/buffer.h
+++ b/drivers/staging/iio/buffer.h
@@ -31,8 +31,6 @@ struct iio_buffer;
  * @set_bytes_per_datum:set number of bytes per datum
  * @get_length:                get number of datums in buffer
  * @set_length:                set number of datums in buffer
- * @is_enabled:                query if buffer is currently being used
- * @enable:            enable the buffer
  *
  * The purpose of this structure is to make the buffer element
  * modular as event for a given driver, different usecases may require
@@ -58,9 +56,6 @@ struct iio_buffer_access_funcs {
        int (*set_bytes_per_datum)(struct iio_buffer *buffer, size_t bpd);
        int (*get_length)(struct iio_buffer *buffer);
        int (*set_length)(struct iio_buffer *buffer, int length);
-
-       int (*is_enabled)(struct iio_buffer *buffer);
-       int (*enable)(struct iio_buffer *buffer);
 };
 
 /**
-- 
1.7.7.3


_______________________________________________
devel mailing list
[email protected]
http://driverdev.linuxdriverproject.org/mailman/listinfo/devel

Reply via email to