Return-path: Received: from mail-ob0-f174.google.com ([209.85.214.174]:44455 "EHLO mail-ob0-f174.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751680Ab2FWKmN convert rfc822-to-8bit (ORCPT ); Sat, 23 Jun 2012 06:42:13 -0400 Received: by obbuo13 with SMTP id uo13so3322265obb.19 for ; Sat, 23 Jun 2012 03:42:12 -0700 (PDT) MIME-Version: 1.0 In-Reply-To: References: Date: Sat, 23 Jun 2012 16:12:12 +0530 Message-ID: (sfid-20120623_124216_815684_2C002F82) Subject: Re: Atheros [168c 0034] can't enable wireless button LED. From: Mohammed Shafi To: Matt Chen Cc: ath9k-devel@lists.ath9k.org, linux-wireless Content-Type: text/plain; charset=ISO-8859-1 Sender: linux-wireless-owner@vger.kernel.org List-ID: On Fri, Jun 22, 2012 at 2:45 PM, Matt Chen wrote: > Hi Mohammed, > > 2012/6/20 Mohammed Shafi : >> Hi Matt, >> >>> Both 0x2f and 0x2d can work fine to me of enabling >>> wiphy_rfkill_start_polling() in gpio.c:ath_start_rfkill_poll(). >>> >>> 1) with 0x2f >>> ? 0x404c address would change when press wifi button >>> ? rfkill block : yes -> 0x00000455 >>> ? rfkill block : no ? -> 0x00000c55 >>> 2) with 0x2d >>> ? 0x404c address would change when press wifi button >>> ? rfkill block : yes -> 0x00000455 >>> ? rfkill block : no ? -> 0x00000c55 >>> >>> >>> But I don't see the LED is changing, it is staying OFF (Amber). >> >> not sure about that, but i think rfkill is working for both of us >> i told 0xeed changes to 0x6ed for me >> >> you got 0x455 changes to 0xc55 >> >> BIT 12(GPIO pin 11 seems to toggle ?4 ->C), you can confirm by rfkill list > Would it be the patch to fix it ? or it is just a workaround to prove > the rfkill_poll can be enabled ? ideally, this should have been properly hard coded in the EEPROM stuff itself. i think you got a very brand new AR9462 just when it came to the market :) its a kind of workaround only. -- thanks, shafi