All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ben Greear <greearb@candelatech.com>
To: Alessandro Bolletta <alessandro@mediaspot.net>,
	"ath10k@lists.infradead.org" <ath10k@lists.infradead.org>
Subject: Re: R: Link can't get estabilished over RB911AC boards
Date: Tue, 22 Sep 2015 14:14:32 -0700	[thread overview]
Message-ID: <5601C4B8.5060807@candelatech.com> (raw)
In-Reply-To: <F52F175DFC537F48A43937B50B44BCA282084A3D@EXCHANGE.mediaspot.local>

On 09/22/2015 02:09 PM, Alessandro Bolletta wrote:
> Just one more information Ben: this patch introduces ack timing in ath10k, but in order to set it, has it to be triggered manually in debugfs or is it UCI (openwrt) able to set it automatically by his configuration process?
>
> Also, there's a little thing that i'm not understanding: is it the firmware that controls ack timings or is it related to ath10k?
>
> Thanks in advance and please be patient with me, I'm not an expert, but i'd like to be :)

debugfs hooks need to be written in ath10k driver to poke the firmware.
Then, openwrt would need to know how to set the value through debugfs.

Maybe someone in openwrt can work with me to get this working sometime soon.

Thanks,
Ben

-- 
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc  http://www.candelatech.com


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

  reply	other threads:[~2015-09-22 21:14 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-21 19:57 Link can't get estabilished over RB911AC boards Alessandro Bolletta
2015-09-21 20:36 ` Ben Greear
2015-09-21 22:18   ` R: " Alessandro Bolletta
2015-09-21 23:18     ` Ben Greear
2015-09-21 23:20       ` R: " Alessandro Bolletta
2015-09-21 23:34         ` Ben Greear
2015-09-22 21:09   ` Alessandro Bolletta
2015-09-22 21:14     ` Ben Greear [this message]
     [not found] ` <CAGNwC3nKb_tJnL44tu0jaV5h2hX2KLqoiLdm-GR+myyKRHZdBQ@mail.gmail.com>
2015-09-22 21:26   ` Alessandro Bolletta

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=5601C4B8.5060807@candelatech.com \
    --to=greearb@candelatech.com \
    --cc=alessandro@mediaspot.net \
    --cc=ath10k@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 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.