Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S964974AbWJXDld (ORCPT ); Mon, 23 Oct 2006 23:41:33 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S965071AbWJXDld (ORCPT ); Mon, 23 Oct 2006 23:41:33 -0400 Received: from gate.crashing.org ([63.228.1.57]:19663 "EHLO gate.crashing.org") by vger.kernel.org with ESMTP id S964974AbWJXDlc (ORCPT ); Mon, 23 Oct 2006 23:41:32 -0400 Subject: Re: Battery class driver. From: Benjamin Herrenschmidt To: Matthew Garrett Cc: David Woodhouse , linux-kernel@vger.kernel.org, olpc-dev@laptop.org, davidz@redhat.com, greg@kroah.com, len.brown@intel.com, sfr@canb.auug.org.au In-Reply-To: <20061023182635.GA19139@srcf.ucam.org> References: <1161627633.19446.387.camel@pmac.infradead.org> <20061023182635.GA19139@srcf.ucam.org> Content-Type: text/plain Date: Tue, 24 Oct 2006 13:36:18 +1000 Message-Id: <1161660978.10524.537.camel@localhost.localdomain> Mime-Version: 1.0 X-Mailer: Evolution 2.8.1 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 622 Lines: 17 > The tp_smapi code also provides average current and power, the charge > cycle count, the date of first use, the date of manufacture and controls > for altering the charge behaviour of the battery. Are these things that > should go in the generic class? Also, should we create files for things that the backend doesn't provide ? Seems like a waste of memory to me. Ben - 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/