From: Kalle Valo <kvalo@qca.qualcomm.com>
To: Peter Oh <poh@qca.qualcomm.com>
Cc: <ath10k@lists.infradead.org>, <linux-wireless@vger.kernel.org>
Subject: Re: [PATCH 1/3] ath10k: update tx path to support QCA99X0
Date: Sat, 11 Jul 2015 19:14:56 +0300 [thread overview]
Message-ID: <87egkewu0v.fsf@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: <1436287676-25767-2-git-send-email-poh@qca.qualcomm.com> (Peter Oh's message of "Tue, 7 Jul 2015 09:47:54 -0700")
Peter Oh <poh@qca.qualcomm.com> writes:
> Since QCA99X0 uses fragmentation descriptor differently from
> other ones on tx path, we need to handle it separately.
>
> QCA99X0 is using 48 bits for address and 16 bits for length
> out of 2 dword and each values have to be programmed by frag
> desc base addr + msdu id, so that hardware can retrieve
> corresponding frag data.
>
> Signed-off-by: Peter Oh <poh@qca.qualcomm.com>
kbuild found a new warning:
>> drivers/net/wireless/ath/ath10k/htt_tx.c:547:52: sparse: incorrect
>> type in assignment (different base types)
drivers/net/wireless/ath/ath10k/htt_tx.c:547:52: expected
>> restricted __le16 [usertype] len_16
drivers/net/wireless/ath/ath10k/htt_tx.c:547:52: got restricted
>> __le32 [usertype] <noident>
--
Kalle Valo
next prev parent reply other threads:[~2015-07-11 16:15 UTC|newest]
Thread overview: 7+ 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 ` [PATCH 1/3] ath10k: update tx " Peter Oh
2015-07-11 16:14 ` Kalle Valo [this message]
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 ` [PATCH 3/3] ath10k: add support for qca99x0 Rx descriptors Peter Oh
2015-07-07 17:09 ` CACook
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=87egkewu0v.fsf@kamboji.qca.qualcomm.com \
--to=kvalo@qca.qualcomm.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).