All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Oh <poh@codeaurora.org>
To: CACook@quantum-sci.com, ath10k@lists.infradead.org
Cc: linux-wireless@vger.kernel.org, Peter Oh <poh@qca.qualcomm.com>
Subject: Re: [PATCH 3/3] ath10k: add support for qca99x0 Rx descriptors
Date: Tue, 07 Jul 2015 14:10:03 -0700	[thread overview]
Message-ID: <559C402B.3090004@codeaurora.org> (raw)
In-Reply-To: <2345251.lpvZM96hbt@andromeda>


On 07/07/2015 10:09 AM, CACook@quantum-sci.com wrote:
> On Tuesday 07 July 2015 9:47:56 Peter Oh wrote:
>> QCA99X0 chip has an extra 4 bytes in rx_msdu_start,
>> 20 bytes in rx_msdu_end and 20 bytes in rx_ppdu_end structure
>> which are used in htt_rx_desc and HTT Rx ring offset setup.
>> This is necessary for correct Rx for QCA99X0 or Rx descriptors
>> will be overwritten and corrupted.
> Will this be in the most recent git,
Yes. this patch set is based on top of most recent git.
>   to support the QCA9880?
QCA9880 is already supported and this patch set is to support QCA99X0.
>
>
>
> _______________________________________________
> ath10k mailing list
> ath10k@lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/ath10k
Thanks,
Peter

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

WARNING: multiple messages have this Message-ID (diff)
From: Peter Oh <poh@codeaurora.org>
To: CACook@quantum-sci.com, ath10k@lists.infradead.org
Cc: linux-wireless@vger.kernel.org, Peter Oh <poh@qca.qualcomm.com>
Subject: Re: [PATCH 3/3] ath10k: add support for qca99x0 Rx descriptors
Date: Tue, 07 Jul 2015 14:10:03 -0700	[thread overview]
Message-ID: <559C402B.3090004@codeaurora.org> (raw)
In-Reply-To: <2345251.lpvZM96hbt@andromeda>


On 07/07/2015 10:09 AM, CACook@quantum-sci.com wrote:
> On Tuesday 07 July 2015 9:47:56 Peter Oh wrote:
>> QCA99X0 chip has an extra 4 bytes in rx_msdu_start,
>> 20 bytes in rx_msdu_end and 20 bytes in rx_ppdu_end structure
>> which are used in htt_rx_desc and HTT Rx ring offset setup.
>> This is necessary for correct Rx for QCA99X0 or Rx descriptors
>> will be overwritten and corrupted.
> Will this be in the most recent git,
Yes. this patch set is based on top of most recent git.
>   to support the QCA9880?
QCA9880 is already supported and this patch set is to support QCA99X0.
>
>
>
> _______________________________________________
> ath10k mailing list
> ath10k@lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/ath10k
Thanks,
Peter

  reply	other threads:[~2015-07-07 21:11 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-07 16:47 [PATCH 0/3] ath10k: update data path to support QCA99X0 Peter Oh
2015-07-07 16:47 ` Peter Oh
2015-07-07 16:47 ` [PATCH 1/3] ath10k: update tx " Peter Oh
2015-07-07 16:47   ` Peter Oh
2015-07-11 16:14   ` Kalle Valo
2015-07-11 16:14     ` Kalle Valo
2015-07-07 16:47 ` [PATCH 2/3] ath10k: redefine rx_ppdu_end_common structure to cover qca99x0 Peter Oh
2015-07-07 16:47   ` Peter Oh
2015-07-07 16:47 ` [PATCH 3/3] ath10k: add support for qca99x0 Rx descriptors Peter Oh
2015-07-07 16:47   ` Peter Oh
2015-07-07 17:09   ` CACook
2015-07-07 17:09     ` CACook
2015-07-07 21:10     ` Peter Oh [this message]
2015-07-07 21:10       ` Peter Oh

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=559C402B.3090004@codeaurora.org \
    --to=poh@codeaurora.org \
    --cc=CACook@quantum-sci.com \
    --cc=ath10k@lists.infradead.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=poh@qca.qualcomm.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.