From: Ben Greear <greearb@candelatech.com>
To: Kalle Valo <kvalo@qca.qualcomm.com>
Cc: linux-wireless <linux-wireless@vger.kernel.org>,
Michal Kazior <michal.kazior@tieto.com>,
"ath10k@lists.infradead.org" <ath10k@lists.infradead.org>
Subject: Re: [PATCH] ath10k: request firmware flush in ath10k_flush.
Date: Mon, 29 Sep 2014 08:58:57 -0700 [thread overview]
Message-ID: <542981C1.7020000@candelatech.com> (raw)
In-Reply-To: <871tqu3dgu.fsf@kamboji.qca.qualcomm.com>
On 09/29/2014 03:53 AM, Kalle Valo wrote:
>> Thanks. I think ath10k should do this instead of having CT-specific
>> flush eventually.
>
> I agree. We should not be forking functionality unless absolutely
> necessary.
Ok, this patch is easy to carry in my own tree.
But, for things upstream firmware just cannot support,
like tx-rate-status and rx-software-crypt, how do you
want it flagged in the driver? Can I get the CT firmware
flag in for that, or does it have to be some other way?
If you just will not accept any such patch, let me know so
I can quite bothering you about it.
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
WARNING: multiple messages have this Message-ID (diff)
From: Ben Greear <greearb@candelatech.com>
To: Kalle Valo <kvalo@qca.qualcomm.com>
Cc: Michal Kazior <michal.kazior@tieto.com>,
linux-wireless <linux-wireless@vger.kernel.org>,
"ath10k@lists.infradead.org" <ath10k@lists.infradead.org>
Subject: Re: [PATCH] ath10k: request firmware flush in ath10k_flush.
Date: Mon, 29 Sep 2014 08:58:57 -0700 [thread overview]
Message-ID: <542981C1.7020000@candelatech.com> (raw)
In-Reply-To: <871tqu3dgu.fsf@kamboji.qca.qualcomm.com>
On 09/29/2014 03:53 AM, Kalle Valo wrote:
>> Thanks. I think ath10k should do this instead of having CT-specific
>> flush eventually.
>
> I agree. We should not be forking functionality unless absolutely
> necessary.
Ok, this patch is easy to carry in my own tree.
But, for things upstream firmware just cannot support,
like tx-rate-status and rx-software-crypt, how do you
want it flagged in the driver? Can I get the CT firmware
flag in for that, or does it have to be some other way?
If you just will not accept any such patch, let me know so
I can quite bothering you about it.
Thanks,
Ben
--
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc http://www.candelatech.com
next prev parent reply other threads:[~2014-09-29 15:59 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-19 18:28 [PATCH] ath10k: request firmware flush in ath10k_flush greearb
2014-09-19 18:28 ` greearb
2014-09-23 9:16 ` Michal Kazior
2014-09-23 9:16 ` Michal Kazior
2014-09-23 14:19 ` Ben Greear
2014-09-23 14:19 ` Ben Greear
2014-09-24 6:50 ` Michal Kazior
2014-09-24 6:50 ` Michal Kazior
2014-09-24 16:13 ` Ben Greear
2014-09-24 16:13 ` Ben Greear
2014-09-29 10:53 ` Kalle Valo
2014-09-29 10:53 ` Kalle Valo
2014-09-29 15:58 ` Ben Greear [this message]
2014-09-29 15:58 ` Ben Greear
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=542981C1.7020000@candelatech.com \
--to=greearb@candelatech.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 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.