On Tuesday, 11 December 2018 05:56:11 CET Pradeep Kumar Chitrapu wrote:
> From: Pradeep kumar Chitrapu
>
> Invalid rate code is sent to firmware when multicast rate value of 0 is
> sent to driver indicating disabled case, causing broken mesh path.
> so fix that.
>
> Tested on QCA9984 with firmwa
Surabhi Vishnoi wrote:
> Currently, rx_duration for each peer is not getting populated in
> fw_stats debugfs entry for WCN3990.
>
> WCN3990 firmware sends rx duration for each peer as part of
> peer_extd_stats in WMI_UPDATE_STATS_EVENT. To enable peer_extd_stats,
> firmware expects host to send
tree: https://git.kernel.org/pub/scm/linux/kernel/git/kvalo/ath.git pending
head: 24030e6e2fb932ab9817c146a2835b4333e1b3c9
commit: b6891b9b2aee2de7d2f3b28907484c12b19c9f58 [13/22] ath10k: Fill rx
duration for each peer in fw_stats for WCN3990
config: xtensa-allyesconfig (attached as .config)
c
With the current implementation of wmi init command,
there is no provision for the host driver to provide mem
chunks addresses with more than 32-bit, to the firmware.
WCN3990 is a 35-bit target and can accept mem chunks addresses
which are above 32-bit.
If firmware supports address range more than
Rakesh Pillai writes:
> The peer param id for PEER_PARAM_USE_FIXED_PWR
> is different for tlv and non-tlv firmware. This
> causes incorrect peer param to be set by the driver
> to the firmware(tlv/non-tlv).
>
> Create seperate peer param map for tlv and non-tlv
> firmware and attach the peer para
