Received: by 2002:ac0:946b:0:0:0:0:0 with SMTP id j40csp3061645imj; Mon, 18 Feb 2019 18:51:09 -0800 (PST) X-Google-Smtp-Source: AHgI3IbE31VN3lD+lGZoUAI0acFCo2Rr++nPWRcOQZ/A7BDGwtTQSKUiiUveKtZxHZs+NLSCXVQW X-Received: by 2002:a63:e84c:: with SMTP id a12mr25489729pgk.241.1550544669439; Mon, 18 Feb 2019 18:51:09 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1550544669; cv=none; d=google.com; s=arc-20160816; b=BaRjaiCQEEgTsILrEXYfyNp6k7euyU2JZhcCHtrKKeNijl3AwXTbzhehBZK8/FLOws MdQ/eegyYmvwAnsmxrD5uHOROM/4+SMGd2zASPK4ENt4l439kEuWPrKBk/NUzFicC4ZP 7QKQek1/1RRtuQ0r5G4McbP/DaHXUSPiGh090fMzi6zH8/lPjGP7+JQrI16r5v0VP7u3 6V6t4iu1N8RSwwB874GnTca6xxvZyBVp9XxFuyJN/S9sMwkZrU/QnRXeeqTl5qHXUzb0 zz4BvgsBwRlTBlRttU5GiNoh7mxbGQ9CTBiRiKv4D0VkRh/eozqAyV2MspjGs70lZhS9 oaxQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:dkim-signature:content-transfer-encoding :content-language:in-reply-to:mime-version:user-agent:date :message-id:references:cc:to:from:subject; bh=l+QX7W8zpi2Ltb5LY3hVoTSMUzGiW1nlP0bUpE54K28=; b=WXioOJ4bWcg1lVL6hO2KJdNpbuT+pawQPUvb6SsMeNB0Oy31zLKjgqioXWYw8B3MmN k29KSbB4N+Xc7sPKsstRZ2Hkngkygg/b5CorYwl4La5EBIh2x9HLPK4uMS+x5hp6iA80 9hf+xLDuKBflQ1VHlWll25IGJ9DZRIMnCtwCadxx6KgY372nnc6Im1L880r0gqfoLwSI JX7eznyfzNE0G2Z5+0SZSowWHdqW6Vw3yiTJZQc3byMg4pvIvmV0U5ZWNLrF32XYa1rH tO6iqwqxY88XzKMRZ9J+a/DkFXm93dgVRRAUwq/7id87jiZ45f7q6X91Z/Vk3ekVAJYq hqVw== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@nvidia.com header.s=n1 header.b=eAZCStvz; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=nvidia.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id y40si16034717pla.251.2019.02.18.18.50.54; Mon, 18 Feb 2019 18:51:09 -0800 (PST) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; dkim=pass header.i=@nvidia.com header.s=n1 header.b=eAZCStvz; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=nvidia.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726798AbfBSCJt (ORCPT + 99 others); Mon, 18 Feb 2019 21:09:49 -0500 Received: from hqemgate16.nvidia.com ([216.228.121.65]:14051 "EHLO hqemgate16.nvidia.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726225AbfBSCJs (ORCPT ); Mon, 18 Feb 2019 21:09:48 -0500 Received: from hqpgpgate101.nvidia.com (Not Verified[216.228.121.13]) by hqemgate16.nvidia.com (using TLS: TLSv1.2, DES-CBC3-SHA) id ; Mon, 18 Feb 2019 18:09:51 -0800 Received: from hqmail.nvidia.com ([172.20.161.6]) by hqpgpgate101.nvidia.com (PGP Universal service); Mon, 18 Feb 2019 18:09:46 -0800 X-PGP-Universal: processed; by hqpgpgate101.nvidia.com on Mon, 18 Feb 2019 18:09:46 -0800 Received: from [192.168.88.246] (172.20.13.39) by HQMAIL101.nvidia.com (172.20.187.10) with Microsoft SMTP Server (TLS) id 15.0.1395.4; Tue, 19 Feb 2019 02:09:44 +0000 Subject: Re: [PATCH v3 2/4] mfd: max77620: add documentation for backup battery charging From: Mark Zhang To: Rob Herring , Bartosz Golaszewski CC: Lee Jones , Mark Rutland , , "linux-kernel@vger.kernel.org" , References: <20190212064353.7451-1-markz@nvidia.com> <20190212064353.7451-3-markz@nvidia.com> <91d3d8f8-0b96-c442-5674-3eff8209848b@nvidia.com> Message-ID: Date: Tue, 19 Feb 2019 10:09:40 +0800 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.5.0 MIME-Version: 1.0 In-Reply-To: <91d3d8f8-0b96-c442-5674-3eff8209848b@nvidia.com> X-Originating-IP: [172.20.13.39] X-ClientProxiedBy: HQMAIL106.nvidia.com (172.18.146.12) To HQMAIL101.nvidia.com (172.20.187.10) Content-Type: text/plain; charset="utf-8" Content-Language: en-US Content-Transfer-Encoding: 7bit DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=nvidia.com; s=n1; t=1550542191; bh=l+QX7W8zpi2Ltb5LY3hVoTSMUzGiW1nlP0bUpE54K28=; h=X-PGP-Universal:Subject:From:To:CC:References:Message-ID:Date: User-Agent:MIME-Version:In-Reply-To:X-Originating-IP: X-ClientProxiedBy:Content-Type:Content-Language: Content-Transfer-Encoding; b=eAZCStvzdtquVwVLmpwhJlzvY6TvXC/+gU/N4N7p81tZ6DunMn1hL+LPknuOlZDJ1 /KXX5f8n8CXafOfZ+agWh82kVjjj8nqpWQ4J79iOS4if1LZiWNhGWdzkgTfMtL65dl Xq2d/vrCDBNKqvIHYYOIIvFYRgDJhV5gBXKiDzCZXU8WEj2esjEK4yzv2T2VwoC51E AjL1piqtQOP74+ZdUO8OuS4bIsUbUHYzB5wLTJMLSLLOmblvqqbPRjVlfeaToSlM95 P2DK18nAQ+wImDAYcp0oYQ+Cx9Bd4tpiQAMHXUv7A5c34ba2UZgo7Is2n7rxeIsem5 HUr3bmlktSFOQ== Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 2/19/2019 10:07 AM, Mark Zhang wrote: > On 2/19/2019 2:06 AM, Rob Herring wrote: >> On Tue, Feb 12, 2019 at 12:44 AM Mark Zhang wrote: >>> >>> Adding documentation for 3 new backup battery charging dts >>> properties: >>> - maxim,charging-current-microamp >>> - maxim,charging-voltage-microvolt >>> - maxim,output-resister-ohms >> >> What's the difference between the 77620 and 77650 as there's patches >> on the list for the 77650 too. The properties are similar, but seems >> to be main vs. backup battery charger. We should have common >> properties for this. > > Rob, it's different. The RTC in max77620 is supplied from a backup > battery and consumes 2.0uA (IBBATT) when no other power sources are > available. So unlike max77620 battery charging, which provides features Oops... s/unlike max77620/unlike max77650. Mark > like: > > static enum power_supply_property max77650_charger_properties[] = { > POWER_SUPPLY_PROP_STATUS, > POWER_SUPPLY_PROP_ONLINE, > POWER_SUPPLY_PROP_CHARGE_TYPE > }; > > For backup battery charging in max77620, what we can do is just setting > those 3 parameters. We don't know whether it's charging, whether the > backup battery is online, the percentage of the charging progress, and > etc. That's why I mentioned before that it's not appropriate to create > it as a power supply driver. > > Mark > >> >>> Signed-off-by: Mark Zhang >>> --- >>> .../devicetree/bindings/mfd/max77620.txt | 20 +++++++++++++++++++ >>> 1 file changed, 20 insertions(+) >>> >>> diff --git a/Documentation/devicetree/bindings/mfd/max77620.txt b/Documentation/devicetree/bindings/mfd/max77620.txt >>> index 9c16d51cc15b..88825eaf2567 100644 >>> --- a/Documentation/devicetree/bindings/mfd/max77620.txt >>> +++ b/Documentation/devicetree/bindings/mfd/max77620.txt >>> @@ -122,6 +122,26 @@ For DT binding details of different sub modules like GPIO, pincontrol, >>> regulator, power, please refer respective device-tree binding document >>> under their respective sub-system directories. >>> >>> +Backup Battery: >>> +============== >>> +This sub-node configure charging backup battery of the device. Device has >>> +support of charging the backup battery. The subnode name is "backup-battery". >>> +The property for backup-battery child nodes as: >>> +Presence of this child node will enable the backup battery charging. >>> + >>> +Optional properties: >>> + -maxim,charging-current-microamp: Charging current setting. >>> + The device supports 50/100/200/400/600/800uA. >>> + If this property is unavailable then it will >>> + charge with 50uA. >>> + -maxim,charging-voltage-microvolt: Charging Voltage Limit Setting. >>> + Device supports 2500000/3000000/3300000/350000uV. >>> + Default will be set to 2500mV. The voltage will be roundoff >>> + to nearest lower side if other than above is configured. >>> + -maxim,output-resister-ohms: Output resistor on Ohm. >>> + Device supports 100/1000/3000/6000 Ohms. >>> + Default will be set to 1000 Ohm. >>> + >>> Example: >>> -------- >>> #include >>> -- >>> 2.19.2 >>>