From: Sudip Mukherjee <sudipm.mukherjee@gmail.com>
To: "Pan, Miaoqing" <miaoqing@qti.qualcomm.com>,
Kalle Valo <kvalo@codeaurora.org>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
ath9k-devel <ath9k-devel@qualcomm.com>,
"linux-next@vger.kernel.org" <linux-next@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
"ath9k-devel@lists.ath9k.org" <ath9k-devel@venema.h4ckr.net>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
Miaoqing Pan <miaoqing@codeaurora.org>
Subject: Re: ath9k gpio request
Date: Wed, 01 Jun 2016 16:42:49 +0530 [thread overview]
Message-ID: <574EC331.1080901@gmail.com> (raw)
In-Reply-To: <1464764036580.70506@qti.qualcomm.com>
On Wednesday 01 June 2016 12:24 PM, Pan, Miaoqing wrote:
> which chip ? And what's the GPIO number ?
lspci -v reports:
09:00.0 Network controller: Qualcomm Atheros AR9462 Wireless Network
Adapter (rev 01)
Subsystem: Foxconn International, Inc. Device e052
Flags: bus master, fast devsel, latency 0, IRQ 19
Memory at c0500000 (64-bit, non-prefetchable) [size=512K]
Expansion ROM at c0580000 [disabled] [size=64K]
Capabilities: [40] Power Management version 2
Capabilities: [50] MSI: Enable- Count=1/4 Maskable+ 64bit+
Capabilities: [70] Express Endpoint, MSI 00
Capabilities: [100] Advanced Error Reporting
Capabilities: [140] Virtual Channel
Capabilities: [160] Device Serial Number 00-00-00-00-00-00-00-00
Kernel driver in use: ath9k
Any easy way to find out the gpio number or i can modify the module to
find that out.
Regards
Sudip
next prev parent reply other threads:[~2016-06-01 15:43 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-30 3:22 linux-next: Tree for May 30 Stephen Rothwell
2016-05-30 14:04 ` Sudip Mukherjee
2016-05-31 7:31 ` ath9k gpio request Kalle Valo
2016-05-31 7:35 ` Sudip Mukherjee
2016-06-01 6:54 ` Pan, Miaoqing
2016-06-01 11:12 ` Sudip Mukherjee [this message]
2016-06-01 12:18 ` Sudip Mukherjee
2016-06-02 8:02 ` Pan, Miaoqing
2016-06-02 9:01 ` Janusz Dziedzic
2016-06-02 11:39 ` Sudip Mukherjee
2016-06-03 5:33 ` Kalle Valo
2016-06-03 5:49 ` Pan, Miaoqing
2016-06-04 14:37 ` Kalle Valo
2016-06-05 17:40 ` Sudip Mukherjee
2016-06-07 11:43 ` Kalle Valo
2016-06-06 1:51 ` Pan, Miaoqing
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=574EC331.1080901@gmail.com \
--to=sudipm.mukherjee@gmail.com \
--cc=ath9k-devel@qualcomm.com \
--cc=ath9k-devel@venema.h4ckr.net \
--cc=kvalo@codeaurora.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=miaoqing@codeaurora.org \
--cc=miaoqing@qti.qualcomm.com \
--cc=netdev@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
/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).