linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Kalle Valo <kvalo@codeaurora.org>
To: Russell Hu <rhu@qti.qualcomm.com>
Cc: <linux-wireless@vger.kernel.org>, <rhu@qti.qualcomm.com>,
	<ryanhsu@qti.qualcomm.com>, <rwchang@qti.qualcomm.com>,
	<aeolus@qti.qualcomm.com>, <kvalo@qca.qualcomm.com>
Subject: Re: [v2] ath9k: add MSI support
Date: Tue, 16 Jan 2018 14:29:45 +0000 (UTC)	[thread overview]
Message-ID: <20180116142945.61B43602BA@smtp.codeaurora.org> (raw)
In-Reply-To: <20171011101806.6295-1-rhu@qti.qualcomm.com>

Russell Hu <rhu@qti.qualcomm.com> wrote:

> On new Intel platforms like ApolloLake, legacy interrupt mechanism
> (INTx) is not supported, so WLAN modules are not working because
> interrupts are missing, therefore this patch is to add MSI support to
> ath9k.  With module paremeter "use_msi=1", ath9k driver would try to
> use MSI instead of INTx.
> 
> Signed-off-by: Russell Hu <rhu@qti.qualcomm.com>
> Signed-off-by: Kalle Valo <kvalo@codeaurora.org>

Patch applied to ath-next branch of ath.git, thanks.

7368160f0ab0 ath9k: add MSI support

-- 
https://patchwork.kernel.org/patch/9999249/

https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches

      parent reply	other threads:[~2018-01-16 14:29 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-11 10:18 [PATCH v2] ath9k: add MSI support Russell Hu
2017-11-10  2:54 ` [v2] " Daniel Drake
2017-11-13  8:48   ` Kalle Valo
2017-11-13 22:36     ` Daniel Drake
2017-11-14 12:15       ` Kalle Valo
2017-11-15  7:38         ` Daniel Drake
2017-12-12 11:43           ` Daniel Drake
2018-01-08 12:24             ` Kalle Valo
2018-01-08 14:16               ` Andy Shevchenko
2018-01-08 23:07               ` Daniel Drake
2018-01-09  1:16                 ` AceLan Kao
2018-01-16 14:29 ` Kalle Valo [this message]

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=20180116142945.61B43602BA@smtp.codeaurora.org \
    --to=kvalo@codeaurora.org \
    --cc=aeolus@qti.qualcomm.com \
    --cc=kvalo@qca.qualcomm.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=rhu@qti.qualcomm.com \
    --cc=rwchang@qti.qualcomm.com \
    --cc=ryanhsu@qti.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).