linux/platform_data/brcmfmac.h

12  * WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN ACTION
27  * Platform specific driver functions and data. Through the platform specific
28  * device data functions and data can be provided to help the brcmfmac driver to
29  * operate with the device in combination with the used platform.
34  * Note: the brcmfmac can be loaded as module or be statically built-in into
35  * the kernel. If built-in then do note that it uses module_init (and
37  * create a module with the platform specific data for the brcmfmac and have
38  * it built-in to the kernel then use a higher initcall then device_initcall
40  * but will not pickup the platform data.
42  * When the driver does not "detect" platform driver data then it will continue
43  * without reporting anything and just assume there is no data needed. Which is
48  * enum brcmf_bus_type - Bus type identifier. Currently SDIO, USB and PCIE are
59  * struct brcmfmac_sdio_pd - SDIO Device specific platform data.
69  *			in-band interrupts are relatively slow and for having
81  * @sd_head_align:	alignment requirement for start of data buffer.
86  *			dongle via sdio data interface, but it requires that
104  * struct brcmfmac_pd_cc_entry - Struct for translating user space country code
119  * struct brcmfmac_pd_cc - Struct for translating country codes as set by user
132  * struct brcmfmac_pd_device - Device specific platform data. (id/rev/bus_type)
135  * @id:			ID of the device for which this data is. In case of SDIO
161  * struct brcmfmac_platform_data - BRCMFMAC specific platform data.
165  *		devices. The platform spcific routine may for example decide to
166  *		power up the complete device. If there is no use-case for this
173  *		for low power devices. If there is no use-case for this