From: Michal Kazior <michal.kazior@tieto.com>
To: ath9k-devel@lists.ath9k.org
Subject: [ath9k-devel] [PATCH 03/10] ath10k: allow deferred regd update
Date: Tue, 11 Jun 2013 07:38:08 +0200 [thread overview]
Message-ID: <51B6B7C0.8040401@tieto.com> (raw)
In-Reply-To: <87d2rtucoc.fsf@kamboji.qca.qualcomm.com>
On 10/06/13 18:56, Kalle Valo wrote:
> Michal Kazior <michal.kazior@tieto.com> writes:
>
>> Regulatory domain notification hook can be called
>> regardless of the hw state (i.e. before start
>> mac80211 callback).
>>
>> Signed-off-by: Michal Kazior <michal.kazior@tieto.com>
>> ---
>> drivers/net/wireless/ath/ath10k/core.h | 2 ++
>> drivers/net/wireless/ath/ath10k/mac.c | 23 ++++++++++++++++++-----
>> 2 files changed, 20 insertions(+), 5 deletions(-)
>>
>> diff --git a/drivers/net/wireless/ath/ath10k/core.h b/drivers/net/wireless/ath/ath10k/core.h
>> index c718b80..a3ab3eb 100644
>> --- a/drivers/net/wireless/ath/ath10k/core.h
>> +++ b/drivers/net/wireless/ath/ath10k/core.h
>> @@ -345,6 +345,8 @@ struct ath10k {
>> struct completion offchan_tx_completed;
>> struct sk_buff *offchan_tx_skb;
>>
>> + bool started;
>
> I would prefer to have a proper state variable right from the start.
> Sooner or later we need it anyway. Otherwise we end up to "flag hell"
> (checking multiple flags).
>
> For ath6kl we currently have:
>
> enum ath6kl_state {
> ATH6KL_STATE_OFF,
> ATH6KL_STATE_ON,
> ATH6KL_STATE_SUSPENDING,
> ATH6KL_STATE_RESUMING,
> ATH6KL_STATE_DEEPSLEEP,
> ATH6KL_STATE_CUTPOWER,
> ATH6KL_STATE_WOW,
> ATH6KL_STATE_RECOVERY,
> };
>
> I think ON and OFF states would be enough for ath10k currently. We can
> extend them as we add more features.
Sounds good. I'll fix this and resend later.
-- Pozdrawiam / Best regards, Michal Kazior.
next prev parent reply other threads:[~2013-06-11 5:38 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-06 10:25 [ath9k-devel] [PATCH 00/10] ath10k: device setup refactor Michal Kazior
2013-06-06 10:25 ` [ath9k-devel] [PATCH 01/10] ath10k: decouple pci init/deinit logic Michal Kazior
2013-06-06 10:25 ` [ath9k-devel] [PATCH 02/10] ath10k: decouple core " Michal Kazior
2013-06-10 16:53 ` Kalle Valo
2013-06-11 5:37 ` Michal Kazior
2013-06-06 10:25 ` [ath9k-devel] [PATCH 03/10] ath10k: allow deferred regd update Michal Kazior
2013-06-06 11:44 ` Sujith Manoharan
2013-06-10 16:56 ` Kalle Valo
2013-06-11 5:38 ` Michal Kazior [this message]
2013-06-06 10:25 ` [ath9k-devel] [PATCH 04/10] ath10k: reset BMI state upon init Michal Kazior
2013-06-10 16:57 ` Kalle Valo
2013-06-06 10:25 ` [ath9k-devel] [PATCH 05/10] ath10k: decouple suspend code Michal Kazior
2013-06-06 11:48 ` Sujith Manoharan
2013-06-06 13:18 ` Michal Kazior
2013-06-06 10:25 ` [ath9k-devel] [PATCH 06/10] ath10k: defer hw setup to start/stop mac80211 hooks Michal Kazior
2013-06-06 10:38 ` Sujith Manoharan
2013-06-06 12:13 ` Sujith Manoharan
2013-06-06 10:25 ` [ath9k-devel] [PATCH 07/10] ath10k: store firmware files in memory Michal Kazior
2013-06-06 10:25 ` [ath9k-devel] [PATCH 08/10] ath10k: make sure all resources are freed upon ath10k_stop() Michal Kazior
2013-06-06 10:26 ` [ath9k-devel] [PATCH 09/10] ath10k: handle hw reconfiguration properly Michal Kazior
2013-06-10 17:08 ` Kalle Valo
2013-06-11 5:43 ` Michal Kazior
2013-06-06 10:26 ` [ath9k-devel] [PATCH 10/10] ath10k: move free_vdev_map initialization Michal Kazior
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=51B6B7C0.8040401@tieto.com \
--to=michal.kazior@tieto.com \
--cc=ath9k-devel@lists.ath9k.org \
/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