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
93
values. The value is in Mbps and minimum value is 0 Mbps. This parameter should be assigned a value which
is less than the value assigned to the <rx_threshold> parameter.
• <monitor_interval>: This parameter specifies the duration (in milliseconds) over which the Transmit and
Receive throughputs are computed to compare with the <tx_threshold>, <rx_threshold>, <tx_hysteresis>
and <rx_hysteresis> values. The maximum value of this parameter is 30000 ms (30 seconds).
• <sleep_duration>: This parameter specifies the duration (in milliseconds) for which the module sleeps in
the Deep Sleep mode. For LP mode, a value of 0 for the <sleep_duration> parameter programs the module
to be in Deep Sleep mode indefinitely till it is woken up by the Host processor via the host interface. The
value of 0 is invalid for ULP mode and should not be used. The maximum value for this parameter can be
65535.
• <listen_interval_duration>: This parameter specifies the duration (in milliseconds) for which the module
sleeps in the connected state power save modes. If a non-zero value is assigned to this parameter it takes
precedence over the other sleep duration parameters that follow (<num_beacons_per_listen_interval>,
<dtim_interval_duration>, <num_dtims_per_sleep>). The maximum duration for which the device supports
sleep is 4095 times the duration of the beacon interval considering the listen interval parameters of the
access point. The maximum value for this parameter can be 65535, but the duration should be the deciding
factor in the beacon interval of the access point. This parameter is considered only after the module is
connected to the access point. For example, if the beacon interval of the AP is 100ms and listen interval of
AP is 8 beacons, then the maximum time the device can sleep without any data loss is 800 ms (8 * 100).
Hence, the listen_interval_duration can be up to 800ms.
• <num_beacons_per_listen_interval>: This parameter specifies the number of beacon intervals for which
the module sleeps in the connected state power save modes. Here, the device will wake up for the nth
beacon, where n is the listen interval value programmed by the user. If a non-zero value is assigned to this
parameter it takes precedence over the other sleep duration parameters that follow
(<dtim_interval_duration>, <num_dtims_per_sleep>). This parameter is used only when the above
parameter is assigned to 0. The maximum value for this parameter is 4095. The value for this parameter also
has to be chosen keeping in mind the listen interval of the access point. . This parameter is considered only
after the module is connected to the access point.
• <dtim_interval_duration>: This parameter specifies the duration (in milliseconds) for which the module
sleeps in the connected state power save modes. The device will wake up for the nearest DTIM beacon after
the time which the user has programmed expires. This parameter can be used when DTIM information is not
available. If a non-zero value is assigned to this parameter, then it takes precedence over the other sleep
duration parameter that follows (<num_dtims_per_sleep>). This parameter is used only when the above
parameters are assigned 0. The maximum value for this parameter can be 10000ms. This parameter is
considered only after the module is connected to the access point.
• <num_dtims_per_sleep>: This parameter specifies the number of DTIM intervals for which the module
sleeps in the connected state power save modes. This parameter has least priority compared to the ones
above and is used only if the above parameters are assigned to 0. The maximum value for this parameter is
10. This parameter is considered only after the module is connected to the access point.
15.5 Procedure to enable device power save for USB interface
In order to enable power save for USB interface, following steps must be followed after enabling LP power save on
USB interface.
Find where the RSI module got detected.
Eg: When RSI module is inserted, following prints are observed when dmesg is done.
The LP and ULP Power Save modes are supported with SDIO interface. USB interface supports only LP
Power Save mode