Reference Manual
Table Of Contents
- Introduction to RS9116
- Getting Started with RS9116
- Compiling the Driver
- Installing the Driver
- Installation of Modules
- Enabling a Protocol
- Disabling a Protocol
- OneBox-Mobile in Wi-Fi Only Mode
- Installation in Wi-Fi Client Mode (with BSD interface support)
- Installation in Access Point Mode (with BSD interface support)
- Installation in Wi-Fi Client Mode (with NL80211 support)
- Installation in Wi-Fi AP mode (with NL80211 support)
- Installation in Wi-Fi Direct Mode (With BSD Interface Support)
- Installation in Wi-Fi Direct Mode (With NL80211 Support only for Kernel v3.8 or higher)
- OneBox-Mobile in Wi-Fi + Bluetooth LE Coexistence Mode
- Driver Information
- Wi-Fi ioctl Usage Guide
- Configuration Using CFG80211
- Enterprise security using CFG80211
- HOSTAPD and Wi-Fi Protected Setup (WPS)
- ACS with Hostapd
- Antenna Diversity
- Sniffer Mode
- Monitor Mode
- Concurrent Mode
- Background Scan Parameters
- Power save Modes, Profiles and Parameters
- Compliance and Certification
- Wi-Fi Performance Test ioctl usage
- Wake-On-Wireless LAN
- PUF [ Physical Unclonable Functions ]
- GTK Offload
- Steps to connect 802.11R client to AP
- Steps to configure 802.11W
- Update WLAN region based maximum powers from driver
- Bluetooth hcitool and hciconfig Usage
- Android support for RS9116
- Appendix A: Configuration of Kernels from 3.13 and above
- Appendix B: Binary Files for Embedded Platforms
- Appendix C: Using the Bluetooth Manager
- Appendix D: Common Configuration Parameters
- Appendix E: Installation of Missing Generic Netlink Libraries
- Appendix F: Procedure to use latest supplicant with NL80211 interface
- Appendix G: Considerations need to be made during hostapd usage
- RS9116 n-Link Software TRM Revision History
RS9116 n-Link Linux and Android Technical Reference Manual
Version 2.0
August 2019
104
18 Wake-On-Wireless LAN
18.1 WoWLAN through onebox_util
The parameters listed below for the Wake-On-Wireless LAN are valid only in Client mode. The <hw_bmiss>
parameter needs to be given as an input during VAP creation inorder to use the WoWLAN feature – refer to the
section 5.5 Configuring Using onebox_util for details on VAP creation.
• <base_interface>: Base Interface (string like rpine0)
• <src_mac_addr>: This parameter is the 48-bit Source MAC address in hexadecimal format with colon
separation, which is used to filter the Unicast packets received by the device. This parameter is valid only
when bit 2 of the <wowlan_flags> parameter is set to '1'.
• <host_sleep_status>: This parameter informs the device whether the Host is entering sleep state ("1") or
exiting sleep state ("0"). The device will toggle the GPIO_2 (Host Wakeup Interrupt) only when the Host
indicates that it is entering to sleep state.
• <wowlan_flags>: This parameter is a bitmap used to program the device to wake up the Host based on the
type of packets received by it. It is a 16-bit value as explained in the table below. The Host can program
multiple bits to "1" at the same time to enable wakeup on different types of events.
18.2 WoWLAN using Linux power state machine
Linux supports different power states to handle power management i.e. S3 (suspend), S4 (hibernate) and S5
(poweroff). WoWLAN can be verified through these power states which is the idle way. Presently only S3 is
supported in N-Link Linux driver. Also WoWLAN configuration is allowed in NL80211 interface only. Enable
ONEBOX_CONFIG_WOWLAN in Makefile to use this feature before building the driver. It supports kernel v3.11 or
higher
18.2.1 Overview
WoWLAN is a power saving technique where device goes to sleep until an explicit trigger is received through WLAN.
For this feature to work station should be connected to an AP and the connection should retain while the system is
in suspend. User shall configure WoWLAN trigger types like magic packet or pattern etc using which he wants to
wake up the system. This trigger packet will be received by the WLAN device through AP. Device firmware shall
process the trigger and check whether it is a valid trigger or not. If it is a valid trigger packet, it will trigger the GPIO
of host wake-up. It is the vendor responsibility to map this GPIO to the platform’s power module.
To verify WoWLAN below steps are needed:
• Configure WoWLAN
• Suspend the system
• Trigger wakeup
The above configuration is used only when you have kept the device in transmit burst mode and has
made random hopping as "enabled". For more details in "Configuration of device in the transmit burst
mode", please refer to the section
18.2.1BT Transmit Tests.