- 09 Jul, 2012 40 commits
-
-
Samuel Ortiz authored
When the MAC link goes down, we should only keep the bound sockets alive. They will be closed by sock_release or when the underlying NFC device is moving away. Signed-off-by:Samuel Ortiz <sameo@linux.intel.com>
-
Samuel Ortiz authored
Drivers will need them before starting a poll or when being activated as targets. Mostly WKS can have changed between device registration and then so we need to re-build the whole array. Signed-off-by: -
Samuel Ortiz authored
Set the right target index and use a better socket declaration routine. Signed-off-by: -
Samuel Ortiz authored
Getting a valid CONNECT means we have a valid target index. Signed-off-by: -
Samuel Ortiz authored
Signed-off-by: -
Samuel Ortiz authored
Signed-off-by: -
Eric Lapuyade authored
Some NFC chips will statically create and open pipes for both standard and proprietary gates. The driver can now pass this information to HCI such that HCI will not attempt to create and open them, but will instead directly use the passed pipe ids. Signed-off-by:
Eric Lapuyade <eric.lapuyade@intel.com> Signed-off-by:
-
Eric Lapuyade authored
Signed-off-by:
-
Eric Lapuyade authored
Signed-off-by:
-
Eric Lapuyade authored
If the device is polling we sent a 0 target found event. Signed-off-by:
-
Eric Lapuyade authored
The semantics for a zero target found event is that the polling operation could not complete. Signed-off-by:
-
Eric Lapuyade authored
There can ever be only one call to nfc_targets_found() after polling has been engaged. This could be from a target discovered event from the driver, or from an error handler to notify poll will never complete. Signed-off-by:
-
Eric Lapuyade authored
If there is an ongoing HCI command executing, it will be completed, thereby pushing the error up to the core. Otherwise, HCI will directly notify the core with the error. Signed-off-by:
-
Eric Lapuyade authored
HCI cmd can be completed either from an HCI response or from an internal driver or HCI error. This requires to factorize the completion code outside of the device lock. Signed-off-by:
-
Eric Lapuyade authored
This API should be used by drivers, HCI, SHDLC or NCI stacks to report an unrecoverable error. Signed-off-by:
-
Eric Lapuyade authored
An HCI command can complete either from an HCI response (with an HCI result) or as a consequence of any other system error during processing. The completion therefore needs to take a standard errno code. The HCI response will convert its result to a standard errno before calling the completion. Signed-off-by:
-
Eric Lapuyade authored
We can now report an ENOMEM error up to the HCI layer. Signed-off-by:
-
Eric Lapuyade authored
nfc_hci_recv_frame can not be called with a NULL skb. Signed-off-by:
-
Eric Lapuyade authored
shdlc reset may leave HCI in an inconsistent state by loosing parts of HCI frames. Handle this case by reporting an unrecoverable error to HCI. Signed-off-by:
-
Eric Lapuyade authored
The questions asked in the comments have been answered and addressed. Signed-off-by:
-
Eric Lapuyade authored
Signed-off-by:
-
Mohammed Shafi Shajakhan authored
Its safe to stop the BTCOEX timers 'period_timer' and 'no_stomp_timer' before disabling BTCOEX. These timers can call ath9k_hw_btcoex_enable (or) change the BT stomp type if they seem to be running after we had called ath9k_hw_btcoex_disable, which is obviously not correct. Cc: Rajkumar Manoharan <rmanohar@qca.qualcomm.com> Cc: Bala Shanmugam <bkamatch@qca.qualcomm.com> Signed-off-by:
Mohammed Shafi Shajakhan <mohammed@qca.qualcomm.com> Signed-off-by:
John W. Linville <linville@tuxdriver.com>
-
Mohammed Shafi Shajakhan authored
We are doing MCI cleanup eventhough BTCOEX is not enabled via module parameter. This means we do ath_mci_cleanup though we skipped calling ath_mci_setup. Yet it does not causes any issues now as we free the DMA buffer allocated only when it is allocated during ath_mci_setup. Reviewed-by:
Bala Shanmugam <bkamatch@qca.qualcomm.com> Signed-off-by:
-
Rafał Miłecki authored
Having bus number printed makes it much easier to anaylze logs on systems with more buses. For example Netgear WNDR4500 has 3 AMBA buses in total, which makes standard log really messy. Signed-off-by:
Rafał Miłecki <zajec5@gmail.com> Signed-off-by:
-
Rafał Miłecki authored
Specs were updated, change code to match it. Signed-off-by:
-
Arend van Spriel authored
This patch fixes an OOPS in brcmsmac driver, which was introduced by the 11ad patch 'cfg80211: add 802.11ad (60gHz band) support'. The value IEEE80211_NUM_BANDS increased, which was used in the brcms_c_regd_init() function. Cc: Vladimir Kondratiev <qca_vkondrat@qca.qualcomm.com> Cc: Johannes Berg <johannes.berg@intel.com> Acked-by:
Seth Forshee <seth.forshee@canonical.com> Signed-off-by:
Arend van Spriel <arend@broadcom.com> Signed-off-by:
-
Gabor Juhos authored
Signed-off-by:
Gabor Juhos <juhosg@openwrt.org> Acked-by:
Luis R. Rodriguez <mcgrof@qca.qualcomm.com> Signed-off-by:
-
Gabor Juhos authored
Signed-off-by:
-
Gabor Juhos authored
Signed-off-by:
-
Gabor Juhos authored
Signed-off-by:
-
Gabor Juhos authored
Signed-off-by:
-
Gabor Juhos authored
Signed-off-by:
-
Gabor Juhos authored
Signed-off-by:
-
Gabor Juhos authored
Signed-off-by:
-
Gabor Juhos authored
Signed-off-by:
-
Gabor Juhos authored
Signed-off-by:
-
Gabor Juhos authored
Signed-off-by:
-
Gabor Juhos authored
Signed-off-by:
-
Gabor Juhos authored
Signed-off-by:
-
Gabor Juhos authored
Signed-off-by:
-
