2019-05-29 17:12:42 +03:00
|
|
|
// SPDX-License-Identifier: GPL-2.0-only
|
wimax: basic API: kernel/user messaging, rfkill and reset
Implements the three basic operations provided by the stack's control
interface to WiMAX devices:
- Messaging channel between user space and driver/device
This implements a direct communication channel between user space
and the driver/device, by which free form messages can be sent back
and forth.
This is intended for device-specific features, vendor quirks, etc.
- RF-kill framework integration
Provide most of the RF-Kill integration for WiMAX drivers so that
all device drivers have to do is after wimax_dev_add() is call
wimax_report_rfkill_{hw,sw}() to update initial state and then every
time it changes.
Provides wimax_rfkill() for the kernel to call to set software
RF-Kill status and/or query current hardware and software switch
status.
Exports wimax_rfkill() over generic netlink to user space.
- Reset a WiMAX device
Provides wimax_reset() for the kernel to reset a wimax device as
needed and exports it over generic netlink to user space.
This API is clearly limited, as it still provides no way to do the
basic scan, connect and disconnect in a hardware independent way. The
WiMAX case is more complex than WiFi due to the way networks are
discovered and provisioned.
The next developments are to add the basic operations so they can be
offerent by different drivers. However, we'd like to get more vendors
to jump in and provide feedback of how the user/kernel API/abstraction
layer should be.
The user space code for the i2400m, as of now, uses the messaging
channel, but that will change as the API evolves.
Signed-off-by: Inaky Perez-Gonzalez <inaky@linux.intel.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
2008-12-21 03:57:38 +03:00
|
|
|
/*
|
|
|
|
* Linux WiMAX
|
|
|
|
* Implement and export a method for resetting a WiMAX device
|
|
|
|
*
|
|
|
|
* Copyright (C) 2008 Intel Corporation <linux-wimax@intel.com>
|
|
|
|
* Inaky Perez-Gonzalez <inaky.perez-gonzalez@intel.com>
|
|
|
|
*
|
|
|
|
* This implements a simple synchronous call to reset a WiMAX device.
|
|
|
|
*
|
|
|
|
* Resets aim at being warm, keeping the device handles active;
|
|
|
|
* however, when that fails, it falls back to a cold reset (that will
|
|
|
|
* disconnect and reconnect the device).
|
|
|
|
*/
|
|
|
|
|
|
|
|
#include <net/wimax.h>
|
|
|
|
#include <net/genetlink.h>
|
|
|
|
#include <linux/wimax.h>
|
|
|
|
#include <linux/security.h>
|
2011-07-15 19:47:34 +04:00
|
|
|
#include <linux/export.h>
|
wimax: basic API: kernel/user messaging, rfkill and reset
Implements the three basic operations provided by the stack's control
interface to WiMAX devices:
- Messaging channel between user space and driver/device
This implements a direct communication channel between user space
and the driver/device, by which free form messages can be sent back
and forth.
This is intended for device-specific features, vendor quirks, etc.
- RF-kill framework integration
Provide most of the RF-Kill integration for WiMAX drivers so that
all device drivers have to do is after wimax_dev_add() is call
wimax_report_rfkill_{hw,sw}() to update initial state and then every
time it changes.
Provides wimax_rfkill() for the kernel to call to set software
RF-Kill status and/or query current hardware and software switch
status.
Exports wimax_rfkill() over generic netlink to user space.
- Reset a WiMAX device
Provides wimax_reset() for the kernel to reset a wimax device as
needed and exports it over generic netlink to user space.
This API is clearly limited, as it still provides no way to do the
basic scan, connect and disconnect in a hardware independent way. The
WiMAX case is more complex than WiFi due to the way networks are
discovered and provisioned.
The next developments are to add the basic operations so they can be
offerent by different drivers. However, we'd like to get more vendors
to jump in and provide feedback of how the user/kernel API/abstraction
layer should be.
The user space code for the i2400m, as of now, uses the messaging
channel, but that will change as the API evolves.
Signed-off-by: Inaky Perez-Gonzalez <inaky@linux.intel.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
2008-12-21 03:57:38 +03:00
|
|
|
#include "wimax-internal.h"
|
|
|
|
|
|
|
|
#define D_SUBMODULE op_reset
|
|
|
|
#include "debug-levels.h"
|
|
|
|
|
|
|
|
|
|
|
|
/**
|
|
|
|
* wimax_reset - Reset a WiMAX device
|
|
|
|
*
|
|
|
|
* @wimax_dev: WiMAX device descriptor
|
|
|
|
*
|
|
|
|
* Returns:
|
|
|
|
*
|
|
|
|
* %0 if ok and a warm reset was done (the device still exists in
|
|
|
|
* the system).
|
|
|
|
*
|
|
|
|
* -%ENODEV if a cold/bus reset had to be done (device has
|
|
|
|
* disconnected and reconnected, so current handle is not valid
|
|
|
|
* any more).
|
|
|
|
*
|
|
|
|
* -%EINVAL if the device is not even registered.
|
|
|
|
*
|
|
|
|
* Any other negative error code shall be considered as
|
|
|
|
* non-recoverable.
|
|
|
|
*
|
|
|
|
* Description:
|
|
|
|
*
|
|
|
|
* Called when wanting to reset the device for any reason. Device is
|
|
|
|
* taken back to power on status.
|
|
|
|
*
|
tree-wide: fix assorted typos all over the place
That is "success", "unknown", "through", "performance", "[re|un]mapping"
, "access", "default", "reasonable", "[con]currently", "temperature"
, "channel", "[un]used", "application", "example","hierarchy", "therefore"
, "[over|under]flow", "contiguous", "threshold", "enough" and others.
Signed-off-by: André Goddard Rosa <andre.goddard@gmail.com>
Signed-off-by: Jiri Kosina <jkosina@suse.cz>
2009-11-14 18:09:05 +03:00
|
|
|
* This call blocks; on successful return, the device has completed the
|
wimax: basic API: kernel/user messaging, rfkill and reset
Implements the three basic operations provided by the stack's control
interface to WiMAX devices:
- Messaging channel between user space and driver/device
This implements a direct communication channel between user space
and the driver/device, by which free form messages can be sent back
and forth.
This is intended for device-specific features, vendor quirks, etc.
- RF-kill framework integration
Provide most of the RF-Kill integration for WiMAX drivers so that
all device drivers have to do is after wimax_dev_add() is call
wimax_report_rfkill_{hw,sw}() to update initial state and then every
time it changes.
Provides wimax_rfkill() for the kernel to call to set software
RF-Kill status and/or query current hardware and software switch
status.
Exports wimax_rfkill() over generic netlink to user space.
- Reset a WiMAX device
Provides wimax_reset() for the kernel to reset a wimax device as
needed and exports it over generic netlink to user space.
This API is clearly limited, as it still provides no way to do the
basic scan, connect and disconnect in a hardware independent way. The
WiMAX case is more complex than WiFi due to the way networks are
discovered and provisioned.
The next developments are to add the basic operations so they can be
offerent by different drivers. However, we'd like to get more vendors
to jump in and provide feedback of how the user/kernel API/abstraction
layer should be.
The user space code for the i2400m, as of now, uses the messaging
channel, but that will change as the API evolves.
Signed-off-by: Inaky Perez-Gonzalez <inaky@linux.intel.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
2008-12-21 03:57:38 +03:00
|
|
|
* reset process and is ready to operate.
|
|
|
|
*/
|
|
|
|
int wimax_reset(struct wimax_dev *wimax_dev)
|
|
|
|
{
|
|
|
|
int result = -EINVAL;
|
|
|
|
struct device *dev = wimax_dev_to_dev(wimax_dev);
|
|
|
|
enum wimax_st state;
|
|
|
|
|
|
|
|
might_sleep();
|
|
|
|
d_fnstart(3, dev, "(wimax_dev %p)\n", wimax_dev);
|
|
|
|
mutex_lock(&wimax_dev->mutex);
|
|
|
|
dev_hold(wimax_dev->net_dev);
|
|
|
|
state = wimax_dev->state;
|
|
|
|
mutex_unlock(&wimax_dev->mutex);
|
|
|
|
|
|
|
|
if (state >= WIMAX_ST_DOWN) {
|
|
|
|
mutex_lock(&wimax_dev->mutex_reset);
|
|
|
|
result = wimax_dev->op_reset(wimax_dev);
|
|
|
|
mutex_unlock(&wimax_dev->mutex_reset);
|
|
|
|
}
|
|
|
|
dev_put(wimax_dev->net_dev);
|
|
|
|
|
|
|
|
d_fnend(3, dev, "(wimax_dev %p) = %d\n", wimax_dev, result);
|
|
|
|
return result;
|
|
|
|
}
|
|
|
|
EXPORT_SYMBOL(wimax_reset);
|
|
|
|
|
|
|
|
|
|
|
|
/*
|
|
|
|
* Exporting to user space over generic netlink
|
|
|
|
*
|
|
|
|
* Parse the reset command from user space, return error code.
|
|
|
|
*
|
|
|
|
* No attributes.
|
|
|
|
*/
|
|
|
|
int wimax_gnl_doit_reset(struct sk_buff *skb, struct genl_info *info)
|
|
|
|
{
|
|
|
|
int result, ifindex;
|
|
|
|
struct wimax_dev *wimax_dev;
|
|
|
|
|
|
|
|
d_fnstart(3, NULL, "(skb %p info %p)\n", skb, info);
|
|
|
|
result = -ENODEV;
|
|
|
|
if (info->attrs[WIMAX_GNL_RESET_IFIDX] == NULL) {
|
2014-10-08 00:12:03 +04:00
|
|
|
pr_err("WIMAX_GNL_OP_RFKILL: can't find IFIDX attribute\n");
|
wimax: basic API: kernel/user messaging, rfkill and reset
Implements the three basic operations provided by the stack's control
interface to WiMAX devices:
- Messaging channel between user space and driver/device
This implements a direct communication channel between user space
and the driver/device, by which free form messages can be sent back
and forth.
This is intended for device-specific features, vendor quirks, etc.
- RF-kill framework integration
Provide most of the RF-Kill integration for WiMAX drivers so that
all device drivers have to do is after wimax_dev_add() is call
wimax_report_rfkill_{hw,sw}() to update initial state and then every
time it changes.
Provides wimax_rfkill() for the kernel to call to set software
RF-Kill status and/or query current hardware and software switch
status.
Exports wimax_rfkill() over generic netlink to user space.
- Reset a WiMAX device
Provides wimax_reset() for the kernel to reset a wimax device as
needed and exports it over generic netlink to user space.
This API is clearly limited, as it still provides no way to do the
basic scan, connect and disconnect in a hardware independent way. The
WiMAX case is more complex than WiFi due to the way networks are
discovered and provisioned.
The next developments are to add the basic operations so they can be
offerent by different drivers. However, we'd like to get more vendors
to jump in and provide feedback of how the user/kernel API/abstraction
layer should be.
The user space code for the i2400m, as of now, uses the messaging
channel, but that will change as the API evolves.
Signed-off-by: Inaky Perez-Gonzalez <inaky@linux.intel.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
2008-12-21 03:57:38 +03:00
|
|
|
goto error_no_wimax_dev;
|
|
|
|
}
|
|
|
|
ifindex = nla_get_u32(info->attrs[WIMAX_GNL_RESET_IFIDX]);
|
|
|
|
wimax_dev = wimax_dev_get_by_genl_info(info, ifindex);
|
|
|
|
if (wimax_dev == NULL)
|
|
|
|
goto error_no_wimax_dev;
|
|
|
|
/* Execute the operation and send the result back to user space */
|
|
|
|
result = wimax_reset(wimax_dev);
|
|
|
|
dev_put(wimax_dev->net_dev);
|
|
|
|
error_no_wimax_dev:
|
|
|
|
d_fnend(3, NULL, "(skb %p info %p) = %d\n", skb, info, result);
|
|
|
|
return result;
|
|
|
|
}
|