Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756665AbYKWR0n (ORCPT ); Sun, 23 Nov 2008 12:26:43 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1751528AbYKWR0U (ORCPT ); Sun, 23 Nov 2008 12:26:20 -0500 Received: from gprs189-60.eurotel.cz ([160.218.189.60]:57039 "EHLO UNKNOWN" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1750902AbYKWR0T (ORCPT ); Sun, 23 Nov 2008 12:26:19 -0500 Date: Sun, 23 Nov 2008 13:31:54 +0100 From: Pavel Machek To: Trent Piepho Cc: Richard Purdie , linux-kernel@vger.kernel.org, linuxppc-dev@ozlabs.org, Anton Vorontsov , Sean MacLennan , Wolfram Sang , Grant Likely Subject: Re: [PATCH 4/4] leds: Let GPIO LEDs keep their current state Message-ID: <20081123123154.GB7310@ucw.cz> References: <1224889741-4167-4-git-send-email-tpiepho@freescale.com> <1226933427.17109.15.camel@ted> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.18 (2008-05-17) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1651 Lines: 48 On Thu 2008-11-20 17:05:56, Trent Piepho wrote: > On Mon, 17 Nov 2008, Richard Purdie wrote: > > On Fri, 2008-10-24 at 16:09 -0700, Trent Piepho wrote: > >> + if (template->keep_state) > >> + state = !!gpio_get_value(led_dat->gpio) ^ led_dat->active_low; > >> + else > >> + state = template->default_state; > >> > >> state = of_get_property(child, "default-state", NULL); > >> led.default_state = state && !strcmp(state, "on"); > >> + led.keep_state = state && !strcmp(state, "keep"); > >> > >> +++ b/include/linux/leds.h > >> @@ -138,7 +138,8 @@ struct gpio_led { > >> const char *default_trigger; > >> unsigned gpio; > >> u8 active_low; > >> - u8 default_state; > >> + u8 default_state; /* 0 = off, 1 = on */ > >> + u8 keep_state; /* overrides default_state */ > >> }; > > > > How about something simpler here, just make default state have three > > different values - "keep", "on" and "off"? I'm not keen on having two > > different state variables like this. > > I thought of that, but it ends up being more complex. Instead of just > using: > static const struct gpio_led myled = { > .name = "something", > .keep_state = 1, > } > > You'd do something like this: > .default_state = LEDS_GPIO_DEFSTATE_KEEP, > > Is that better? Yes. -- (english) http://www.livejournal.com/~pavelmachek (cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/