From owner-freebsd-bugs@FreeBSD.ORG Sun Apr 14 05:00:00 2013 Return-Path: Delivered-To: freebsd-bugs@smarthost.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id D61C8F9E for ; Sun, 14 Apr 2013 05:00:00 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:1900:2254:206c::16:87]) by mx1.freebsd.org (Postfix) with ESMTP id 6C7C914C for ; Sun, 14 Apr 2013 05:00:00 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.6/8.14.6) with ESMTP id r3E500OK069926 for ; Sun, 14 Apr 2013 05:00:00 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.6/8.14.6/Submit) id r3E500x0069925; Sun, 14 Apr 2013 05:00:00 GMT (envelope-from gnats) Resent-Date: Sun, 14 Apr 2013 05:00:00 GMT Resent-Message-Id: <201304140500.r3E500x0069925@freefall.freebsd.org> Resent-From: FreeBSD-gnats-submit@FreeBSD.org (GNATS Filer) Resent-To: freebsd-bugs@FreeBSD.org Resent-Reply-To: FreeBSD-gnats-submit@FreeBSD.org, adrian chadd Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 6A85CF61 for ; Sun, 14 Apr 2013 04:51:34 +0000 (UTC) (envelope-from nobody@FreeBSD.org) Received: from red.freebsd.org (red.freebsd.org [IPv6:2001:4f8:fff6::22]) by mx1.freebsd.org (Postfix) with ESMTP id 5983A12E for ; Sun, 14 Apr 2013 04:51:34 +0000 (UTC) Received: from red.freebsd.org (localhost [127.0.0.1]) by red.freebsd.org (8.14.5/8.14.5) with ESMTP id r3E4pYYa036449 for ; Sun, 14 Apr 2013 04:51:34 GMT (envelope-from nobody@red.freebsd.org) Received: (from nobody@localhost) by red.freebsd.org (8.14.5/8.14.5/Submit) id r3E4pYWQ036442; Sun, 14 Apr 2013 04:51:34 GMT (envelope-from nobody) Message-Id: <201304140451.r3E4pYWQ036442@red.freebsd.org> Date: Sun, 14 Apr 2013 04:51:34 GMT From: adrian chadd To: freebsd-gnats-submit@FreeBSD.org X-Send-Pr-Version: www-3.1 Subject: misc/177847: [ath] With TPC enabled, TX power values aren't clamped to the hardware maximum X-BeenThere: freebsd-bugs@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 14 Apr 2013 05:00:00 -0000 >Number: 177847 >Category: misc >Synopsis: [ath] With TPC enabled, TX power values aren't clamped to the hardware maximum >Confidential: no >Severity: non-critical >Priority: low >Responsible: freebsd-bugs >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Sun Apr 14 05:00:00 UTC 2013 >Closed-Date: >Last-Modified: >Originator: adrian chadd >Release: >Organization: >Environment: -HEAD >Description: When TPC is enabled, the PHY doesn't necessarily clamp the TX power limit at the value programmed into the per-rate TX power registers. For 11n chips, the HT20 and HT40 rates have a different adjustment to the programmed TX power values. Thus when doing TPC, the TX descriptor TX power register needs to be adjusted by that factor. For later series chips (AR9280 and later), the TX descriptor TX power values need to be adjusted to account for the PHY minimum TX power being -2.5dBm, rather than 0 dBm (ie, instead of 0 == 0 dBm, 0 == -2.5dBm.) For later later chips (AR9285), there are some differences between TX power levels for CCK, OFDM and HT rates. >How-To-Repeat: Enable TPC, see things go haywire. >Fix: >Release-Note: >Audit-Trail: >Unformatted: