{"shas":[["92ecbff48e3993ca58525533dc58ec1025c45609","771765c27e4a0a8dc00f0c2f551d06e8bc1a9ada@chromium.org","ath6kl: query device tree for firmware board-id\n\nWhen no default board data file is present query the device tree for a\nboard-id setting to identify the board data to use.  If the FDT lacks the\nnecesary info fall back to the previous behaviour of using a compile-time\nboard filename.\n\nSigned-off-by: Sam Leffler <sleffler@chromium.org>\nSigned-off-by: Kalle Valo <kvalo@qca.qualcomm.com>","Sam Leffler"],["772c31ee438e4d2d7a5e049b8d73c2ee8902f656","7081a7d99b8c74c0698a728df19e3915a995d7e1@qca.qualcomm.com","ath6kl: separate firmware fetch from upload\n\nIn preparation for the new firmware image format.\n\nSigned-off-by: Kalle Valo <kvalo@qca.qualcomm.com>","Kalle Valo"],["cfc301edfb4f762309b5704ae316ea98d7ba1106","7081a7d99b8c74c0698a728df19e3915a995d7e1@qca.qualcomm.com","ath6kl: fix busy loop in ath6kl_bmi_get_rx_lkahd()\n\nBrent reported that ath6kl busy loops if firmware doesn't boot for some\nreason (in this case he was using an older firmware which wasn't supported\nby ath6kl).\n\nInvestigation revealed that this was even on purpose,\nath6kl_bmi_get_rx_lkahd() had a parameter to disable the timeout check,\nwhich is extremely evil. I didn't find any reason why the timeout needs\nto be disabled so I just removed the feature. The function already busyloops\na maximum of one second if it doesn't get an answer, even that's too long.\nIf something takes longer than that a more friendly approach is needed.\n\nReported-by: Brent Taylor <btaylor1@motorolasolutions.com>\nSigned-off-by: Kalle Valo <kvalo@qca.qualcomm.com>","Kalle Valo"],["50d412346e49aee71b66d90dffb68f8d90ed35b2","7081a7d99b8c74c0698a728df19e3915a995d7e1@qca.qualcomm.com","ath6kl: add support for firmware API 2 format\n\nIn the new format all the format images are embedded into one file.\n\nSigned-off-by: Kalle Valo <kvalo@qca.qualcomm.com>","Kalle Valo"],["a01ac4144e7af80f8c1fd861dc5d280c5687c2a9","7081a7d99b8c74c0698a728df19e3915a995d7e1@qca.qualcomm.com","ath6kl: refactor firmware load address code\n\nCurrently the load address was calculated everytime when it was needed,\nand with a mess if clauses. Simplify this by adding a field to struct\nath6kl for each address and choose the address with simple switch\nstatements.\n\nAlso move the code just after target version is retrieved. That way it's\neasier to override the values later in the boot process.\n\nSigned-off-by: Kalle Valo <kvalo@qca.qualcomm.com>","Kalle Valo"],["991b27eaf937a67bb575a95be5c592d9b9109a84","7081a7d99b8c74c0698a728df19e3915a995d7e1@qca.qualcomm.com","ath6kl: refactor firmware ext data addr and reserved ram handling size\n\nLess if clauses this way and again easier to override the values.\n\nSigned-off-by: Kalle Valo <kvalo@qca.qualcomm.com>","Kalle Valo"],["639d0b8996aa5913402b846932d57a51a23a40c9","7081a7d99b8c74c0698a728df19e3915a995d7e1@qca.qualcomm.com","ath6kl: read firmware start address from hardware\n\nIt's actually possible to read the firmware start address from hardware,\nthat way there's no need to hardcode the address in hardware.\n\nThanks to Chilam Ng for the idea.\n\nSigned-off-by: Kalle Valo <kvalo@qca.qualcomm.com>","Kalle Valo"],["8a13748034e93b4134455ebf51e2fada8eb00aca","7081a7d99b8c74c0698a728df19e3915a995d7e1@qca.qualcomm.com","ath6kl: read reserved ram size from firmware file\n\nA new version of firmware needs different reserved ram size so read that\nfrom the firmware image.\n\nSigned-off-by: Kalle Valo <kvalo@qca.qualcomm.com>","Kalle Valo"],["97e0496d056726ab46e7e977315f2ab847b34209","7081a7d99b8c74c0698a728df19e3915a995d7e1@qca.qualcomm.com","ath6kl: add firmware capabilities support\n\nThe new firmware format includes capability bits which make it\npossible to check what features the firmware supports. Add infrastructure\nto read the capabilities. For now it only provides\nATH6KL_FW_CAPABILITY_HOST_P2P which is not even used anywhere yet, but that\nwill be added later.\n\nSigned-off-by: Kalle Valo <kvalo@qca.qualcomm.com>","Kalle Valo"],["ac59a2b285abbcec1ec487ef56dcc25c654853fb","fad83ef5273ec3c13c39984b66e16f59e1c4a510@qca.qualcomm.com","ath6kl: Remove auth type fall back in auto authentication mode\n\nTarget already tries with different authentication mechanism\nwhen authentication type is configured to NL80211_AUTHTYPE_AUTOMATIC.\nRemove this piece of code from driver. Having this code in driver\neven affects auto + WEP authentication in some cases.\n\nSigned-off-by: Vasanthakumar Thiagarajan <vthiagar@qca.qualcomm.com>\nSigned-off-by: Kalle Valo <kvalo@qca.qualcomm.com>","Vasanthakumar Thiagarajan"],["170826dd0d9fa71b648aa31ecb1e2973d777dbdb","fad83ef5273ec3c13c39984b66e16f59e1c4a510@qca.qualcomm.com","ath6kl: Set the sme_state to disconnected in disconnect() callback\n\nAfter a successful completion of disconnect() driver needs to set\nit's sme_state to SME_DISCONNECTED to be in sync with cfg80211\nstate.\n\nSigned-off-by: Vasanthakumar Thiagarajan <vthiagar@qca.qualcomm.com>\nSigned-off-by: Kalle Valo <kvalo@qca.qualcomm.com>","Vasanthakumar Thiagarajan"]],"ref":"refs/heads/ath6kl-next","size":11,"head":"170826dd0d9fa71b648aa31ecb1e2973d777dbdb","push_id":43174096}