From: "Dedy Lansky" <dlansky@codeaurora.org>
To: "'David Dean Zhang'" <daviddean166@gmail.com>,
<linux-wireless@vger.kernel.org>
Subject: RE: wil6210: low level sector API
Date: Sun, 22 Apr 2018 17:29:01 +0300 [thread overview]
Message-ID: <000e01d3da46$43f06430$cbd12c90$@codeaurora.org> (raw)
In-Reply-To: <CAFnQ7oti-cKJxBXyuCCfJeLgHMcw1U0pE1hkdCH_ukN032f90A@mail.gmail.com>
> From: linux-wireless-owner@vger.kernel.org =
[mailto:linux-wireless-owner@vger.kernel.org] On Behalf Of David Dean =
Zhang
> Sent: Wednesday, April 18, 2018 9:01 PM
> I updated the firmware and tried to call some low level functions, =
like WMI_PRIO_TX_SECTORS_NUMBER_CMDID and WMI_SET_RF_SECTOR_ON_CMDID .
> The previous errors have gone but it still has errors:
> wil6210 0000:03:00.0 wlp3s0: wmi_event_handle: Unhandled event 0x19a5
> wil6210 0000:03:00.0 wlp3s0: wmi_call: wmi_call(0x09a6->0x19a6) =
timeout 2000 msec
> So I am wondering whether it is because the chipset does not support =
these wmi commands. I just want to know how to use these commands and =
how to disable TXSS. I appreciate if anyone could provide some =
suggestions. Thanks.
This is a bug in FW that upon WMI_PRIO_TX_SECTORS_NUMBER_CMDID, wrong =
event is returned. Most likely that the WMI_PRIO_TX_SECTORS_NUMBER_CMDID =
was handled successfully. The bug is not critical - event 0x19a5 is =
returned instead of 0x19a6 (as can be seen in dmesg).
Another option for disabling TXSS/BRP and hopefully to keep the sector =
locked is by using WMI_BF_CONTROL_CMDID. Setting "triggers" and =
"long_term_enable" to 0 should disable BF completely.
Thanks,
Dedy.
next prev parent reply other threads:[~2018-04-22 14:29 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-26 18:37 wil6210: low level sector API David Dean
2018-03-29 12:29 ` Dedy Lansky
2018-04-18 18:01 ` David Dean Zhang
2018-04-22 14:29 ` Dedy Lansky [this message]
2018-04-27 21:40 ` David Dean Zhang
-- strict thread matches above, loose matches on Subject: below --
2024-08-24 17:31 Herman Zeilstra
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='000e01d3da46$43f06430$cbd12c90$@codeaurora.org' \
--to=dlansky@codeaurora.org \
--cc=daviddean166@gmail.com \
--cc=linux-wireless@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.