From mboxrd@z Thu Jan 1 00:00:00 1970 From: Pan, Miaoqing Date: Wed, 01 Jun 2016 07:01:14 -0000 Subject: [ath9k-devel] ath9k gpio request In-Reply-To: <574D3EAA.3060102@gmail.com> References: <20160530132225.4d297678@canb.auug.org.au> <574C4851.9090201@gmail.com> <87fusy3cqx.fsf_-_@kamboji.qca.qualcomm.com>, <574D3EAA.3060102@gmail.com> Message-ID: <1464764036580.70506@qti.qualcomm.com> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: ath9k-devel@lists.ath9k.org which chip ? And what's the GPIO number ? Thanks, Miaoqing ________________________________________ From: Sudip Mukherjee Sent: Tuesday, May 31, 2016 3:35 PM To: Kalle Valo Cc: Stephen Rothwell; ath9k-devel; linux-next at vger.kernel.org; linux-kernel at vger.kernel.org; linux-wireless at vger.kernel.org; ath9k-devel at lists.ath9k.org; netdev at vger.kernel.org; Miaoqing Pan Subject: Re: ath9k gpio request On Tuesday 31 May 2016 01:01 PM, Kalle Valo wrote: > (Changing subject to a more descriptive one, was "Re: linux-next: Tree > for May 30") > > Sudip Mukherjee writes: > >> Hi All, >> I have just built and booted with next-20160530 and my dmesg is full >> of warnings from ath9k. Last kernel tested was v4.6 and there was no >> problem with that. >> > The traces look incomplete to me, is there anything more before the > "Call Trace:" line? Full unedited logs are usually the best. sure, its attached. those two warnings are recursively going on and there is nothing else left in dmesg to see what started it. Regards Sudip From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Pan, Miaoqing" Subject: Re: ath9k gpio request Date: Wed, 1 Jun 2016 06:54:01 +0000 Message-ID: <1464764036580.70506@qti.qualcomm.com> References: <20160530132225.4d297678@canb.auug.org.au> <574C4851.9090201@gmail.com> <87fusy3cqx.fsf_-_@kamboji.qca.qualcomm.com>,<574D3EAA.3060102@gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7BIT Return-path: In-Reply-To: <574D3EAA.3060102@gmail.com> Content-Language: en-US Sender: linux-kernel-owner@vger.kernel.org To: Sudip Mukherjee , Kalle Valo Cc: Stephen Rothwell , ath9k-devel , "linux-next@vger.kernel.org" , "linux-kernel@vger.kernel.org" , "linux-wireless@vger.kernel.org" , "ath9k-devel@lists.ath9k.org" , "netdev@vger.kernel.org" , Miaoqing Pan List-Id: linux-next.vger.kernel.org which chip ? And what's the GPIO number ? Thanks, Miaoqing ________________________________________ From: Sudip Mukherjee Sent: Tuesday, May 31, 2016 3:35 PM To: Kalle Valo Cc: Stephen Rothwell; ath9k-devel; linux-next@vger.kernel.org; linux-kernel@vger.kernel.org; linux-wireless@vger.kernel.org; ath9k-devel@lists.ath9k.org; netdev@vger.kernel.org; Miaoqing Pan Subject: Re: ath9k gpio request On Tuesday 31 May 2016 01:01 PM, Kalle Valo wrote: > (Changing subject to a more descriptive one, was "Re: linux-next: Tree > for May 30") > > Sudip Mukherjee writes: > >> Hi All, >> I have just built and booted with next-20160530 and my dmesg is full >> of warnings from ath9k. Last kernel tested was v4.6 and there was no >> problem with that. >> > The traces look incomplete to me, is there anything more before the > "Call Trace:" line? Full unedited logs are usually the best. sure, its attached. those two warnings are recursively going on and there is nothing else left in dmesg to see what started it. Regards Sudip From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1757526AbcFAGyM (ORCPT ); Wed, 1 Jun 2016 02:54:12 -0400 Received: from wolverine01.qualcomm.com ([199.106.114.254]:53555 "EHLO wolverine01.qualcomm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751197AbcFAGyI convert rfc822-to-8bit (ORCPT ); Wed, 1 Jun 2016 02:54:08 -0400 X-IronPort-AV: E=Sophos;i="5.26,400,1459839600"; d="scan'208";a="197261452" Cc: Stephen Rothwell , ath9k-devel , "linux-next@vger.kernel.org" , "linux-kernel@vger.kernel.org" , "linux-wireless@vger.kernel.org" , "ath9k-devel@lists.ath9k.org" , "netdev@vger.kernel.org" , Miaoqing Pan X-IronPort-AV: E=McAfee;i="5700,7163,8182"; a="1153496339" From: "Pan, Miaoqing" To: Sudip Mukherjee , Kalle Valo Subject: Re: ath9k gpio request Thread-Topic: ath9k gpio request Thread-Index: AQHRuw5qZUYpLTroXEmbqMln9rQM6Z/SIa0AgAIMTrI= Date: Wed, 1 Jun 2016 06:54:01 +0000 Message-ID: <1464764036580.70506@qti.qualcomm.com> References: <20160530132225.4d297678@canb.auug.org.au> <574C4851.9090201@gmail.com> <87fusy3cqx.fsf_-_@kamboji.qca.qualcomm.com>,<574D3EAA.3060102@gmail.com> In-Reply-To: <574D3EAA.3060102@gmail.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-ms-exchange-transport-fromentityheader: Hosted x-originating-ip: [199.106.107.6] Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7BIT MIME-Version: 1.0 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org which chip ? And what's the GPIO number ? Thanks, Miaoqing ________________________________________ From: Sudip Mukherjee Sent: Tuesday, May 31, 2016 3:35 PM To: Kalle Valo Cc: Stephen Rothwell; ath9k-devel; linux-next@vger.kernel.org; linux-kernel@vger.kernel.org; linux-wireless@vger.kernel.org; ath9k-devel@lists.ath9k.org; netdev@vger.kernel.org; Miaoqing Pan Subject: Re: ath9k gpio request On Tuesday 31 May 2016 01:01 PM, Kalle Valo wrote: > (Changing subject to a more descriptive one, was "Re: linux-next: Tree > for May 30") > > Sudip Mukherjee writes: > >> Hi All, >> I have just built and booted with next-20160530 and my dmesg is full >> of warnings from ath9k. Last kernel tested was v4.6 and there was no >> problem with that. >> > The traces look incomplete to me, is there anything more before the > "Call Trace:" line? Full unedited logs are usually the best. sure, its attached. those two warnings are recursively going on and there is nothing else left in dmesg to see what started it. Regards Sudip