linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Kalle Valo <kvalo@qca.qualcomm.com>
To: Daniel Drake <drake@endlessm.com>
Cc: Russell Hu <rhu@qti.qualcomm.com>,
	"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
	Ryan Hsu <ryanhsu@qti.qualcomm.com>,
	"Robert Chang" <rwchang@qti.qualcomm.com>,
	Aeolus Yang <aeolus@qti.qualcomm.com>,
	ath9k-devel <ath9k-devel@qca.qualcomm.com>,
	"linux@endlessm.com" <linux@endlessm.com>,
	"rafael.j.wysocki@intel.com" <rafael.j.wysocki@intel.com>,
	"andy@infradead.org" <andy@infradead.org>,
	"acelan.kao@canonical.com" <acelan.kao@canonical.com>
Subject: Re: [v2] ath9k: add MSI support
Date: Mon, 8 Jan 2018 12:24:34 +0000	[thread overview]
Message-ID: <87bmi45yim.fsf@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: <CAD8Lp44BWhK7j5dKzHqqXTaR4uG9=-6oJd2NEsdM8oQYw0D8Bw@mail.gmail.com>       (Daniel Drake's message of "Tue, 12 Dec 2017 11:43:15 +0000")

(Adding AceLan)

Daniel Drake <drake@endlessm.com> writes:

> On Wed, Nov 15, 2017 at 7:38 AM, Daniel Drake <drake@endlessm.com> wrote:
>> On Tue, Nov 14, 2017 at 8:15 PM, Kalle Valo <kvalo@qca.qualcomm.com> wro=
te:
>>>> Can't be fixed in firmware, but it would be good to have confirmation
>>>> of the hardware behavivour, and maybe some other solution is possible?
>>>> Are you following this up within Qualcomm?
>>>
>>> No time to do that right now, sorry.
>>
>> I got several autoresponders from people on this thread from Qualcomm
>> Taiwan. Would it be useful for us to drop off a sample of the affected
>> product at your Taipei or Hsinchu office so that you can investigate
>> further?
>
> Ping - how can we collaborate on this?

Are you asking me? While looking at my todo list for this year I doubt I
can find time to help with the MSI implementation or bugfixing.

But my plan is that first I would apply Russel's patch which makes it
possible to enable MSI with a module parameter:

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

Then if AceLan could rebase the quirk patches and resubmit those so that
I can apply those:

https://patchwork.kernel.org/patch/9971097/
https://patchwork.kernel.org/patch/9971095/
https://patchwork.kernel.org/patch/9971093/
https://patchwork.kernel.org/patch/9971091/
https://patchwork.kernel.org/patch/9971089/

Also I don't see the need to have five different patches for the quirks,
having just one patch adding all those should be ok.

Are everyone happy with this plan?

> Also, we have been testing the MSI support patch and while it seems to
> be working fine on AR9565, multiple users hit failures on AR9462. The
> most common report is that the system simply cannot maintain the
> connection with the AP for more than a few seconds. It hits a check in
> mac80211 where it sends a nullfunc to the AP and expects an ack in
> less than 500ms, but it disconnects since it doesn't see the ack.
>
> https://marc.info/?l=3Dlinux-wireless&m=3D151027741010422&w=3D2
>
> We also reproduced a problem in our office with AR9462. With the MSI
> support patch in use, we ping a server every second for 1000 seconds
> while monitoring "iw dev wlp2s0 link" output. With the MSI support
> patch in place, this test fails every time; the connection is dropped
> in less than 1000s.
> With the patch reverted everything is fine.

I'm not really surprised and this is exactly why I was against of
enabling MSI by default. It can cause all sorts of weird problems.

--=20
Kalle Valo=

  reply	other threads:[~2018-01-08 12:24 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 [this message]
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

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=87bmi45yim.fsf@kamboji.qca.qualcomm.com \
    --to=kvalo@qca.qualcomm.com \
    --cc=acelan.kao@canonical.com \
    --cc=aeolus@qti.qualcomm.com \
    --cc=andy@infradead.org \
    --cc=ath9k-devel@qca.qualcomm.com \
    --cc=drake@endlessm.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linux@endlessm.com \
    --cc=rafael.j.wysocki@intel.com \
    --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).