All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Luis R. Rodriguez" <mcgrof@gmail.com>
To: Rajkumar Manoharan <rmanohar@qca.qualcomm.com>
Cc: linville@tuxdriver.com, linux-wireless@vger.kernel.org
Subject: Re: [PATCH 1/9] ath9k: Dump base eeprom header for AR9003
Date: Thu, 28 Jul 2011 14:11:32 -0700	[thread overview]
Message-ID: <CAB=NE6WfMgGQCzWUtdnA70w-u9agG8SS-W=JKL1V0nL8Rq=TEA@mail.gmail.com> (raw)
In-Reply-To: <1311874176-27569-1-git-send-email-rmanohar@qca.qualcomm.com>

On Thu, Jul 28, 2011 at 10:29 AM, Rajkumar Manoharan
<rmanohar@qca.qualcomm.com> wrote:
> Debugfs file location:
> <debugfs_mnt>/ieee80211/phy#/ath9k/base_eeprom
>
> Signed-off-by: Rajkumar Manoharan <rmanohar@qca.qualcomm.com>
> ---
>  drivers/net/wireless/ath/ath9k/debug.c |  147 ++++++++++++++++++++++++++++++++
>  1 files changed, 147 insertions(+), 0 deletions(-)
>
> diff --git a/drivers/net/wireless/ath/ath9k/debug.c b/drivers/net/wireless/ath/ath9k/debug.c
> index d1eb896..df71c72 100644
> --- a/drivers/net/wireless/ath/ath9k/debug.c
> +++ b/drivers/net/wireless/ath/ath9k/debug.c
> @@ -1163,6 +1163,151 @@ static const struct file_operations fops_regdump = {
>        .llseek = default_llseek,/* read accesses f_pos */
>  };
>
> +static ssize_t read_file_base_eeprom(struct file *file, char __user *user_buf,
> +                                    size_t count, loff_t *ppos)
> +{
> +       struct ath_softc *sc = file->private_data;
> +       struct ath_hw *ah = sc->sc_ah;
> +       struct ar9300_base_eep_hdr *pBase = NULL;
> +       unsigned int len = 0, size = 1500;
> +       ssize_t retval = 0;
> +       char *buf;
> +
> +       if (!AR_SREV_9300_20_OR_LATER(ah))
> +               return 0;

This is really really cool stuff, but instead of doing this can we
instead implement this as a callback design which would enable other
hw revisions to be supported? If we do not then we need to make the
code branch out on each type of card.

  Luis

  parent reply	other threads:[~2011-07-28 21:11 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-28 17:29 [PATCH 1/9] ath9k: Dump base eeprom header for AR9003 Rajkumar Manoharan
2011-07-28 17:29 ` [PATCH 2/9] ath9k: Dump modal " Rajkumar Manoharan
2011-07-28 17:29 ` [PATCH 3/9] ath9k: Remove virtual wiphy specific frame type Rajkumar Manoharan
2011-07-28 17:29 ` [PATCH 4/9] ath9k_hw: Fix incorrect Tx control power in AR9003 template Rajkumar Manoharan
2011-07-28 21:12   ` Luis R. Rodriguez
2011-07-29  6:54     ` Rajkumar Manoharan
2011-07-28 17:29 ` [PATCH 5/9] ath9k_hw: Optimize rx descriptor processing for AR9003 Rajkumar Manoharan
2011-07-28 17:29 ` [PATCH 6/9] ath9k_hw: update PMU to improve ripple issue for AR9485 Rajkumar Manoharan
2011-07-28 21:14   ` Luis R. Rodriguez
2011-07-29  7:07     ` Rajkumar Manoharan
2011-07-28 17:29 ` [PATCH 7/9] ath9k_hw: Disable Walsh spatial spreading for 2 chains Rajkumar Manoharan
2011-07-28 21:14   ` Luis R. Rodriguez
2011-07-29  7:09     ` Rajkumar Manoharan
2011-07-28 17:29 ` [PATCH 8/9] ath9k_hw: Update the radio parameters related to high_power Rajkumar Manoharan
2011-07-28 17:29 ` [PATCH 9/9] ath9k_hw: Update AR9003 high_power tx gain table Rajkumar Manoharan
2011-07-28 21:11 ` Luis R. Rodriguez [this message]
2011-07-29  6:46   ` [PATCH 1/9] ath9k: Dump base eeprom header for AR9003 Rajkumar Manoharan

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='CAB=NE6WfMgGQCzWUtdnA70w-u9agG8SS-W=JKL1V0nL8Rq=TEA@mail.gmail.com' \
    --to=mcgrof@gmail.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linville@tuxdriver.com \
    --cc=rmanohar@qca.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.