Return-path: Received: from mail-pf0-f182.google.com ([209.85.192.182]:33697 "EHLO mail-pf0-f182.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750948AbcEIJLS (ORCPT ); Mon, 9 May 2016 05:11:18 -0400 Received: by mail-pf0-f182.google.com with SMTP id 206so74433651pfu.0 for ; Mon, 09 May 2016 02:11:18 -0700 (PDT) Subject: Re: [PATCH] Fix regression in Android due to rework .get_station() callback To: Kalle Valo , Jaap Jan Meijer References: <1462280620-13000-1-git-send-email-jjmeijer88@gmail.com> <87poszs8tc.fsf@kamboji.qca.qualcomm.com> <87wpn7p6dv.fsf@kamboji.qca.qualcomm.com> <87futvp432.fsf@kamboji.qca.qualcomm.com> Cc: linux-wireless@vger.kernel.org, brcm80211-dev-list@broadcom.com From: Arend Van Spriel Message-ID: <5730542C.8020201@broadcom.com> (sfid-20160509_111122_367335_57CD2648) Date: Mon, 9 May 2016 11:11:08 +0200 MIME-Version: 1.0 In-Reply-To: <87futvp432.fsf@kamboji.qca.qualcomm.com> Content-Type: text/plain; charset=windows-1252 Sender: linux-wireless-owner@vger.kernel.org List-ID: On 6-5-2016 18:02, Kalle Valo wrote: > Jaap Jan Meijer writes: > >> 2016-05-06 16:12 GMT+01:00 Kalle Valo : >>> Jaap Jan Meijer writes: >>> >>>> Hi Kalle, >>>> >>>> Op vr 6 mei 2016 12:52 schreef Kalle Valo : >>>> >>>> >>>> This has multiple issues: >>>> >>>> o Use your full name. >>>> o Use prefix "brcmfmac: " in the title. >>>> >>>> o I can't find commit f654d13, is the commit id really correct? >>>> o Also check from SubmittingPatches how you should reference commit ids. >>>> >>>> >>>> >>>> Thank you for the feedback, I will send a reworked patch as soon as I get home >>>> next week. Also I did this against v4.4.8 so I'll have to rebase it as well. >>>> >>>> I'm not sure what went wrong with the commit hash, its actually this commit: >>>> 1f0dc59a6de93586fcfc04696a61946408ffc56a. >>> >>> That commit id looks to be valid. >>> >>>> I see you did this commit, maybe you can check if this actually is the root >>>> cause? I'm sure you have a lot more insight into this issue than I do. > > I just commited the patch. Broadcom folks (CCed) should be able to > answer better, most likely they missed this patch as the title didn't > have "brcmfmac". Hi Kalle, I did see the patch and noticed the procedural issues as well. However, last week was a short week over here and I did not get to it to respond. The fix is not done properly. The function determines the RSSI from the per-chain values. I suspect that Jaap Jan is using a device which does not report per-chain values so his solution should be used as fallback. So can you revert the patch so Jaap Jan can rework the patch, ie.: if (count_rssi) { : } else if (test_bit(BRCMF_VIF_STATUS_CONNECTED, &ifp->vif->sme_state)) { memset(&scb_val, 0, sizeof(scb_val)); err = brcmf_fil_cmd_data_get(ifp, BRCMF_C_GET_RSSI, &scb_val, sizeof(scb_val)); if (err) { brcmf_err("Could not get rssi (%d)\n", err); goto done; } else { rssi = le32_to_cpu(scb_val.val); sinfo->filled |= BIT(NL80211_STA_INFO_SIGNAL); sinfo->signal = rssi; brcmf_dbg(CONN, "RSSI %d dBm\n", rssi); } } Let me know if that is ok or should I submit a fixup patch. Regards, Arend