Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751469AbZLDFZC (ORCPT ); Fri, 4 Dec 2009 00:25:02 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1751181AbZLDFZA (ORCPT ); Fri, 4 Dec 2009 00:25:00 -0500 Received: from cantor.suse.de ([195.135.220.2]:57595 "EHLO mx1.suse.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751081AbZLDFY7 (ORCPT ); Fri, 4 Dec 2009 00:24:59 -0500 Date: Thu, 3 Dec 2009 21:20:56 -0800 From: Greg KH To: Jonathan Cameron Cc: Jean Delvare , Amit Kucheria , List Linux Kernel , rui.zhang@intel.com, alan@linux.intel.com, linux-acpi@vger.kernel.org Subject: Re: [PATCH 2/2] als: add unique device-ids to the als device class Message-ID: <20091204052056.GA16660@suse.de> References: <1259237081-4403-1-git-send-email-amit.kucheria@verdurent.com> <1259237186-5459-1-git-send-email-amit.kucheria@verdurent.com> <20091126160713.5e19eb04@hyperion.delvare> <4B0EB891.4010309@cam.ac.uk> <20091126180646.GA9059@suse.de> <4B0ECB84.9010503@cam.ac.uk> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4B0ECB84.9010503@cam.ac.uk> User-Agent: Mutt/1.5.17 (2007-11-01) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1906 Lines: 36 On Thu, Nov 26, 2009 at 06:40:04PM +0000, Jonathan Cameron wrote: > Greg KH wrote: > > On Thu, Nov 26, 2009 at 05:19:13PM +0000, Jonathan Cameron wrote: > >>> That being said... If we want user-space to know what device is there, > >>> we may want to still let drivers pass a name string to > >>> als_device_register() and let the ALS core create a "name" sysfs > >>> attribute returning the string in question. This would be much lighter > >>> (for individual drivers) than the previous situation, as the string in > >>> question would be a constant (e.g. "TSL2550".) Opinions? > >>> > >> Makes sense given we want all drivers to support some form of identification. > >> We could do it by stating they will all have that attribute, but given it's constant > >> will save repetition to put it in the driver. Conversely it might complicate the handling > >> of subsequent attribute_groups so I'd probably favour adding relevant documentation lines > >> and leaving it up to the drivers to implement this attribute. > >> > >> Thus we'd require (within reason) all drivers to have illuminance0 and name. > > > > Why have a name attribute when you can just use the name of the device > > itself instead? Isn't that what it is there for? > Could do, though I'm not entirely sure all bus types are implementing a name > attribute (I may be wrong, but I don't think spi does for example though it might > have gone in with the recent device table stuff). We could just specify that it > should be present for the device. ah, sorry, I was thinking of the name of the actual device, which is the bus id here. Nevermind, I'll go back to feeling stupid... greg k-h -- 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/