All of lore.kernel.org
 help / color / mirror / Atom feed
From: Luis R. Rodriguez <lrodriguez@atheros.com>
To: ath9k-devel@lists.ath9k.org
Subject: [ath9k-devel] [PATCH 2/2] ath9k_hw: Fix AR_GPIO_INPUT_EN_VAL_BT_PRIORITY_BB	and its shift value in 0x4054
Date: Fri, 13 Nov 2009 09:14:38 -0800	[thread overview]
Message-ID: <20091113171438.GD3865@tux> (raw)
In-Reply-To: <1258102960-22768-2-git-send-email-vasanth@atheros.com>

On Fri, Nov 13, 2009 at 01:02:40AM -0800, Vasanth Thiagarajan wrote:
> The bit value of AR_GPIO_INPUT_EN_VAL_BT_PRIORITY_BB is wrong, it should
> be 0x400 and the number of bits to be right shifted is 10. Having this
> wrong value in 0x4054 sometimes affects bt quality on btcoex environment.
> 
> Signed-off-by: Vasanthakumar Thiagarajan <vasanth@atheros.com>

These both seem small enough and reasonable for stable fixes no?
Although I didn't get the impact of the first one..

  Luis

WARNING: multiple messages have this Message-ID (diff)
From: "Luis R. Rodriguez" <lrodriguez@atheros.com>
To: Vasanth Thiagarajan <Vasanth.Thiagarajan@Atheros.com>
Cc: "linville@tuxdriver.com" <linville@tuxdriver.com>,
	"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
	Luis Rodriguez <Luis.Rodriguez@Atheros.com>,
	Jouni Malinen <Jouni.Malinen@Atheros.com>,
	"ath9k-devel@lists.ath9k.org" <ath9k-devel@lists.ath9k.org>
Subject: Re: [PATCH 2/2] ath9k_hw: Fix AR_GPIO_INPUT_EN_VAL_BT_PRIORITY_BB and its shift value in 0x4054
Date: Fri, 13 Nov 2009 09:14:38 -0800	[thread overview]
Message-ID: <20091113171438.GD3865@tux> (raw)
In-Reply-To: <1258102960-22768-2-git-send-email-vasanth@atheros.com>

On Fri, Nov 13, 2009 at 01:02:40AM -0800, Vasanth Thiagarajan wrote:
> The bit value of AR_GPIO_INPUT_EN_VAL_BT_PRIORITY_BB is wrong, it should
> be 0x400 and the number of bits to be right shifted is 10. Having this
> wrong value in 0x4054 sometimes affects bt quality on btcoex environment.
> 
> Signed-off-by: Vasanthakumar Thiagarajan <vasanth@atheros.com>

These both seem small enough and reasonable for stable fixes no?
Although I didn't get the impact of the first one..

  Luis

  reply	other threads:[~2009-11-13 17:14 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-13  9:02 [ath9k-devel] [PATCH 1/2] ath9k_hw: Fix possible OOB array indexing in gen_timer_index[] on 64-bit Vasanthakumar Thiagarajan
2009-11-13  9:02 ` Vasanthakumar Thiagarajan
2009-11-13  9:02 ` [ath9k-devel] [PATCH 2/2] ath9k_hw: Fix AR_GPIO_INPUT_EN_VAL_BT_PRIORITY_BB and its shift value in 0x4054 Vasanthakumar Thiagarajan
2009-11-13  9:02   ` Vasanthakumar Thiagarajan
2009-11-13 17:14   ` Luis R. Rodriguez [this message]
2009-11-13 17:14     ` Luis R. Rodriguez
2009-11-16  7:20     ` [ath9k-devel] " Vasanthakumar Thiagarajan
2009-11-16  7:20       ` Vasanthakumar Thiagarajan
2009-11-16 15:36       ` [ath9k-devel] " Luis R. Rodriguez
2009-11-16 15:36         ` Luis R. Rodriguez

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=20091113171438.GD3865@tux \
    --to=lrodriguez@atheros.com \
    --cc=ath9k-devel@lists.ath9k.org \
    /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.