1 /* SPDX-License-Identifier: GPL-2.0 */ 2 3 /* Copyright (c) 2012-2018, The Linux Foundation. All rights reserved. 4 * Copyright (C) 2019-2021 Linaro Ltd. 5 */ 6 #ifndef _IPA_DATA_H_ 7 #define _IPA_DATA_H_ 8 9 #include <linux/types.h> 10 11 #include "ipa_version.h" 12 #include "ipa_endpoint.h" 13 #include "ipa_mem.h" 14 15 /** 16 * DOC: IPA/GSI Configuration Data 17 * 18 * Boot-time configuration data is used to define the configuration of the 19 * IPA and GSI resources to use for a given platform. This data is supplied 20 * via the Device Tree match table, associated with a particular compatible 21 * string. The data defines information about how resources, endpoints and 22 * channels, memory, power and so on are allocated and used for the 23 * platform. 24 * 25 * Resources are data structures used internally by the IPA hardware. The 26 * configuration data defines the number (or limits of the number) of various 27 * types of these resources. 28 * 29 * Endpoint configuration data defines properties of both IPA endpoints and 30 * GSI channels. A channel is a GSI construct, and represents a single 31 * communication path between the IPA and a particular execution environment 32 * (EE), such as the AP or Modem. Each EE has a set of channels associated 33 * with it, and each channel has an ID unique for that EE. For the most part 34 * the only GSI channels of concern to this driver belong to the AP 35 * 36 * An endpoint is an IPA construct representing a single channel anywhere 37 * in the system. An IPA endpoint ID maps directly to an (EE, channel_id) 38 * pair. Generally, this driver is concerned with only endpoints associated 39 * with the AP, however this will change when support for routing (etc.) is 40 * added. IPA endpoint and GSI channel configuration data are defined 41 * together, establishing the endpoint_id->(EE, channel_id) mapping. 42 * 43 * Endpoint configuration data consists of three parts: properties that 44 * are common to IPA and GSI (EE ID, channel ID, endpoint ID, and direction); 45 * properties associated with the GSI channel; and properties associated with 46 * the IPA endpoint. 47 */ 48 49 /* The maximum possible number of source or destination resource groups */ 50 #define IPA_RESOURCE_GROUP_MAX 8 51 52 /** enum ipa_qsb_master_id - array index for IPA QSB configuration data */ 53 enum ipa_qsb_master_id { 54 IPA_QSB_MASTER_DDR, 55 IPA_QSB_MASTER_PCIE, 56 }; 57 58 /** 59 * struct ipa_qsb_data - Qualcomm System Bus configuration data 60 * @max_writes: Maximum outstanding write requests for this master 61 * @max_reads: Maximum outstanding read requests for this master 62 * @max_reads_beats: Max outstanding read bytes in 8-byte "beats" (if non-zero) 63 */ 64 struct ipa_qsb_data { 65 u8 max_writes; 66 u8 max_reads; 67 u8 max_reads_beats; /* Not present for IPA v3.5.1 */ 68 }; 69 70 /** 71 * struct gsi_channel_data - GSI channel configuration data 72 * @tre_count: number of TREs in the channel ring 73 * @event_count: number of slots in the associated event ring 74 * @tlv_count: number of entries in channel's TLV FIFO 75 * 76 * A GSI channel is a unidirectional means of transferring data to or 77 * from (and through) the IPA. A GSI channel has a ring buffer made 78 * up of "transfer ring elements" (TREs) that specify individual data 79 * transfers or IPA immediate commands. TREs are filled by the AP, 80 * and control is passed to IPA hardware by writing the last written 81 * element into a doorbell register. 82 * 83 * When data transfer commands have completed the GSI generates an 84 * event (a structure of data) and optionally signals the AP with 85 * an interrupt. Event structures are implemented by another ring 86 * buffer, directed toward the AP from the IPA. 87 * 88 * The input to a GSI channel is a FIFO of type/length/value (TLV) 89 * elements, and the size of this FIFO limits the number of TREs 90 * that can be included in a single transaction. 91 */ 92 struct gsi_channel_data { 93 u16 tre_count; /* must be a power of 2 */ 94 u16 event_count; /* must be a power of 2 */ 95 u8 tlv_count; 96 }; 97 98 /** 99 * struct ipa_endpoint_tx_data - configuration data for TX endpoints 100 * @seq_type: primary packet processing sequencer type 101 * @seq_rep_type: sequencer type for replication processing 102 * @status_endpoint: endpoint to which status elements are sent 103 * 104 * The @status_endpoint is only valid if the endpoint's @status_enable 105 * flag is set. 106 */ 107 struct ipa_endpoint_tx_data { 108 enum ipa_seq_type seq_type; 109 enum ipa_seq_rep_type seq_rep_type; 110 enum ipa_endpoint_name status_endpoint; 111 }; 112 113 /** 114 * struct ipa_endpoint_rx_data - configuration data for RX endpoints 115 * @buffer_size: requested receive buffer size (bytes) 116 * @pad_align: power-of-2 boundary to which packet payload is aligned 117 * @aggr_close_eof: whether aggregation closes on end-of-frame 118 * 119 * With each packet it transfers, the IPA hardware can perform certain 120 * transformations of its packet data. One of these is adding pad bytes 121 * to the end of the packet data so the result ends on a power-of-2 boundary. 122 * 123 * It is also able to aggregate multiple packets into a single receive buffer. 124 * Aggregation is "open" while a buffer is being filled, and "closes" when 125 * certain criteria are met. One of those criteria is the sender indicating 126 * a "frame" consisting of several transfers has ended. 127 */ 128 struct ipa_endpoint_rx_data { 129 u32 buffer_size; 130 u32 pad_align; 131 bool aggr_close_eof; 132 }; 133 134 /** 135 * struct ipa_endpoint_config_data - IPA endpoint hardware configuration 136 * @resource_group: resource group to assign endpoint to 137 * @checksum: whether checksum offload is enabled 138 * @qmap: whether endpoint uses QMAP protocol 139 * @aggregation: whether endpoint supports aggregation 140 * @status_enable: whether endpoint uses status elements 141 * @dma_mode: whether endpoint operates in DMA mode 142 * @dma_endpoint: peer endpoint, if operating in DMA mode 143 * @tx: TX-specific endpoint information (see above) 144 * @rx: RX-specific endpoint information (see above) 145 */ 146 struct ipa_endpoint_config_data { 147 u32 resource_group; 148 bool checksum; 149 bool qmap; 150 bool aggregation; 151 bool status_enable; 152 bool dma_mode; 153 enum ipa_endpoint_name dma_endpoint; 154 union { 155 struct ipa_endpoint_tx_data tx; 156 struct ipa_endpoint_rx_data rx; 157 }; 158 }; 159 160 /** 161 * struct ipa_endpoint_data - IPA endpoint configuration data 162 * @filter_support: whether endpoint supports filtering 163 * @config: hardware configuration (see above) 164 * 165 * Not all endpoints support the IPA filtering capability. A filter table 166 * defines the filters to apply for those endpoints that support it. The 167 * AP is responsible for initializing this table, and it must include entries 168 * for non-AP endpoints. For this reason we define *all* endpoints used 169 * in the system, and indicate whether they support filtering. 170 * 171 * The remaining endpoint configuration data applies only to AP endpoints. 172 */ 173 struct ipa_endpoint_data { 174 bool filter_support; 175 /* Everything else is specified only for AP endpoints */ 176 struct ipa_endpoint_config_data config; 177 }; 178 179 /** 180 * struct ipa_gsi_endpoint_data - GSI channel/IPA endpoint data 181 * @ee_id: GSI execution environment ID 182 * @channel_id: GSI channel ID 183 * @endpoint_id: IPA endpoint ID 184 * @toward_ipa: direction of data transfer 185 * @channel: GSI channel configuration data (see above) 186 * @endpoint: IPA endpoint configuration data (see above) 187 */ 188 struct ipa_gsi_endpoint_data { 189 u8 ee_id; /* enum gsi_ee_id */ 190 u8 channel_id; 191 u8 endpoint_id; 192 bool toward_ipa; 193 194 struct gsi_channel_data channel; 195 struct ipa_endpoint_data endpoint; 196 }; 197 198 /** 199 * struct ipa_resource_limits - minimum and maximum resource counts 200 * @min: minimum number of resources of a given type 201 * @max: maximum number of resources of a given type 202 */ 203 struct ipa_resource_limits { 204 u32 min; 205 u32 max; 206 }; 207 208 /** 209 * struct ipa_resource - resource group source or destination resource usage 210 * @limits: array of resource limits, indexed by group 211 */ 212 struct ipa_resource { 213 struct ipa_resource_limits limits[IPA_RESOURCE_GROUP_MAX]; 214 }; 215 216 /** 217 * struct ipa_resource_data - IPA resource configuration data 218 * @rsrc_group_src_count: number of source resource groups supported 219 * @rsrc_group_dst_count: number of destination resource groups supported 220 * @resource_src_count: number of entries in the resource_src array 221 * @resource_src: source endpoint group resources 222 * @resource_dst_count: number of entries in the resource_dst array 223 * @resource_dst: destination endpoint group resources 224 * 225 * In order to manage quality of service between endpoints, certain resources 226 * required for operation are allocated to groups of endpoints. Generally 227 * this information is invisible to the AP, but the AP is responsible for 228 * programming it at initialization time, so we specify it here. 229 */ 230 struct ipa_resource_data { 231 u32 rsrc_group_src_count; 232 u32 rsrc_group_dst_count; 233 u32 resource_src_count; 234 const struct ipa_resource *resource_src; 235 u32 resource_dst_count; 236 const struct ipa_resource *resource_dst; 237 }; 238 239 /** 240 * struct ipa_mem_data - description of IPA memory regions 241 * @local_count: number of regions defined in the local[] array 242 * @local: array of IPA-local memory region descriptors 243 * @imem_addr: physical address of IPA region within IMEM 244 * @imem_size: size in bytes of IPA IMEM region 245 * @smem_id: item identifier for IPA region within SMEM memory 246 * @smem_size: size in bytes of the IPA SMEM region 247 */ 248 struct ipa_mem_data { 249 u32 local_count; 250 const struct ipa_mem *local; 251 u32 imem_addr; 252 u32 imem_size; 253 u32 smem_id; 254 u32 smem_size; 255 }; 256 257 /** 258 * struct ipa_interconnect_data - description of IPA interconnect bandwidths 259 * @name: Interconnect name (matches interconnect-name in DT) 260 * @peak_bandwidth: Peak interconnect bandwidth (in 1000 byte/sec units) 261 * @average_bandwidth: Average interconnect bandwidth (in 1000 byte/sec units) 262 */ 263 struct ipa_interconnect_data { 264 const char *name; 265 u32 peak_bandwidth; 266 u32 average_bandwidth; 267 }; 268 269 /** 270 * struct ipa_power_data - description of IPA power configuration data 271 * @core_clock_rate: Core clock rate (Hz) 272 * @interconnect_count: Number of entries in the interconnect_data array 273 * @interconnect_data: IPA interconnect configuration data 274 */ 275 struct ipa_power_data { 276 u32 core_clock_rate; 277 u32 interconnect_count; /* # entries in interconnect_data[] */ 278 const struct ipa_interconnect_data *interconnect_data; 279 }; 280 281 /** 282 * struct ipa_data - combined IPA/GSI configuration data 283 * @version: IPA hardware version 284 * @backward_compat: BCR register value (prior to IPA v4.5 only) 285 * @qsb_count: number of entries in the qsb_data array 286 * @qsb_data: Qualcomm System Bus configuration data 287 * @endpoint_count: number of entries in the endpoint_data array 288 * @endpoint_data: IPA endpoint/GSI channel data 289 * @resource_data: IPA resource configuration data 290 * @mem_data: IPA memory region data 291 * @power_data: IPA power data 292 */ 293 struct ipa_data { 294 enum ipa_version version; 295 u32 backward_compat; 296 u32 qsb_count; /* number of entries in qsb_data[] */ 297 const struct ipa_qsb_data *qsb_data; 298 u32 endpoint_count; /* number of entries in endpoint_data[] */ 299 const struct ipa_gsi_endpoint_data *endpoint_data; 300 const struct ipa_resource_data *resource_data; 301 const struct ipa_mem_data *mem_data; 302 const struct ipa_power_data *power_data; 303 }; 304 305 extern const struct ipa_data ipa_data_v3_1; 306 extern const struct ipa_data ipa_data_v3_5_1; 307 extern const struct ipa_data ipa_data_v4_2; 308 extern const struct ipa_data ipa_data_v4_5; 309 extern const struct ipa_data ipa_data_v4_9; 310 extern const struct ipa_data ipa_data_v4_11; 311 312 #endif /* _IPA_DATA_H_ */ 313