Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S261702AbVEVHE6 (ORCPT ); Sun, 22 May 2005 03:04:58 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S261755AbVEVHE5 (ORCPT ); Sun, 22 May 2005 03:04:57 -0400 Received: from smtp815.mail.sc5.yahoo.com ([66.163.170.1]:55186 "HELO smtp815.mail.sc5.yahoo.com") by vger.kernel.org with SMTP id S261702AbVEVHEz (ORCPT ); Sun, 22 May 2005 03:04:55 -0400 From: Dmitry Torokhov To: Jean Delvare Subject: Re: [lm-sensors] [PATCH 2.6.12-rc4 15/15] drivers/i2c/chips/adm1026.c: use dynamic sysfs callbacks Date: Sun, 22 May 2005 02:04:52 -0500 User-Agent: KMail/1.8 Cc: LM Sensors , Greg KH , LKML References: <20050519213551.GA806@kroah.com> <200505212058.14851.dtor_core@ameritech.net> <20050522085026.40e73d49.khali@linux-fr.org> In-Reply-To: <20050522085026.40e73d49.khali@linux-fr.org> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200505220204.52907.dtor_core@ameritech.net> Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1528 Lines: 37 On Sunday 22 May 2005 01:50, Jean Delvare wrote: > Hi Dmitry, > > > I really think that as far as I2C subsystem goes instead of creating > > arrays of attributes we should move in direction of drivers > > registering individual sensor class devices. So for example it87 would > > register 3 fans, 3 temp, sensors and 8 voltage sensors... > > First, it's a matter of hardware monitoring drivers, not i2c subsystem > (both are tightly binded at the moment but I'd like this to change). > Right, it's just i2c is pretty much the only supplier of these for now. > Second, not all devices have the same attributes for a temperature, fan > or voltage channel. Sure there are commonly found feature sets, but some > channels will lack some feature (e.g. it87's in8 has no min and max > limits), other chips will provide additional features (extra limits or > enhanced configurability). So I don't think you can have all devices > (and thus all drivers) fit into a single sensor class. > Well, userspace code manages it somehow, plus nothing stops driver from adding some additional attributes to class devices. > But of course I can be convinced your approach is better, with patches. Heh, I was afraid you'd say so... Input sysfs conversion first and then we'll see... -- Dmitry - 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/