From: Erik Stromdahl <erik.stromdahl@gmail.com>
To: Michal Kazior <michal.kazior@tieto.com>
Cc: Kalle Valo <kvalo@qca.qualcomm.com>,
linux-wireless <linux-wireless@vger.kernel.org>,
"ath10k@lists.infradead.org" <ath10k@lists.infradead.org>
Subject: Re: [RFC 02/12] ath10k: htc: rx trailer lookahead support
Date: Tue, 15 Nov 2016 18:31:15 +0100 [thread overview]
Message-ID: <ac58b3f6-4432-b0b6-8b50-c733f898eded@gmail.com> (raw)
In-Reply-To: <CA+BoTQkJqv28=Mg1ncmyznRo-CLh6Y_OW-mJ+YTyqaREaqp39Q@mail.gmail.com>
On 11/15/2016 10:57 AM, Michal Kazior wrote:
> On 14 November 2016 at 17:33, Erik Stromdahl <erik.stromdahl@gmail.com> wrote:
>> The RX trailer parsing is now capable of parsing lookahead reports.
>> This is needed by SDIO/mbox.
>
> It'd be useful to know what exactly lookahead will be used for. What
> payload does it carry.
>
It carries the 4 first bytes of the next RX message, i.e. the first 4
bytes of an HTC header.
It is used by the sdio interrupt handler to know if the next packet is a
part of an RX bundle, which endpoint it belongs to and how long it is
(so we know how many bytes to allocate).
>
>> Signed-off-by: Erik Stromdahl <erik.stromdahl@gmail.com>
>> ---
>> drivers/net/wireless/ath/ath10k/htc.c | 91 ++++++++++++++++++++++++++++++++-
>> drivers/net/wireless/ath/ath10k/htc.h | 30 +++++++++--
>> 2 files changed, 116 insertions(+), 5 deletions(-)
>>
>> diff --git a/drivers/net/wireless/ath/ath10k/htc.c b/drivers/net/wireless/ath/ath10k/htc.c
>> index 26b1e15..e3f7bf4 100644
>> --- a/drivers/net/wireless/ath/ath10k/htc.c
>> +++ b/drivers/net/wireless/ath/ath10k/htc.c
>> @@ -228,10 +228,74 @@ void ath10k_htc_tx_completion_handler(struct ath10k *ar, struct sk_buff *skb)
>> spin_unlock_bh(&htc->tx_lock);
>> }
>>
>> +static int
>> +ath10k_htc_process_lookahead(struct ath10k_htc *htc,
>> + const struct ath10k_htc_lookahead_report *report,
>> + int len,
>> + enum ath10k_htc_ep_id eid,
>> + u32 *next_lk_ahds,
>
> next_lk_ahds should be u8 or void. From what I understand by glancing
> through the code it is an agnostic buffer that carries payload which
> is later interpreted either as eid or htc header, right? void is
> probably most suitable in this case for passing around and u8 for
> inline-based storage.
>
Sounds reasonable, I'll change to void pointer.
> I'd also avoid silly abbreviations. Probably "lookahead" alone is enough.
>
Ok, this abbreviation was actually taken from the ath6kl code. I think
the intention was to reduce line lengths.
>> + int *next_lk_ahds_len)
>> +{
>> + struct ath10k *ar = htc->ar;
>> +
>> + if (report->pre_valid != ((~report->post_valid) & 0xFF))
>> + /* Invalid lookahead flags are actually transmitted by
>> + * the target in the HTC control message.
>> + * Since this will happen at every boot we silently ignore
>> + * the lookahead in this case
>> + */
>
> I'd put this comment before the if().
Ok
>
>
>> + return 0;
>> +
>> + if (next_lk_ahds && next_lk_ahds_len) {
>> + ath10k_dbg(ar, ATH10K_DBG_HTC,
>> + "htc rx lk_ahd found pre_valid 0x%x post_valid 0x%x\n",
>> + report->pre_valid, report->post_valid);
>> +
>> + /* look ahead bytes are valid, copy them over */
>> + memcpy((u8 *)&next_lk_ahds[0], report->lk_ahd, 4);
>> +
>> + *next_lk_ahds_len = 1;
>> + }
>> +
>> + return 0;
>> +}
>> +
>> +static int
>> +ath10k_htc_process_lookahead_bundle(struct ath10k_htc *htc,
>> + const struct ath10k_htc_lookahead_report_bundle *report,
>> + int len,
>> + enum ath10k_htc_ep_id eid,
>> + u32 *next_lk_ahds,
>
> Ditto. void.
>
>
>> + int *next_lk_ahds_len)
>> +{
>> + int bundle_cnt = len / sizeof(*report);
>> +
>> + if (!bundle_cnt || (bundle_cnt > HTC_HOST_MAX_MSG_PER_BUNDLE)) {
>> + WARN_ON(1);
>
> This should be ath10k_warn() instead. This isn't internal driver flow
> assertion. It is possible firmware bug or revision misalignment
> instead.
>
Ok
>
>> + return -EINVAL;
>> + }
>> +
>> + if (next_lk_ahds && next_lk_ahds_len) {
>> + int i;
>> +
>> + for (i = 0; i < bundle_cnt; i++) {
>> + memcpy((u8 *)&next_lk_ahds[i], report->lk_ahd,
>> + sizeof(u32));
>
> You'll need to re-adjust the &x[i] to maintain proper offset with void pointer.
>
>
> Michał
>
next prev parent reply other threads:[~2016-11-15 17:31 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-14 16:33 [RFC 00/12] ath10k sdio support Erik Stromdahl
2016-11-14 16:33 ` [RFC 01/12] ath10k: htc: made static function public Erik Stromdahl
2016-11-14 16:33 ` [RFC 02/12] ath10k: htc: rx trailer lookahead support Erik Stromdahl
2016-11-15 9:57 ` Michal Kazior
2016-11-15 17:31 ` Erik Stromdahl [this message]
2016-11-16 13:53 ` Valo, Kalle
2016-11-14 16:33 ` [RFC 03/12] ath10k: htc: Changed order of wait target and ep connect Erik Stromdahl
2016-11-15 10:13 ` Michal Kazior
2016-11-15 17:07 ` Erik Stromdahl
2016-11-16 14:29 ` Michal Kazior
2016-11-14 16:33 ` [RFC 04/12] ath10k: htc: refactorization Erik Stromdahl
2016-11-15 10:19 ` Michal Kazior
2016-11-17 16:32 ` Erik Stromdahl
2016-11-18 14:49 ` Michal Kazior
2016-11-14 16:33 ` [RFC 05/12] ath10k: htc: Added ATH10K_HTC_FLAG_BUNDLE_LSB Erik Stromdahl
2016-11-15 10:25 ` Michal Kazior
2016-11-15 10:46 ` Valo, Kalle
2016-11-14 16:33 ` [RFC 06/12] ath10k: bmi: Added SOC reg read/write functions Erik Stromdahl
2016-11-15 10:28 ` Michal Kazior
2016-11-15 17:11 ` Erik Stromdahl
2016-11-14 16:33 ` [RFC 07/12] ath10k: Added SDIO dbg masks Erik Stromdahl
2016-11-14 16:33 ` [RFC 08/12] ath10k: Added ATH10K_BUS_SDIO enum Erik Stromdahl
2016-11-14 16:33 ` [RFC 09/12] ath10k: Mailbox address definitions Erik Stromdahl
2016-11-15 10:31 ` Michal Kazior
2016-11-15 10:48 ` Valo, Kalle
2016-11-14 16:33 ` [RFC 10/12] ath10k: Added QCA65XX hw definition Erik Stromdahl
2016-11-15 10:34 ` Michal Kazior
2016-11-15 10:54 ` Valo, Kalle
2016-11-15 18:34 ` Erik Stromdahl
2016-11-14 16:33 ` [RFC 11/12] ath10k: Added more host_interest members Erik Stromdahl
2016-11-14 16:33 ` [RFC 12/12] ath10k: Added sdio support Erik Stromdahl
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=ac58b3f6-4432-b0b6-8b50-c733f898eded@gmail.com \
--to=erik.stromdahl@gmail.com \
--cc=ath10k@lists.infradead.org \
--cc=kvalo@qca.qualcomm.com \
--cc=linux-wireless@vger.kernel.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 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).