Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755310AbaGNNFY (ORCPT ); Mon, 14 Jul 2014 09:05:24 -0400 Received: from atrey.karlin.mff.cuni.cz ([195.113.26.193]:34739 "EHLO atrey.karlin.mff.cuni.cz" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754492AbaGNNFR (ORCPT ); Mon, 14 Jul 2014 09:05:17 -0400 Date: Mon, 14 Jul 2014 15:05:16 +0200 From: Pavel Machek To: Jenny TC Cc: linux-kernel@vger.kernel.org, Sebastian Reichel , Dmitry Eremin-Solenikov , Stephen Rothwell , Anton Vorontsov , David Woodhouse , David Cohen , Pallala Ramakrishna Subject: Re: [PATCH 1/4] power_supply: Add inlmt,iterm, min/max temp props Message-ID: <20140714130516.GB18934@amd.pavel.ucw.cz> References: <1404799461-26345-1-git-send-email-jenny.tc@intel.com> <1404799461-26345-2-git-send-email-jenny.tc@intel.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1404799461-26345-2-git-send-email-jenny.tc@intel.com> User-Agent: Mutt/1.5.20 (2009-06-14) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue 2014-07-08 11:34:18, Jenny TC wrote: > Add new power supply properties for input current, charge termination > current, min and max temperature > > POWER_SUPPLY_PROP_TEMP_MIN - minimum operatable temperature > POWER_SUPPLY_PROP_TEMP_MAX - maximum operatable temperature > > POWER_SUPPLY_PROP_INPUT_CURRENT_LIMIT - input current limit programmed > by charger. Indicates the input current for a charging source. > > POWER_SUPPLY_PROP_CHARGE_TERM_CURRENT - Charge termination current used > to detect the end of charge condition > > Signed-off-by: Jenny TC Acked-by: Pavel Machek -- (english) http://www.livejournal.com/~pavelmachek (cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html -- 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/