From: Sujith Manoharan <c_manoha@qca.qualcomm.com>
To: Mohammed Shafi <shafi.wireless@gmail.com>
Cc: <linux-wireless@vger.kernel.org>, <ath9k-devel@lists.ath9k.org>
Subject: Re: [RFC/WIP 09/22] ath9k: Initialize BTCOEX scheme using a helper
Date: Tue, 21 Feb 2012 19:43:00 +0530 [thread overview]
Message-ID: <20291.42604.545286.901746@gargle.gargle.HOWL> (raw)
In-Reply-To: <CAD2nsn2bPffcbPcJAn1BG25Q-XTR8sJCHFwh_siGmneme7JpYQ@mail.gmail.com>
Mohammed Shafi wrote:
> is it possible to move it to gpio.c, except we are initializing btcoex
> related GPIO pins so logically gpio.c could be a good idea. pls let me
> know if i had missed something
The coex parameters in ath_hw are initialized, so btcoex.c is okay.
Sujith
prev parent reply other threads:[~2012-02-21 14:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-21 9:22 [RFC/WIP 09/22] ath9k: Initialize BTCOEX scheme using a helper Sujith Manoharan
2012-02-21 11:11 ` Mohammed Shafi
2012-02-21 14:13 ` Sujith Manoharan [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=20291.42604.545286.901746@gargle.gargle.HOWL \
--to=c_manoha@qca.qualcomm.com \
--cc=ath9k-devel@lists.ath9k.org \
--cc=linux-wireless@vger.kernel.org \
--cc=shafi.wireless@gmail.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).