ATH10K Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Kalle Valo <kvalo@qca.qualcomm.com>
To: Michal Kazior <michal.kazior@tieto.com>
Cc: Marek Puzyniak <marek.puzyniak@tieto.com>,
	linux-wireless <linux-wireless@vger.kernel.org>,
	"ath10k@lists.infradead.org" <ath10k@lists.infradead.org>
Subject: Re: [PATCH v4 1/6] ath10k: unify tx mode and dispatch
Date: Fri, 27 Mar 2015 14:41:44 +0200	[thread overview]
Message-ID: <87wq227gtz.fsf@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: <CA+BoTQmk+KzhO1xa3AP9tiDnEVG36OD5WoV+VwRCtvSF1sEtMw@mail.gmail.com> (Michal Kazior's message of "Thu, 26 Mar 2015 11:03:08 +0100")

Michal Kazior <michal.kazior@tieto.com> writes:

> On 26 March 2015 at 10:27, Michal Kazior <michal.kazior@tieto.com> wrote:
>> On 20 March 2015 at 12:02, Marek Puzyniak <marek.puzyniak@tieto.com> wrote:
>>> From: Michal Kazior <michal.kazior@tieto.com>
>>>
>>> There are a few different tx paths depending on
>>> firmware and frame itself.
>>>
>>> Creating a uniform decision will make it possible
>>> to switch between different txmode easier, both
>>> for testing and for future features as well.
>>>
>>> Signed-off-by: Michal Kazior <michal.kazior@tieto.com>
>>> Signed-off-by: Marek Puzyniak <marek.puzyniak@tieto.com>
>> [...]
>>
>> This patch apparently breaks AP operation. I need to investigate this.
>
> Ok - htt.freq missed clearing and in some cases it contained garbage
> leading to HTT discarding packets.
>
> @Kalle: I've posted a patch `ath10k: clear htt.freq` which addresses
> the problem separately. Please apply it _before_ you apply TDLS
> patches (which are fine, including this patch) to avoid breakage
> in-between commits.

Ack, I'll do that. Thanks for fixing this.

-- 
Kalle Valo

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

  reply	other threads:[~2015-03-27 12:42 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-20 11:02 [PATCH v4 0/6] ath10k: add basic tdls support Marek Puzyniak
2015-03-20 11:02 ` [PATCH v4 1/6] ath10k: unify tx mode and dispatch Marek Puzyniak
2015-03-26  9:27   ` Michal Kazior
2015-03-26 10:03     ` Michal Kazior
2015-03-27 12:41       ` Kalle Valo [this message]
2015-03-20 11:02 ` [PATCH v4 2/6] ath10k: make peer type configurable Marek Puzyniak
2015-03-20 11:02 ` [PATCH v4 3/6] ath10k: store max tdls vdevs that fw can handle Marek Puzyniak
2015-03-20 11:02 ` [PATCH v4 4/6] ath10k: update station counting Marek Puzyniak
2015-03-20 11:02 ` [PATCH v4 5/6] ath10k: add wmi support for tdls Marek Puzyniak
2015-03-22  7:49   ` Arik Nemtsov
2015-03-23  8:09     ` Michal Kazior
2015-03-23  8:59       ` Marek Puzyniak
2015-03-23  9:46         ` Arik Nemtsov
2015-03-23 15:53   ` Kalle Valo
2015-03-24  7:33     ` Marek Puzyniak
2015-03-24  8:50       ` Kalle Valo
2015-03-20 11:02 ` [PATCH v4 6/6] ath10k: introduce basic tdls functionality Marek Puzyniak
2015-03-27 14:33   ` Marek Puzyniak
2015-03-27 17:43     ` Kalle Valo
2015-03-30 12:06 ` [PATCH v4 0/6] ath10k: add basic tdls support Kalle Valo

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=87wq227gtz.fsf@kamboji.qca.qualcomm.com \
    --to=kvalo@qca.qualcomm.com \
    --cc=ath10k@lists.infradead.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=marek.puzyniak@tieto.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox