All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ben Greear <greearb@candelatech.com>
To: Adrian Chadd <adrian@freebsd.org>
Cc: Michal Kazior <michal.kazior@tieto.com>,
	"ath10k@lists.infradead.org" <ath10k@lists.infradead.org>
Subject: Re: hacked 4.4.6+, 10.4.3 firmware, Running out of ring-index for pipe-id 3 (WMI).
Date: Wed, 30 Mar 2016 13:07:47 -0700	[thread overview]
Message-ID: <56FC3213.7050103@candelatech.com> (raw)
In-Reply-To: <CAJ-VmokzeRX=ZPtP+JJqfL+tL60GR8aZpaBCCxVHZ=D8JRD3ww@mail.gmail.com>

On 03/29/2016 10:45 AM, Adrian Chadd wrote:
> On 29 March 2016 at 10:13, Ben Greear <greearb@candelatech.com> wrote:
>> On 03/29/2016 10:08 AM, Adrian Chadd wrote:
>>>
>>> Does it eventually catch up?
>>
>>
>> It seems to.
>>
>>> IE, put a wait completion in there?
>>
>>
>> Maybe so, but the current wait-completion waits on tx-credits,
>> so more like I'd need to put the whole wait-completion in a loop
>> and add a small sleep, maybe?
>>
>> Or, maybe try to force a read of the CE entries if the CE logic
>> ever detects the ring is full?
>
> Right. A little sleep (as long as its in a place where you can do it!)
> just to check would be good. I'd also print out the CE ring contents
> as well - see where the firmware has gotten to.

This seemed to help my system, but I also fixed some other bugs that made
the system work better over-all, so not sure this is a complete fix on its
own.  I'll send a patch in case someone wants to give it a try.

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:[~2016-03-30 20:36 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-28 19:01 hacked 4.4.6+, 10.4.3 firmware, Running out of ring-index for pipe-id 3 (WMI) Ben Greear
2016-03-29  8:05 ` Michal Kazior
2016-03-29 15:48   ` Ben Greear
     [not found]     ` <CAJ-Vmo=RzwymMtdWkrKTEnf+FU=Q3MU3QNqFneq74Qcn3BMfyg@mail.gmail.com>
2016-03-29 17:13       ` Ben Greear
2016-03-29 17:45         ` Adrian Chadd
2016-03-30 20:07           ` Ben Greear [this message]
2016-03-31  6:51     ` Michal Kazior
2016-03-31 15:51       ` Ben Greear
2016-03-31 16:44       ` Ben Greear
2016-04-01  5:18         ` Michal Kazior
2016-04-01  5:23           ` Ben Greear
2016-04-01  6:23             ` Michal Kazior

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=56FC3213.7050103@candelatech.com \
    --to=greearb@candelatech.com \
    --cc=adrian@freebsd.org \
    --cc=ath10k@lists.infradead.org \
    --cc=michal.kazior@tieto.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 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.