Return-path: Received: from victor.provo.novell.com ([137.65.250.26]:35456 "EHLO victor.provo.novell.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1761841Ab2FVJPn convert rfc822-to-8bit (ORCPT ); Fri, 22 Jun 2012 05:15:43 -0400 Received: by bkcji2 with SMTP id ji2so1345735bkc.19 for ; Fri, 22 Jun 2012 02:15:35 -0700 (PDT) MIME-Version: 1.0 In-Reply-To: References: Date: Fri, 22 Jun 2012 17:15:35 +0800 Message-ID: (sfid-20120622_111545_889962_6F7C1C75) Subject: Re: Atheros [168c 0034] can't enable wireless button LED. From: Matt Chen To: Mohammed Shafi 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: 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 ? > -- > thanks, > shafi > -- Thank you.