{"push_id":633472397,"size":19,"distinct_size":14,"ref":"refs/heads/pending","head":"e406ef5c2eb34779e704ab624d08e22905f49461","before":"abe24efb9bc1d613b4e39202425cc79bc3170630","commits":[{"sha":"694c0e0a177783ebf302f462237daa1e2f254025","author":{"email":"2f655c9759e57674d0e5bb5678ad791bc0e5d3ad@qca.qualcomm.com","name":"Peter Oh"},"message":"ath: support new FCC DFS Radar Type 1\n\nAdd support for new FCC DFS rules released on August 14, 2014.\nFCC has added a new radar type named Radar Type 1 and original\nRadar Type 1 is renamed to Radar Type 0 in consequence.\n\nDuring the certificate test, Type 1 PRI values are randomly selected\nwithin the range of 518 and 3066 and we divide it to 3 groups based on\npractical test result data collected for more than a year.\n\nFor about Radar type ID, it does nothing to functionalities.\nIn other words, even if we re-order the IDs, DFS detection will\nwork as well, but we give the ID with matching to FCC doc.\n\nBy adding this support, the drivers using this DFS function are\nable to support both of old and new FCC DFS rules simultaneously\nwithout any other changes.\n\nSigned-off-by: Peter Oh <poh@qca.qualcomm.com>\nSigned-off-by: Kalle Valo <kvalo@qca.qualcomm.com>","distinct":false,"url":"https://api.github.com/repos/kvalo/ath/commits/694c0e0a177783ebf302f462237daa1e2f254025"},{"sha":"fcf9844636be1674a565afcdf6901e1cf37f09fb","author":{"email":"956a8aa249cc11dbf2733fc41294eabd5c99981c@tieto.com","name":"Michal Kazior"},"message":"ath10k: fix hw roc expiration\n\nIt is not guaranteed firmware will switch to\nforeign channel immediately after starting scan\nsequence. To account for that don't use duration\nparameter for scan time. Instead request insanely\nlong scan and use timeout worker to cancel it from\ndriver.\n\nThis should improve P2P reliability a bit.\n\nSigned-off-by: Michal Kazior <michal.kazior@tieto.com>\nSigned-off-by: Kalle Valo <kvalo@qca.qualcomm.com>","distinct":false,"url":"https://api.github.com/repos/kvalo/ath/commits/fcf9844636be1674a565afcdf6901e1cf37f09fb"},{"sha":"dbd3f9f37ed217653ffe46368766a8fcdca5fcfb","author":{"email":"956a8aa249cc11dbf2733fc41294eabd5c99981c@tieto.com","name":"Michal Kazior"},"message":"ath10k: use scan burst for hw roc\n\nThis improves chances of getting onto a foreign\nchannel and thus makes P2P a bit more reliable.\n\nWithout scan burst it was possible for firmware to\nnot switch to foreign channel resulting in \"failed\nto switch to channel for roc scan\" warning. This\nwould also effectively fail some offchan tx\nrequests and lead to P2P find/connect taking\nlonger. This could be observed when other vifs\nwere running/busy, e.g. with P2P GO.\n\nSigned-off-by: Michal Kazior <michal.kazior@tieto.com>\nSigned-off-by: Kalle Valo <kvalo@qca.qualcomm.com>","distinct":false,"url":"https://api.github.com/repos/kvalo/ath/commits/dbd3f9f37ed217653ffe46368766a8fcdca5fcfb"},{"sha":"cb3fbd63575cca6cff60222b5a51cc3bebe866ee","author":{"email":"2f655c9759e57674d0e5bb5678ad791bc0e5d3ad@qca.qualcomm.com","name":"Peter Oh"},"message":"ath: define JP DFS patterns separated from FCC\n\nSeparate Japan's DFS pattern from FCC to control PPB threshold.\n\nCurrently all the radar detectors use the same threshold rate at\n50%, but it's not able to achieve if data traffic rate is higher\nthan 40% because WLAN baseband used by ath9k and ath10k often fails\ndetecting radar pulses, so that SW cannot get enough radar reports\nto achieve the rate.\n\nSince Japan's W53 band requires 50% data traffic during its DFS\ntest we need to apply different threshold rate than others on it.\nHence define its own pattern to give flexibility to threshold rate.\n\nSigned-off-by: Peter Oh <poh@qca.qualcomm.com>\nSigned-off-by: Kalle Valo <kvalo@qca.qualcomm.com>","distinct":false,"url":"https://api.github.com/repos/kvalo/ath/commits/cb3fbd63575cca6cff60222b5a51cc3bebe866ee"},{"sha":"26bea13a65654b21b224a47daf02827c79302f2e","author":{"email":"2f655c9759e57674d0e5bb5678ad791bc0e5d3ad@qca.qualcomm.com","name":"Peter Oh"},"message":"ath: lower JP W53 band DFS detection threshold around 30%\n\nJapan's W53 band requires 50% data traffic during its DFS test,\nbut WLAN baseband used by ath9k and ath10k is not able to achieve\ncurrent threshold rate, 50%, under the data traffic rate.\nIn other words, HW occasionally fails detecting radar pulses,\nso that SW cannot get enough radar reports to achieve the rate.\n\nSigned-off-by: Peter Oh <poh@qca.qualcomm.com>\nSigned-off-by: Kalle Valo <kvalo@qca.qualcomm.com>","distinct":false,"url":"https://api.github.com/repos/kvalo/ath/commits/26bea13a65654b21b224a47daf02827c79302f2e"},{"sha":"6a70766667915917f5e8defa8bd270bd7b78d7bf","author":{"email":"956a8aa249cc11dbf2733fc41294eabd5c99981c@tieto.com","name":"Michal Kazior"},"message":"ath10k: share board file loading code across FW APIs\n\nThere's no need to implement the same thing twice.\nReduce code duplication.\n\nSigned-off-by: Michal Kazior <michal.kazior@tieto.com>\nSigned-off-by: Kalle Valo <kvalo@qca.qualcomm.com>","distinct":true,"url":"https://api.github.com/repos/kvalo/ath/commits/6a70766667915917f5e8defa8bd270bd7b78d7bf"},{"sha":"9951f2cf227d961b95fe9e1dfe40df5098123b95","author":{"email":"956a8aa249cc11dbf2733fc41294eabd5c99981c@tieto.com","name":"Michal Kazior"},"message":"ath10k: allow loading device specific board files\n\nSome devices differ slightly and require different\nboard files. These devices can be differentiated\nby looking at PCI subsystem device id. That is the\ncase for qca6174 devices at least.\n\nUse that and load subsystem id specific board\nfiles if possible. Otherwise fall back to use the\n(old) generic board file path.\n\nUsing wrong board data may cause device crashes or\ninvalid behaviour (wrong tx power, garbled RF\nsignal).\n\nSigned-off-by: Michal Kazior <michal.kazior@tieto.com>\nSigned-off-by: Kalle Valo <kvalo@qca.qualcomm.com>","distinct":true,"url":"https://api.github.com/repos/kvalo/ath/commits/9951f2cf227d961b95fe9e1dfe40df5098123b95"},{"sha":"281bf9997bae55fae9e0f0c6805b9da8e932976a","author":{"email":"2f655c9759e57674d0e5bb5678ad791bc0e5d3ad@qca.qualcomm.com","name":"Peter Oh"},"message":"ath: use PRI value given by spec for fixed PRI\n\nPRI value is used as divider when DFS detector analyzes candidate\nradar pulses.\nIf PRI deviation is big from its origin PRI, DFS detector could miss\nvalid radar reports since HW often misses detecting radar pulses and\ncauses long interval value of pulses.\n\nFor instance from practical results, if runtime PRI is calculated as\n1431 for fixed PRI value of 1428 and delta timestamp logs 15719,\nthe modular remainder will be 1409 and the delta between the remainder\nand runtime PRI is 22 that is bigger than PRI tolerance which is 16.\nAs a result this radar report will be ignored even though it's valid.\n\nBy using spec defined PRI for fixed PRI, we can correct this error.\n\nSigned-off-by: Peter Oh <poh@qca.qualcomm.com>\nSigned-off-by: Kalle Valo <kvalo@qca.qualcomm.com>","distinct":true,"url":"https://api.github.com/repos/kvalo/ath/commits/281bf9997bae55fae9e0f0c6805b9da8e932976a"},{"sha":"6f1da4ec3be983f9663755b4e36fd98c7167c1a4","author":{"email":"956a8aa249cc11dbf2733fc41294eabd5c99981c@tieto.com","name":"Michal Kazior"},"message":"ath10k: fix error handling in pci_probe\n\nIf chip_id wasn't recognized clean up code wasn't\nexecuted properly. It would skip freeing memory\ncausing a leak and irqs causing possibly MSI\nwarning splats later or even kernel crashes.\n\nFixes: 1a7fecb766c8 (\"ath10k: reset chip before reading chip_id in probe\")\nSigned-off-by: Michal Kazior <michal.kazior@tieto.com>\nSigned-off-by: Kalle Valo <kvalo@qca.qualcomm.com>","distinct":true,"url":"https://api.github.com/repos/kvalo/ath/commits/6f1da4ec3be983f9663755b4e36fd98c7167c1a4"},{"sha":"221b81bdb0567c8923fce77be989e12feabb5a0c","author":{"email":"956a8aa249cc11dbf2733fc41294eabd5c99981c@tieto.com","name":"Michal Kazior"},"message":"ath10k: add extra check for frame tracing\n\nFrames are logged via tracing in two slices:\nheader and payload, separately. This is done for\nperformance reasons when one wants to, e.g.\nanalyse metadata only of frames only.\n\nIf for some reason device delivered a frame buffer\nwhich was sized below what 802.11 header implied\ntracing logic would blow doing an invalid memory\naccesses.\n\nI've hit this problem when running IBSS on QCA988X\nwith 999.999.0.636 and tracing at the same time.\n\nFixes: 5ce8e7fdcc7a (\"ath10k: handle ieee80211 header and payload tracing separately\")\nSigned-off-by: Michal Kazior <michal.kazior@tieto.com>\nSigned-off-by: Kalle Valo <kvalo@qca.qualcomm.com>","distinct":true,"url":"https://api.github.com/repos/kvalo/ath/commits/221b81bdb0567c8923fce77be989e12feabb5a0c"},{"sha":"35f780ed224ef70356fedbf54bc04051bdf2292c","author":{"email":"956a8aa249cc11dbf2733fc41294eabd5c99981c@tieto.com","name":"Michal Kazior"},"message":"ath10k: change static wep key handling for client mode\n\nmac80211 sets static WEP keys as groupwise while\nfirmware requires them to be installed twice as\nboth pairwise and groupwise.\n\nUntil now these keys were installed once as\npairwise only and, due to that special handling,\nneeded additional tricks to support 802.1x as\nwell.\n\nWithout this patch in some cases (when AP and\nath10k client use different default tx keys)\nmulticast communication was broken.\n\nSigned-off-by: Michal Kazior <michal.kazior@tieto.com>\nSigned-off-by: Kalle Valo <kvalo@qca.qualcomm.com>","distinct":true,"url":"https://api.github.com/repos/kvalo/ath/commits/35f780ed224ef70356fedbf54bc04051bdf2292c"},{"sha":"048e9c6909e565a61011442e84679c4fb23963c5","author":{"email":"956a8aa249cc11dbf2733fc41294eabd5c99981c@tieto.com","name":"Michal Kazior"},"message":"ath10k: don't use reassoc flag\n\nFirmware actually re-creates peer entry when\nreassoc flag is set. This is undesired and could\ncause trouble with IBSS crypto-wise. This is also\nimportant for upcomming bitrate mask improvement.\n\nSigned-off-by: Michal Kazior <michal.kazior@tieto.com>\nSigned-off-by: Kalle Valo <kvalo@qca.qualcomm.com>","distinct":true,"url":"https://api.github.com/repos/kvalo/ath/commits/048e9c6909e565a61011442e84679c4fb23963c5"},{"sha":"5a7e2e642e1b00ed92240c1dec7923cb7c7908bd","author":{"email":"956a8aa249cc11dbf2733fc41294eabd5c99981c@tieto.com","name":"Michal Kazior"},"message":"ath10k: fix multiple key static wep with ibss\n\nApparently firmware requires both pairwise and\ngroupwise keys to be installed per-peer for static\nWEP in IBSS. This wasn't necessary for AP mode\n(and installing both doesn't seem to break AP\nmode thus there's no special handling).\n\nAlso there seems to be some kind of issue with\nmapping tx/rx keys in firmware properly which\nresulted in wrong keys being used and broken\ncommunication between devices.\n\nIt can be argued the vdev param part is more of a\nworkaround than a real fix. However I couldn't\nfigure out how to fix this differently. It works\nand isn't super ugly.\n\nSigned-off-by: Michal Kazior <michal.kazior@tieto.com>\nSigned-off-by: Kalle Valo <kvalo@qca.qualcomm.com>","distinct":true,"url":"https://api.github.com/repos/kvalo/ath/commits/5a7e2e642e1b00ed92240c1dec7923cb7c7908bd"},{"sha":"ab47e4d1b0f6841631c094f53ca2bba57851a744","author":{"email":"956a8aa249cc11dbf2733fc41294eabd5c99981c@tieto.com","name":"Michal Kazior"},"message":"ath10k: set def key idx for ibss\n\nSome time ago there was a weird issue with AP\nusing wrong multicast keys and generating\ncorrupted traffic on 10.1 firmware.\n\nApparently a very similar problem applies for\nIBSS-RSN on 999.999.0.636.\n\nath10k doesn't have IBSS-RSN enabled yet. This\npatch is a prerequisite to support it.\n\nSigned-off-by: Michal Kazior <michal.kazior@tieto.com>\nSigned-off-by: Kalle Valo <kvalo@qca.qualcomm.com>","distinct":true,"url":"https://api.github.com/repos/kvalo/ath/commits/ab47e4d1b0f6841631c094f53ca2bba57851a744"},{"sha":"3d1653d32895cf7ede6c4ee94e4b2ba7abcc7b3e","author":{"email":"a4201e08a607951e17dcd5a575c0fe6bceb34e87@tieto.com","name":"Janusz Dziedzic"},"message":"ath10k: enable ibss-rsn\n\nWith latest additions to the driver it seems\nviable to enable support for IBSS-RSN.\n\nIt seems to work on QCA988X and 999.999.0.636 but\nis a bit slow to exchange RSN keys for some\nreason. This may be a firmware quirk or ath10k is\nmissing something. Nevertheless it makes sense to\nfinally enable IBSS-RSN in ath10k even if somewhat\nhandicapped.\n\nQCA6174 firmware doesn't seem to be able to Tx\nEAPOL frames at all now (they get stuck in hw\nqueues for some reason) so it never gets to set\nthe keys in driver. It's fairly safe to assume that\nonce this is fixed IBSS-RSN will work with QCA6174\nfirmware without any additional changes. Hence no\nspecial handling for advertising\nIEEE80211_HW_SUPPORTS_PER_STA_GTK and\nWIPHY_FLAG_IBSS_RSN is done now.\n\nSigned-off-by: Janusz Dziedzic <janusz.dziedzic@tieto.com>\nSigned-off-by: Michal Kazior <michal.kazior@tieto.com>\nSigned-off-by: Kalle Valo <kvalo@qca.qualcomm.com>","distinct":true,"url":"https://api.github.com/repos/kvalo/ath/commits/3d1653d32895cf7ede6c4ee94e4b2ba7abcc7b3e"},{"sha":"7be4f2df8af0a3c1014a6c47c184def93ebf2061","author":{"email":"956a8aa249cc11dbf2733fc41294eabd5c99981c@tieto.com","name":"Michal Kazior"},"message":"ath10k: implement more versatile set_bitrate_mask\n\nUntil now only a single fixed tx rate or nss was\nallowed to be set.\n\nThe patch attempts to improve this by allowing\nmost bitrate masks. The limitation is VHT MCS\nrates cannot be expressed separately using\nexisting firmware interfaces and only the\nfollowing VHT MCS ranges are supported: none, 0-7,\n0-8, and 0-9.\n\nThis keeps the old behaviour when requesting\nsingle tx rate or single nss. The new bitrate mask\nlogic is only applied to other cases that would\nreturn -EINVAL until now.\n\nDepending on firmware revisions some combinations\nmay crash firmware so use with care, please.\n\nThis depends on \"ath10k: don't use reassoc flag\".\nWithout it key cache would effectively be\ninvalidated upon bitrate change leading to\ncommunication being no longer possible.\n\nSigned-off-by: Michal Kazior <michal.kazior@tieto.com>\nSigned-off-by: Kalle Valo <kvalo@qca.qualcomm.com>","distinct":true,"url":"https://api.github.com/repos/kvalo/ath/commits/7be4f2df8af0a3c1014a6c47c184def93ebf2061"},{"sha":"9fd8309cbb040c4d9fa02b0cd6eee7fcb846b0d1","author":{"email":"2f655c9759e57674d0e5bb5678ad791bc0e5d3ad@qca.qualcomm.com","name":"Peter Oh"},"message":"ath10k: use MAC clock rate same as FW uses for survey accuracy\n\nWLAN survey data provides several informative values on each channels\nsuch as noise, active time, transmit time, and etc.\nRegarding the channel activity time data, it is reported from firmware\nin different form which is number of cycles instead of time itself.\nHence host driver converts it to time unit by dividing it by clock rate\nthat is used at baseband MAC.\n\nUsing difference clock rate from that actual HW is using will result in\ninaccurate survey data. For instance, channel active time can be reported\nwith bigger than 150ms even though we set Dwell time to 150ms.\nTherefore set the clock rate to 88000 (88 MHz) which is ath10k baseband\nMAC is using.\n\nSigned-off-by: Peter Oh <poh@qca.qualcomm.com>\nSigned-off-by: Kalle Valo <kvalo@qca.qualcomm.com>","distinct":true,"url":"https://api.github.com/repos/kvalo/ath/commits/9fd8309cbb040c4d9fa02b0cd6eee7fcb846b0d1"},{"sha":"c62671fb546ef9e00ac628962ba4875cb351b748","author":{"email":"803f7f688a905c0e1de11b59c6c49015cb8da318@qca.qualcomm.com","name":"Yanbo Li"},"message":"ath10k: Add the WMI Air Time Fairness service define\n\nAdd the FW ATF (Air Time Fairness) service define to keep consistent\nwith 10.2 FW capability\n\nSigned-off-by: Yanbo Li <yanbol@qca.qualcomm.com>\nSigned-off-by: Kalle Valo <kvalo@qca.qualcomm.com>","distinct":true,"url":"https://api.github.com/repos/kvalo/ath/commits/c62671fb546ef9e00ac628962ba4875cb351b748"},{"sha":"e406ef5c2eb34779e704ab624d08e22905f49461","author":{"email":"803f7f688a905c0e1de11b59c6c49015cb8da318@qca.qualcomm.com","name":"Yanbo Li"},"message":"ath10k: Enable the BT-coex feature\n\nThe new 10.2.4 FW support the BT-coex feature with external BT module,\nThe external BT modules can communicate with it via the GPIO. This patch\ncheck the BT-coex capability of the FW and enable it by default.\n\nSigned-off-by: Yanbo Li <yanbol@qca.qualcomm.com>\nSigned-off-by: Kalle Valo <kvalo@qca.qualcomm.com>","distinct":true,"url":"https://api.github.com/repos/kvalo/ath/commits/e406ef5c2eb34779e704ab624d08e22905f49461"}]}