From: "fengwei.yin" <fengwei.yin@linaro.org>
To: Bjorn Andersson <bjorn@kryo.se>, Bob Copeland <me@bobcopeland.com>
Cc: wcn36xx <wcn36xx@lists.infradead.org>,
Andy Green <andy.green@linaro.org>,
linux-wireless <linux-wireless@vger.kernel.org>,
Bjorn Andersson <bjorn.andersson@sonymobile.com>,
Eugene Krasnikov <k.eugene.e@gmail.com>
Subject: Re: [PATCH 4/5] wcn3620: use new response format for wcn3620 trigger_ba
Date: Thu, 12 Nov 2015 14:37:22 +0800 [thread overview]
Message-ID: <564433A2.1080407@linaro.org> (raw)
In-Reply-To: <CAJAp7OhJyj4qEU+quqs3RLr10FB1D+XUCsSsH04DaQ8bVWsd_A@mail.gmail.com>
Hi Bjorn,
On 2015/11/12 12:50, Bjorn Andersson wrote:
> On Mon, Nov 9, 2015 at 7:40 AM, Bob Copeland <me@bobcopeland.com> wrote:
>> On Mon, Nov 09, 2015 at 05:02:41AM -0500, Yin, Fengwei wrote:
>>> From: Andy Green <andy.green@linaro.org>
>>>
>>> From: Andy Green <andy.green@linaro.org>
>>>
>>> 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?
>>
>
> I had to introduce this on one of my 3680 devices recently to silence
> the error described originally by Andy. So it not only seems safe but
> seems required. But still, based on how the code was written this
> doesn't seem to be the case on all versions of the firmware or all
> chips(?)
>
Thanks for the information. It confirm my thought that the change sticks
to new firmware instead of specific platform.
But we couldn't tell which version of firmware need this new format. Andy's
original change has two conditions to use the new format:
1. The platform is 3620. - this should be removed because you need the same
change for 3680. And patch v2 already remove it.
2. The packet size from firmware is larger than old response size. I suppose
this one works in most case.
Regards
Yin, Fengwei
> Regards,
> Bjorn
>
next prev parent reply other threads:[~2015-11-12 6:37 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-09 10:02 [PATCH 0/5] wcn36xx: add some new firmware functionalities support Yin, Fengwei
2015-11-09 10:02 ` [PATCH 1/5] wcn36xx: introduce WCN36XX_HAL_AVOID_FREQ_RANGE_IND Yin, Fengwei
2015-11-09 15:37 ` Bob Copeland
2015-11-09 10:02 ` [PATCH 2/5] wcn36xx: swallow two wcn3620 IND messages Yin, Fengwei
2015-11-09 15:38 ` Bob Copeland
2015-11-09 10:02 ` [PATCH 3/5] wcn36xx: handle new hal response format Yin, Fengwei
2015-11-09 9:25 ` kbuild test robot
2015-11-09 9:29 ` fengwei.yin
2015-11-09 10:22 ` kbuild test robot
2015-11-09 15:43 ` Bob Copeland
2015-11-09 10:02 ` [PATCH 4/5] wcn3620: use new response format for wcn3620 trigger_ba Yin, Fengwei
2015-11-09 15:40 ` Bob Copeland
2015-11-10 7:08 ` fengwei.yin
2015-11-10 14:13 ` Bob Copeland
2015-11-11 0:37 ` fengwei.yin
2015-11-19 3:20 ` yfw
2015-11-19 17:41 ` Bob Copeland
2015-11-20 1:40 ` fengwei.yin
2015-11-20 1:52 ` Bob Copeland
2015-11-20 2:11 ` fengwei.yin
2015-11-12 4:50 ` Bjorn Andersson
2015-11-12 6:37 ` fengwei.yin [this message]
2015-11-22 20:13 ` Eugene Krasnikov
2015-11-09 10:02 ` [PATCH 5/5] wcn3620: use new response format for wcn3620 remove_bsskey Yin, Fengwei
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=564433A2.1080407@linaro.org \
--to=fengwei.yin@linaro.org \
--cc=andy.green@linaro.org \
--cc=bjorn.andersson@sonymobile.com \
--cc=bjorn@kryo.se \
--cc=k.eugene.e@gmail.com \
--cc=linux-wireless@vger.kernel.org \
--cc=me@bobcopeland.com \
--cc=wcn36xx@lists.infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).