qcacmn: Clarify usage on Q_TARGET_ACCESS_BEGIN/END
Document where register writes are for legacy vs srng devices.
With the target access begin/end calls being associated with
the register writes and the register writes being associated to
specific HW, we avoid performing unneeded force wakes on common
code paths shared by legacy & srng based hardware.
Change-Id: Id91399d03298bfc5df56f0c5d5d14b648b665279
CRs-Fixed: 2117144
diff --git a/hif/src/ce/ce_api.h b/hif/src/ce/ce_api.h
index e3fa2c7..786f447 100644
--- a/hif/src/ce/ce_api.h
+++ b/hif/src/ce/ce_api.h
@@ -495,7 +495,7 @@
struct ce_ops {
uint32_t (*ce_get_desc_size)(uint8_t ring_type);
- void (*ce_ring_setup)(struct hif_softc *scn, uint8_t ring_type,
+ int (*ce_ring_setup)(struct hif_softc *scn, uint8_t ring_type,
uint32_t ce_id, struct CE_ring_state *ring,
struct CE_attr *attr);
int (*ce_send_nolock)(struct CE_handle *copyeng,