All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sujith Manoharan <sujith@msujith.org>
To: Stanislaw Gruszka <sgruszka@redhat.com>
Cc: John Linville <linville@tuxdriver.com>, linux-wireless@vger.kernel.org
Subject: Re: [PATCH 2/7] ath9k: Enable WoW only for AR9462
Date: Mon, 3 Jun 2013 20:47:57 +0530	[thread overview]
Message-ID: <20908.45989.889590.158302@gargle.gargle.HOWL> (raw)
In-Reply-To: <20130603150846.GB2146@redhat.com>

Stanislaw Gruszka wrote:
> Do this feature will be added back in the future? If so, when? Or there
> are some limitations regarding WoW support on older chips?

WoW hasn't been tested or verified with ath9k using AR9280 at all, so we
don't know what is missing in ath9k to handle the chip's peculiarities.

> I'm asking because, we have RHEL customer that request WoWLAN support
> for AR9280. I thought this will be matter of backport ath9k driver
> from upstream to RHEL, since we have commits that add WoW for AR9002,
> including AR9280. But since you're now removing that feature I'm a bit
> worried. Will WoW be supported on AR9280, or we should rather ask
> customer to use different chip i.e. AR9462 ?

If AR9280 is used, getting support for WoW would be difficult. AR9462 has
been through internal test-cycles for WoW, so it seems a more sensible choice.

But, the AR9002-specific code can be retained in the driver if RH needs it.

Sujith

  reply	other threads:[~2013-06-03 15:20 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-03  3:49 [PATCH 1/7] ath9k: Return early for invalid rates Sujith Manoharan
2013-06-03  3:49 ` [PATCH 2/7] ath9k: Enable WoW only for AR9462 Sujith Manoharan
2013-06-03 15:08   ` Stanislaw Gruszka
2013-06-03 15:17     ` Sujith Manoharan [this message]
     [not found]       ` <CAD2nsn0=W+KU4S7cOzAQ1C5mt_GUzAYDNjtwhjvw-C7NM_4eQQ@mail.gmail.com>
2013-06-05 16:13         ` Sujith Manoharan
2013-06-03  3:49 ` [PATCH 3/7] ath9k: Remove unused structure ath_dbg_bb_mac_samp Sujith Manoharan
2013-06-03  3:49 ` [PATCH 4/7] ath9k: Simplify ANI initialization Sujith Manoharan
2013-06-03  3:49 ` [PATCH 5/7] ath9k: Set ofdmWeakSigDetect directly Sujith Manoharan
2013-06-03  3:49 ` [PATCH 6/7] ath9k: Print ANI statistics in debugfs Sujith Manoharan
2013-06-03  3:49 ` [PATCH 7/7] ath9k: Do not maintain ANI state per-channel Sujith Manoharan

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=20908.45989.889590.158302@gargle.gargle.HOWL \
    --to=sujith@msujith.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linville@tuxdriver.com \
    --cc=sgruszka@redhat.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.