From mboxrd@z Thu Jan 1 00:00:00 1970 From: Johannes Berg Subject: Re: [PATCH] asus-wmi: explicitly set the wireless LED Date: Thu, 15 Dec 2011 09:22:20 +0100 Message-ID: <1323937340.3337.3.camel@jlt3.sipsolutions.net> References: <1323244922-2673-1-git-send-email-kengyu@canonical.com> (sfid-20111215_080747_060859_05239F9D) Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: (sfid-20111215_080747_060859_05239F9D) List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: acpi4asus-user-bounces-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org To: Corentin Chary Cc: Richard, Keng-Yu Lin , acpi4asus-user-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org, linux-wireless-u79uwXL29TY76Z2rM5mHXA@public.gmane.org, linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org, platform-driver-x86-u79uwXL29TY76Z2rM5mHXA@public.gmane.org, Purdie , Matthew Garrett List-Id: platform-driver-x86.vger.kernel.org On Thu, 2011-12-15 at 08:07 +0100, Corentin Chary wrote: > Anyway, you should use a led trigger for that, ideally the rfkill%d > led trigger, but for that you need the rfkill idx, which is not > exported, so you may need a new rfkill_idx() function. CCing rfkill > and led guys, they may have a better advice on that. Since you wouldn't want to build the string yourself, you'd probably want a new rfkill_ledtrigname() function like this: static const char *rfkill_ledtrigname(struct rfkill *rfkill) { #ifdef CONFIG_RFKILL_LEDS return rfkill->ledtrigname; #endif return NULL; } which you use to assign the LED class device's default trigger. johannes ------------------------------------------------------------------------------ 10 Tips for Better Server Consolidation Server virtualization is being driven by many needs. But none more important than the need to reduce IT complexity while improving strategic productivity. Learn More! http://www.accelacomm.com/jaw/sdnl/114/51507609/