struct_uio_mem(9) [centos man page]

STRUCT 
UIO_MEM(9)					   Device drivers infrastructure					 STRUCT UIO_MEM(9)

NAME

       struct_uio_mem - description of a UIO memory region

SYNOPSIS

       struct uio_mem {
	 const char * name;
	 phys_addr_t addr;
	 unsigned long size;
	 int memtype;
	 void __iomem * internal_addr;
	 struct uio_map * map;
       };

MEMBERS

       name
	   name of the memory region for identification

       addr
	   address of the device's memory (phys_addr is used since addr can be logical, virtual, or physical & phys_addr_t should always be large
	   enough to handle any of the address types)

       size
	   size of IO

       memtype
	   type of memory addr points to

       internal_addr
	   ioremap-ped version of addr, for driver internal use

       map
	   for use by the UIO core only.

COPYRIGHT

Kernel Hackers Manual 3.10					     June 2014							 STRUCT UIO_MEM(9)

STRUCT 
IEEE80211_VIF(9) 				  The basic mac80211 driver inte				   STRUCT IEEE80211_VIF(9)

NAME

       struct_ieee80211_vif - per-interface data

SYNOPSIS

       struct ieee80211_vif {
	 enum nl80211_iftype type;
	 struct ieee80211_bss_conf bss_conf;
	 u8 addr[ETH_ALEN];
	 bool p2p;
	 u8 cab_queue;
	 u8 hw_queue[IEEE80211_NUM_ACS];
	 struct ieee80211_chanctx_conf __rcu * chanctx_conf;
	 u32 driver_flags;
       #ifdef CONFIG_MAC80211_DEBUGFS
	 struct dentry * debugfs_dir;
       #endif
	 u8 drv_priv[0];
       };

MEMBERS

       type
	   type of this virtual interface

       bss_conf
	   BSS configuration for this interface, either our own or the BSS we're associated to

       addr[ETH_ALEN]
	   address of this interface

       p2p
	   indicates whether this AP or STA interface is a p2p interface, i.e. a GO or p2p-sta respectively

       cab_queue
	   content-after-beacon (DTIM beacon really) queue, AP mode only

       hw_queue[IEEE80211_NUM_ACS]
	   hardware queue for each AC

       chanctx_conf
	   The channel context this interface is assigned to, or NULL when it is not assigned. This pointer is RCU-protected due to the TX path
	   needing to access it; even though the netdev carrier will always be off when it is NULL there can still be races and packets could be
	   processed after it switches back to NULL.

       driver_flags
	   flags/capabilities the driver has for this interface, these need to be set (or cleared) when the interface is added or, if supported by
	   the driver, the interface type is changed at runtime, mac80211 will never touch this field

       debugfs_dir
	   debugfs dentry, can be used by drivers to create own per interface debug files. Note that it will be NULL for the virtual monitor
	   interface (if that is requested.)

       drv_priv[0]
	   data area for driver use, will always be aligned to sizeof(void *).

DESCRIPTION

       Data in this structure is continually present for driver use during the life of a virtual interface.

AUTHOR

       Johannes Berg <johannes@sipsolutions.net>
	   Author.

COPYRIGHT

Kernel Hackers Manual 3.10					     June 2014						   STRUCT IEEE80211_VIF(9)