Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932153Ab0FAUjM (ORCPT ); Tue, 1 Jun 2010 16:39:12 -0400 Received: from smtp1.linux-foundation.org ([140.211.169.13]:44023 "EHLO smtp1.linux-foundation.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S932130Ab0FAUjI (ORCPT ); Tue, 1 Jun 2010 16:39:08 -0400 Date: Tue, 1 Jun 2010 13:38:51 -0700 From: Andrew Morton To: Daniel Mack Cc: Hemanth V , linux-kernel@vger.kernel.org, linux-omap@vger.kernel.org, Jonathan Cameron , Wolfram Sang Subject: Re: [PATCH V2] misc : ROHM BH1780GLI Ambient light sensor Driver Message-Id: <20100601133851.76adbe17.akpm@linux-foundation.org> In-Reply-To: <20100601202715.GV2695@buzzloop.caiaq.de> References: <39216.10.24.255.17.1274699065.squirrel@dbdmail.itg.ti.com> <20100601131244.7164b43c.akpm@linux-foundation.org> <20100601202715.GV2695@buzzloop.caiaq.de> X-Mailer: Sylpheed 2.4.8 (GTK+ 2.12.9; x86_64-pc-linux-gnu) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1675 Lines: 38 On Tue, 1 Jun 2010 22:27:15 +0200 Daniel Mack wrote: > On Tue, Jun 01, 2010 at 01:12:44PM -0700, Andrew Morton wrote: > > On Mon, 24 May 2010 16:34:25 +0530 (IST) > > "Hemanth V" wrote: > > > > > This patch adds support for ROHM BH1780GLI Ambient light sensor. > > > > > > BH1780 supports I2C interface. Driver supports read/update of power state and > > > read of lux value (through SYSFS). Writing value 3 to power_state enables the > > > sensor and current lux value could be read. > > > > There are at least two other ambient light sensor drivers: > > drivers/misc/isl29003.c and drivers/misc/tsl2550.c. > > > > Is there any standardisation of the ABIs whcih these drivers offer? If > > so, does this new driver comply with that? > > Jonathan proposed the ALS framework for these type of devices, but it > was rejected (don't know about the reasons, I didn't follow the > discussions). The new idea is to put such drivers in the industrial IO > subsystem, but I don't know how mature that approach is currently. > > For the time being, these drivers cook up whatever sysfs interface they > like, and their userspace ABIs are not standardized, unfortunately. Well can we fix that? Look at the existing drivers, pick one and make this new driver provide the same interface? It's not a grand plan - more of an incremental baby step, but it's better than this random proliferation. -- 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/