Linux and UNIX Man Pages

Linux & Unix Commands - Search Man Pages

wimax_report_rfkill_sw(9) [centos man page]

WIMAX_REPORT_RFKILL_(9) 					 Linux Networking					   WIMAX_REPORT_RFKILL_(9)

wimax_report_rfkill_sw - Reports changes in the software RF switch SYNOPSIS
void wimax_report_rfkill_sw(struct wimax_dev * wimax_dev, enum wimax_rf_state state); ARGUMENTS
wimax_dev WiMAX device descriptor state New state of the RF kill switch. WIMAX_RF_ON radio on, WIMAX_RF_OFF radio off. DESCRIPTION
Reports changes in the software RF switch state to the the WiMAX stack. The main use is during initialization, so the driver can query the device for its current software radio kill switch state and feed it to the system. On the side, the device does not change the software state by itself. In practice, this can happen, as the device might decide to switch (in software) the radio off for different reasons. COPYRIGHT
Kernel Hackers Manual 3.10 June 2014 WIMAX_REPORT_RFKILL_(9)

Check Out this Related Man Page

WIMAX_ST(9) Linux Networking ENUM WIMAX_ST(9) NAME
enum_wimax_st - The different states of a WiMAX device SYNOPSIS
__WIMAX_ST_NULL The device structure has been allocated and zeroed, but still wimax_dev_add hasn't been called. There is no state. WIMAX_ST_DOWN The device has been registered with the WiMAX and networking stacks, but it is not initialized (normally that is done with 'ifconfig DEV up' [or equivalent], which can upload firmware and enable communications with the device). In this state, the device is powered down and using as less power as possible. This state is the default after a call to wimax_dev_add. It is ok to have drivers move directly to WIMAX_ST_UNINITIALIZED or WIMAX_ST_RADIO_OFF in _probe after the call to wimax_dev_add. It is recommended that the driver leaves this state when calling 'ifconfig DEV up' and enters it back on 'ifconfig DEV down'. __WIMAX_ST_QUIESCING The device is being torn down, so no API operations are allowed to proceed except the ones needed to complete the device clean up process. WIMAX_ST_UNINITIALIZED [optional] Communication with the device is setup, but the device still requires some configuration before being operational. Some WiMAX API calls might work. WIMAX_ST_RADIO_OFF The device is fully up; radio is off (wether by hardware or software switches). It is recommended to always leave the device in this state after initialization. WIMAX_ST_READY The device is fully up and radio is on. WIMAX_ST_SCANNING [optional] The device has been instructed to scan. In this state, the device cannot be actively connected to a network. WIMAX_ST_CONNECTING The device is connecting to a network. This state exists because in some devices, the connect process can include a number of negotiations between user space, kernel space and the device. User space needs to know what the device is doing. If the connect sequence in a device is atomic and fast, the device can transition directly to CONNECTED WIMAX_ST_CONNECTED The device is connected to a network. __WIMAX_ST_INVALID This is an invalid state used to mark the maximum numeric value of states. DESCRIPTION
Transitions from one state to another one are atomic and can only be caused in kernel space with wimax_state_change. To read the state, use wimax_state_get. States starting with __ are internal and shall not be used or referred to by drivers or userspace. They look ugly, but that's the point -- if any use is made non-internal to the stack, it is easier to catch on review. All API operations [with well defined exceptions] will take the device mutex before starting and then check the state. If the state is __WIMAX_ST_NULL, WIMAX_ST_DOWN, WIMAX_ST_UNINITIALIZED or __WIMAX_ST_QUIESCING, it will drop the lock and quit with -EINVAL, -ENOMEDIUM, -ENOTCONN or -ESHUTDOWN. The order of the definitions is important, so we can do numerical comparisons (eg: < WIMAX_ST_RADIO_OFF means the device is not ready to operate). COPYRIGHT
Kernel Hackers Manual 2.6. July 2010 ENUM WIMAX_ST(9)
Man Page