From owner-freebsd-wireless@FreeBSD.ORG Fri Jan 11 22:19:45 2013 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id D37DFEE0 for ; Fri, 11 Jan 2013 22:19:45 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-wi0-f174.google.com (mail-wi0-f174.google.com [209.85.212.174]) by mx1.freebsd.org (Postfix) with ESMTP id 59A5A69B for ; Fri, 11 Jan 2013 22:19:44 +0000 (UTC) Received: by mail-wi0-f174.google.com with SMTP id hq4so146078wib.1 for ; Fri, 11 Jan 2013 14:19:38 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=UGXVae2hnQpw5Yc8Pyjth/b7+4XjsfJ15+1dG4y4Bys=; b=J564oJJZcoTCYjfrcqeo/MppB82cuLo1fJCmv5rNMJx2/R/7m63I8ETfTfl4KbYsAl rXnCmkkD3lANAi8+QoR0YVYwCNm697niUdIY5OCUXKOawJHDuIW+uwXMAmZ+PbtPfP03 nSjF4l8fwbT2GZk8CXn3/FA6LWcIq4nPcSqFuxamqnC8vaTBJ3wq58jR9xixAmYeW1ir Teh4VJekFibtZIUcPOt5uq/pFHmJzFLSELYggfzhV4K2kyGGoVPMVHDqI7qKS/fKr9fx uKYwkxKIK/EkVh+sOVIBtlPs2RC+BMY92sTnJtjWmQBJMUgqYABrTZWetqzNQDflEdo0 mvDA== MIME-Version: 1.0 Received: by 10.180.100.163 with SMTP id ez3mr651278wib.32.1357942778699; Fri, 11 Jan 2013 14:19:38 -0800 (PST) Received: by 10.217.57.9 with HTTP; Fri, 11 Jan 2013 14:19:38 -0800 (PST) In-Reply-To: <20130111075136.GA67643@zxy.spb.ru> References: <20130109121613.GO1967@zxy.spb.ru> <50edf68e.ec05320a.6ea9.ffff8ee4@mx.google.com> <20130110080729.GQ1967@zxy.spb.ru> <20130111075136.GA67643@zxy.spb.ru> Date: Fri, 11 Jan 2013 14:19:38 -0800 Message-ID: Subject: Re: Atheros 9220 don't return from S3 state From: Adrian Chadd To: Slawa Olhovchenkov Content-Type: text/plain; charset=ISO-8859-1 Cc: "freebsd-wireless@freebsd.org" X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 11 Jan 2013 22:19:45 -0000 .. so there's no _specific_ code being run when it goes to sleep or comes back from sleep for the 11n PCI NICs (AR5416, AR9160, AR9220, AR9227..) .. there's some code to tinker with the internal reset line(s) that force the hardware to re-initialise, but that's not appropriate for you. The problem here is: * it probe/attches fine; * you go to sleep; * you come back from sleep; * the PCI registers seem to be all 0xffffffff; which means the slot or the card is entirely asleep. So it's not something I can do when the NIC comes back - there's likely something that needs to happen to the PCI interface inside the AR9220 before you put the chip to sleep. And I don't (yet) have anything like that in the driver(s) that I've seen internally. But we need to first eliminate that it's the specific slot in question.. does Linux work right? adrian