Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756441AbYG1TQT (ORCPT ); Mon, 28 Jul 2008 15:16:19 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1752033AbYG1TQJ (ORCPT ); Mon, 28 Jul 2008 15:16:09 -0400 Received: from az33egw02.freescale.net ([192.88.158.103]:48707 "EHLO az33egw02.freescale.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751529AbYG1TQI (ORCPT ); Mon, 28 Jul 2008 15:16:08 -0400 Date: Mon, 28 Jul 2008 12:11:01 -0700 (PDT) From: Trent Piepho X-X-Sender: xyzzy@t2.domain.actdsltmp To: Anton Vorontsov cc: Grant Likely , linux-kernel@vger.kernel.org, Richard Purdie , Stephen Rothwell , Kumar Gala , linuxppc-dev@ozlabs.org Subject: Re: [PATCH 2/2] leds: Support OpenFirmware led bindings In-Reply-To: <20080728185103.GA25343@polina.dev.rtsoft.ru> Message-ID: References: <1217019705-24244-2-git-send-email-tpiepho@freescale.com> <20080727022116.GN12191@secretlab.ca> <20080728170914.GA21265@secretlab.ca> <20080728180204.GA13190@polina.dev.rtsoft.ru> <20080728185103.GA25343@polina.dev.rtsoft.ru> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 2661 Lines: 65 On Mon, 28 Jul 2008, Anton Vorontsov wrote: > On Mon, Jul 28, 2008 at 11:26:28AM -0700, Trent Piepho wrote: >> On Mon, 28 Jul 2008, Anton Vorontsov wrote: >>> On Mon, Jul 28, 2008 at 11:09:14AM -0600, Grant Likely wrote: >>> [...] >>>>>>> +- function : (optional) This parameter, if present, is a string >>>>>>> + defining the function of the LED. It can be used to put the LED >>>>>>> + under software control, e.g. Linux LED triggers like "heartbeat", >>>>>>> + "ide-disk", and "timer". Or it could be used to attach a hardware >>>>>>> + signal to the LED, e.g. a SoC that can configured to put a SATA >>>>>>> + activity signal on a GPIO line. >>>>>> >>>>>> This makes me nervous. It exposes Linux internal implementation details >>>>>> into the device tree data. If you want to have a property that >>>>>> describes the LED usage, then the possible values and meanings should be >>>>>> documented here. >>>>> >>>>> Should it be a linux specific property then? I could list all the current >>>>> linux triggers, but enumerating every possible function someone might want >>>>> to assign to an LED seems hopeless. >>>> >>>> I'd rather see the device tree provide 'hints' toward the expected usage >>>> and if a platform needs something specific, then the platform specific >>>> code should setup the trigger. >>>> >>> Maybe we can encode leds into devices themselves, via phandles? >> >> How will this work for anything besides ide activity? For example, flashing, >> heartbeat, default on, overheat, fan failed, kernel panic, etc. > > Everything is possible, but will look weird. For example, > > Default on (power led) could be encoded in the root node. > fan and overheat in a PM controller's node. > Kernel panic in the chosen node. What about flashing? What if the sensor chip isn't an OF device? >>> And then the OF GPIO LEDs driver could do something like: >>> >>> char *ide_disk_trigger_compatibles[] = { >>> "fsl,sata", >>> "ide-generic", >>> ... >>> }; >> >> Everytime someone added a new ide driver, this table would have to be updated. > > Yes. device_type would be helpful here. :-) > > > Well, otherwise, we could provide a trigger map in the chosen node: > > chosen { > /* leds map: default-on, ide-disk, nand-disk, panic */ > linux,leds = <&green_led &red_led 0 0>; > }; What if you have multiple leds that you want to be default on? What happens when new functions are added? -- 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/