Return-path: Received: from mail-oi0-f42.google.com ([209.85.218.42]:44197 "EHLO mail-oi0-f42.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750962AbdKOHiW (ORCPT ); Wed, 15 Nov 2017 02:38:22 -0500 Received: by mail-oi0-f42.google.com with SMTP id a75so9832305oib.1 for ; Tue, 14 Nov 2017 23:38:21 -0800 (PST) MIME-Version: 1.0 In-Reply-To: <87bmk5hx9x.fsf@kamboji.qca.qualcomm.com> References: <20171110025415.7854-1-drake@endlessm.com> <87y3na7eei.fsf@qca.qualcomm.com> <87bmk5hx9x.fsf@kamboji.qca.qualcomm.com> From: Daniel Drake Date: Wed, 15 Nov 2017 15:38:20 +0800 Message-ID: (sfid-20171115_083826_260489_10AEDF6B) Subject: Re: [v2] ath9k: add MSI support To: Kalle Valo Cc: Russell Hu , "linux-wireless@vger.kernel.org" , Ryan Hsu , Robert Chang , Aeolus Yang , ath9k-devel , "linux@endlessm.com" , "rafael.j.wysocki@intel.com" , "andy@infradead.org" Content-Type: text/plain; charset="UTF-8" Sender: linux-wireless-owner@vger.kernel.org List-ID: On Tue, Nov 14, 2017 at 8:15 PM, Kalle Valo wrote: >> 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? Thanks Daniel