Received: by 2002:ac0:946b:0:0:0:0:0 with SMTP id j40csp3661768imj; Tue, 19 Feb 2019 07:21:06 -0800 (PST) X-Google-Smtp-Source: AHgI3IYgdCSmIlAAy+N8467odMs77P+2/OeYSA7WpIwOdCaaCqEY06n1QHYX1Tw2ki4equK9IDcD X-Received: by 2002:a62:a9b:: with SMTP id 27mr29800266pfk.223.1550589666348; Tue, 19 Feb 2019 07:21:06 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1550589666; cv=none; d=google.com; s=arc-20160816; b=wv2kYN8pv36H7mP1BFcXGpV2NsaB6z+Yc1mlpYNR0ltegD7wC9r7O8W4zQbIa3A+qP Bx2iY9UM6PuLcydCKv5mU5sd2TENGl9z5yq+VrFNmTULjPKmR4MG3YxwfOQudiBJdaHX lJbBbRbJJA5Qk10OfP3GBYfqncuXgawlT59qclFyWq8WzEW6nuOPhTsrJ+nL8iXIiEwK +KmOWq/tDXWznc2BubaJwX15MBcCm7sE8RFwoWrgHq3tJlJKfIlYWCspGBryfEiEsEMU flnhU9G3Vu85vpIgZF+5yaUo43cYBw3Ui7UQU/YE1UYn0r4aLch/q8rs4wzGvDq149lB 4KbQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:dkim-signature; bh=n7W4hXLRAODTFAE7Nto58l+PhxCiLdSqgODN+zYO1TE=; b=RpqZC7b3s0ePPlZ2KoGBJf6hdKJO5u9IdNY9i5fBd1nkCKadEjnqeTZ4rfeZttH/Ml jGefy9bBwzaQdNfk9XwCx6c21WRQrRtHtW5Iskj47t+f0eWYh/qvMW2yJWveCK5SAI5c uFA9n4ciKnubZY+3yZDBdTd87iZtwWXm+YmJSJEUckY343B7SWgOZ4q+/ZDjPGbMoWCd k1b5+y1jl6oi0DMsfp8doZGe0S96Z37rrHgHypx/oT0XOi3IEOwYMKaQ0YgL+2DQgIwm g5DHtU2RP2i1KPaF/qGExXRJripAflMv5hCx3lzOx//dRW0izDmLxSlRjImjMFH0x8zT zOcw== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@kernel.org header.s=default header.b=GJa5eUWu; 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=kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id 98si16920573pls.205.2019.02.19.07.20.51; Tue, 19 Feb 2019 07:21:06 -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=@kernel.org header.s=default header.b=GJa5eUWu; 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=kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1729071AbfBSPSg (ORCPT + 99 others); Tue, 19 Feb 2019 10:18:36 -0500 Received: from mail.kernel.org ([198.145.29.99]:34592 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1727170AbfBSPSf (ORCPT ); Tue, 19 Feb 2019 10:18:35 -0500 Received: from mail-qk1-f174.google.com (mail-qk1-f174.google.com [209.85.222.174]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPSA id CD4512177E; Tue, 19 Feb 2019 15:18:34 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1550589515; bh=8ocIakfqk5NNFo2WuTtRy1WckjPnY0q6N5mmUiwiGyQ=; h=References:In-Reply-To:From:Date:Subject:To:Cc:From; b=GJa5eUWuzJ6rbptYr8ytl52ViQysDpRRLUNXSBCShOCicH7NUmUHCRx5CvaMZNPrI lFqQv8uXRzmC32z6622Q8MVQnD0OTtGCWYNiPMLmLJUqnPdlKpPcdvi654MPzMycaJ Zq1RsK9TkxNQaCnB5R1ZdACSW3A75sG+aiMj4Hkc= Received: by mail-qk1-f174.google.com with SMTP id x9so12251895qkf.0; Tue, 19 Feb 2019 07:18:34 -0800 (PST) X-Gm-Message-State: AHQUAuYeGOJEJnhGsqvs9Vdt0CzX88uxOO6dNjNyFy46+Rl+Y44chdaW 0UL/x1NBSI6m/KCOYTFT69gxfwCSPcMNZDpXIA== X-Received: by 2002:a37:4a84:: with SMTP id x126mr21047468qka.326.1550589513982; Tue, 19 Feb 2019 07:18:33 -0800 (PST) MIME-Version: 1.0 References: <20190212064353.7451-1-markz@nvidia.com> <20190212064353.7451-3-markz@nvidia.com> <91d3d8f8-0b96-c442-5674-3eff8209848b@nvidia.com> In-Reply-To: <91d3d8f8-0b96-c442-5674-3eff8209848b@nvidia.com> From: Rob Herring Date: Tue, 19 Feb 2019 09:18:22 -0600 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: [PATCH v3 2/4] mfd: max77620: add documentation for backup battery charging To: Mark Zhang Cc: Bartosz Golaszewski , Lee Jones , Mark Rutland , devicetree@vger.kernel.org, "linux-kernel@vger.kernel.org" , linux-tegra@vger.kernel.org Content-Type: text/plain; charset="UTF-8" Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, Feb 18, 2019 at 8:07 PM 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 > 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. Maybe so, but that's all outside the scope of the binding. Both bindings define charging current and voltage. And other vendor's chargers likely need the same parameters, too. So there's no reason to have different properties. Rob