coresight: moving struct cs_buffers to header file

That way we can re-use the structure in other drivers.

Signed-off-by: Mathieu Poirier <mathieu.poirier@linaro.org>
Reviewed-by: Suzuki K Poulose <suzuki.poulose@arm.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
(cherry picked from commit a02e81f7a32b49f3cb70c5ebd2eab5608a088514)

diff --git a/drivers/hwtracing/coresight/coresight-etb10.c b/drivers/hwtracing/coresight/coresight-etb10.c
index b0d402dbfeae371e95274fbc5e768a3c92876e0e..92f942321e1e86f7f271d8c66d979a740e2f4577 100644 (file)
--- a/drivers/hwtracing/coresight/coresight-etb10.c
+++ b/drivers/hwtracing/coresight/coresight-etb10.c
@@ -70,26 +70,6 @@
 #define ETB_FFSR_BIT           1
 #define ETB_FRAME_SIZE_WORDS   4
 
-/**
- * struct cs_buffer - keep track of a recording session' specifics
- * @cur:       index of the current buffer
- * @nr_pages:  max number of pages granted to us
- * @offset:    offset within the current buffer
- * @data_size: how much we collected in this run
- * @lost:      other than zero if we had a HW buffer wrap around
- * @snapshot:  is this run in snapshot mode
- * @data_pages:        a handle the ring buffer
- */
-struct cs_buffers {
-       unsigned int            cur;
-       unsigned int            nr_pages;
-       unsigned long           offset;
-       local_t                 data_size;
-       local_t                 lost;
-       bool                    snapshot;
-       void                    **data_pages;
-};
-
 /**
  * struct etb_drvdata - specifics associated to an ETB component
  * @base:      memory mapped base address for this component.

diff --git a/drivers/hwtracing/coresight/coresight-priv.h b/drivers/hwtracing/coresight/coresight-priv.h
index 3b5dd95a3588333be5072d343ec9eb9e39936d42..ad975c58080d28b0a43034ff2938825262951322 100644 (file)
--- a/drivers/hwtracing/coresight/coresight-priv.h
+++ b/drivers/hwtracing/coresight/coresight-priv.h
@@ -53,6 +53,26 @@ enum cs_mode {
        CS_MODE_PERF,
 };
 
+/**
+ * struct cs_buffer - keep track of a recording session' specifics
+ * @cur:       index of the current buffer
+ * @nr_pages:  max number of pages granted to us
+ * @offset:    offset within the current buffer
+ * @data_size: how much we collected in this run
+ * @lost:      other than zero if we had a HW buffer wrap around
+ * @snapshot:  is this run in snapshot mode
+ * @data_pages:        a handle the ring buffer
+ */
+struct cs_buffers {
+       unsigned int            cur;
+       unsigned int            nr_pages;
+       unsigned long           offset;
+       local_t                 data_size;
+       local_t                 lost;
+       bool                    snapshot;
+       void                    **data_pages;
+};
+
 static inline void CS_LOCK(void __iomem *addr)
 {
        do {