On 2018-09-19 07:50, Toke Høiland-Jørgensen wrote:
Kalle Valo writes:
Toke Høiland-Jørgensen writes:
Unfortunately ath10k is not reporting last_tx_rate in tx_status().
So
I also applied this "ath10k: report tx rate using
ieee80211_tx_status"
change.
Yeah, that and the patch that
Kalle Valo writes:
> Toke Høiland-Jørgensen writes:
>
>>> Unfortunately ath10k is not reporting last_tx_rate in tx_status(). So
>>> I also applied this "ath10k: report tx rate using ieee80211_tx_status"
>>> change.
>>
>> Yeah, that and the patch that computes the last used rate will probably
>>
Toke Høiland-Jørgensen writes:
>> Unfortunately ath10k is not reporting last_tx_rate in tx_status(). So
>> I also applied this "ath10k: report tx rate using ieee80211_tx_status"
>> change.
>
> Yeah, that and the patch that computes the last used rate will probably
> be necessary; but they can be
Rajkumar Manoharan writes:
> On 2018-09-18 13:41, Toke Høiland-Jørgensen wrote:
>> Rajkumar Manoharan writes:
>>
> Also an option to add the node at head or tail would be preferred.
> If
> return_txq adds node at head of list, then it is forcing the driver
> to
> serve
On 2018-09-18 13:41, Toke Høiland-Jørgensen wrote:
Rajkumar Manoharan writes:
Also an option to add the node at head or tail would be preferred.
If
return_txq adds node at head of list, then it is forcing the driver
to
serve same txq until it becomes empty. Also this will not allow the
Rajkumar Manoharan writes:
>>> Also an option to add the node at head or tail would be preferred. If
>>> return_txq adds node at head of list, then it is forcing the driver to
>>> serve same txq until it becomes empty. Also this will not allow the
>>> driver to send N frames from each txqs.
>>
On 2018-09-18 03:29, Toke Høiland-Jørgensen wrote:
Rajkumar Manoharan writes:
On 2018-09-16 10:42, Toke Høiland-Jørgensen wrote:
return_txq() should return a bool to inform the driver that whether
txq is queued back or not.
What would the driver do with that return value, exactly?
never
Rajkumar Manoharan writes:
> On 2018-09-16 10:42, Toke Høiland-Jørgensen wrote:
>> +/**
>> + * ieee80211_return_txq - return a TXQ previously acquired by
>> ieee80211_next_txq()
>> + *
>> + * @hw: pointer as obtained from ieee80211_alloc_hw()
>> + * @txq: pointer obtained from station or virtual
On 2018-09-16 10:42, Toke Høiland-Jørgensen wrote:
+/**
+ * ieee80211_return_txq - return a TXQ previously acquired by
ieee80211_next_txq()
+ *
+ * @hw: pointer as obtained from ieee80211_alloc_hw()
+ * @txq: pointer obtained from station or virtual interface
+ *
+ * Should only be called
This adds an API to mac80211 to handle scheduling of TXQs. The interface
between driver and mac80211 for TXQ handling is changed by adding two new
functions: ieee80211_next_txq(), which will return the next TXQ to schedule
in the current round-robin rotation, and ieee80211_return_txq(), which the
10 matches
Mail list logo
