Hi Bob,
On 2015/11/9 23:40, Bob Copeland wrote:
On Mon, Nov 09, 2015 at 05:02:41AM -0500, Yin, Fengwei wrote:
From: Andy Green <andy.green@xxxxxxxxxx>
From: Andy Green <andy.green@xxxxxxxxxx>
On wcn3620, firmware response to trigger_ba uses the new, larger
"v2" format
- ret = wcn36xx_smd_rsp_status_check(wcn->hal_buf, wcn->hal_rsp_len);
+ ret = wcn36xx_smd_rsp_status_check_v2(wcn, wcn->hal_buf,
+ wcn->hal_rsp_len);
It's unclear from the changelog -- is it safe to call
wcn36xx_smd_rsp_status_check_v2 on the 3660/3680 as well?
Is wcn36xx_smd_rsp_status_check() still needed?
Even on 3620, not all cmds switch to wcn36xx_smd_rsp_status_check_v2.
And I don't think wcn36xx_smd_rsp_status_check_v2 should bind to 3620 (it
may be related with firmware).
In patch v2, the wcn36xx_smd_rsp_status_check_v2 is not bind to 3620. If
you could test on none-3620 platform (I don't have none-3620 plafrom), that
will be great.
I will send out patch v2 soon which drive the build error and the comments
from you. Thanks a lot for reviewing.
Regards
Yin, Fengwei
--
To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
