ATH10K Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Kalle Valo <kvalo@qca.qualcomm.com>
To: Janusz Dziedzic <janusz.dziedzic@tieto.com>
Cc: while1eq1@gmail.com, markaswift@gmail.com, ath10k@lists.infradead.org
Subject: Re: [RFC 2/2] ath10k: setup AMSDU subframes to 1
Date: Thu, 15 May 2014 14:26:34 +0300	[thread overview]
Message-ID: <87a9aj9tat.fsf@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: <1400151186-24949-2-git-send-email-janusz.dziedzic@tieto.com> (Janusz Dziedzic's message of "Thu, 15 May 2014 12:53:06 +0200")

Janusz Dziedzic <janusz.dziedzic@tieto.com> writes:

> Fore test purpose only.
>
> Signed-off-by: Janusz Dziedzic <janusz.dziedzic@tieto.com>
> ---
>  drivers/net/wireless/ath/ath10k/core.c |    2 ++
>  1 file changed, 2 insertions(+)
>
> diff --git a/drivers/net/wireless/ath/ath10k/core.c b/drivers/net/wireless/ath/ath10k/core.c
> index 75b3dfb..1e492a1 100644
> --- a/drivers/net/wireless/ath/ath10k/core.c
> +++ b/drivers/net/wireless/ath/ath10k/core.c
> @@ -847,6 +847,8 @@ int ath10k_core_start(struct ath10k *ar)
>  	if (status)
>  		goto err_disconnect_htc;
>  
> +	WARN_ON(ath10k_htt_h2t_aggr_cfg_msg(&ar->htt, 64, 1));

I anticipate we will need to change AMSDU values in the future and it
would be good to have some proper interface for this command. Maybe a
debugfs file which takes both values? Or something else?

-- 
Kalle Valo

_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k

  reply	other threads:[~2014-05-15 11:27 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-15 10:53 [RFC 1/2] ath10k: add implementation for configure max amsdu, ampdu Janusz Dziedzic
2014-05-15 10:53 ` [RFC 2/2] ath10k: setup AMSDU subframes to 1 Janusz Dziedzic
2014-05-15 11:26   ` Kalle Valo [this message]
2014-05-15 11:24 ` [RFC 1/2] ath10k: add implementation for configure max amsdu, ampdu Kalle Valo
2014-05-15 11:35   ` Janusz Dziedzic
2014-05-15 12:24     ` Kalle Valo
2014-07-08 10:46       ` Bartosz Markowski

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=87a9aj9tat.fsf@kamboji.qca.qualcomm.com \
    --to=kvalo@qca.qualcomm.com \
    --cc=ath10k@lists.infradead.org \
    --cc=janusz.dziedzic@tieto.com \
    --cc=markaswift@gmail.com \
    --cc=while1eq1@gmail.com \
    /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