Received: by 2002:ac0:bc90:0:0:0:0:0 with SMTP id a16csp2805628img; Sun, 24 Mar 2019 19:46:35 -0700 (PDT) X-Google-Smtp-Source: APXvYqzmlW6ysO8fOk3Xjp0+tC7B5YdkO/KOzZC7YDTVvEDpHzcyn/JrBU+BQpuo/sxSVNKDLADX X-Received: by 2002:a63:4383:: with SMTP id q125mr19766503pga.370.1553481995493; Sun, 24 Mar 2019 19:46:35 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1553481995; cv=none; d=google.com; s=arc-20160816; b=PvgGAVpYVSBdkvw4HzWdmRc7JJ1jE5rsdUwqW7B+NUwuLbOUP5GSj8DRg9tCRv2GWk XZ74GDvmuX0Y59rZuDPMDlmbkYbkdQZwhRgpiLgrGz5ZMnc06mQv2UR3mT1QpE1n+XuT 30EWyv/1UewEENC784dBDd3Rq4pliAKKvf1kaVLGAMSPuCoBezEBvtKGlGQtvHtiroj3 NN5xsU3W3zoze4fiF/qjiZpnIaV2TkrDBbzGArXvkIT/7uLwKZx6mlSBpTxnmUOt5jjZ ySJ0dOimrmq74HPnD/k43I/xmqz1mssVMV1VBw9WRnCU/4AX8OdZS+WCn5KZ2nb4Dosa tF5g== 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=rS8rDDpmBAbqOPIQdktMy1PhNQumRZTe+e/aIb5w/ZQ=; b=pyWcVDRKEVXcnXwrOq8w2nnl4ZBmWRCgEgFHUaaF+Qj0BvXBofE8dChDcNVIG+OTaC fVzDFNNQOWOXDp3hslVFDkc3sUS4/7XEu85oFP4ZjAFGHM9OPvtrfYAQL4/xa9rR8MZE IXEYej51XnBLdqwbMzeXZBLy4KWrLxvY04qTz8UDW2aG2GsVhxeIeM0ckWMNJr93Xa7r CocCJs2ntfk9xTcaCYrrsTDYzw9HejrF2kTi26Bsy6kEs6HyCfNF1DovicnalFWdan2+ sd/KajbgcRzW1xL8xcEllFRxtBVqM0b4oBcL0BiRx1gSkh8KgJtUJf4aRpfLSe/xOx1A 4V4A== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@kernel.org header.s=default header.b=NZ9dER7W; 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 q61si13892132plb.252.2019.03.24.19.46.09; Sun, 24 Mar 2019 19:46:35 -0700 (PDT) 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=NZ9dER7W; 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 S1729329AbfCYCpO (ORCPT + 99 others); Sun, 24 Mar 2019 22:45:14 -0400 Received: from mail.kernel.org ([198.145.29.99]:42440 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1729154AbfCYCpN (ORCPT ); Sun, 24 Mar 2019 22:45:13 -0400 Received: from mail-wr1-f41.google.com (mail-wr1-f41.google.com [209.85.221.41]) (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 9509A2133F; Mon, 25 Mar 2019 02:45:12 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1553481912; bh=GjnI2BEpx2hjKi1OtnX5B8pSFx7DJWOnCd0dIwqIFYs=; h=References:In-Reply-To:From:Date:Subject:To:Cc:From; b=NZ9dER7WVNPPavbt/F9xodY0NRjFuV/h+hTIvDXi30nPM5GJYqozQFMd1BMZbyozN 4L6dYRYrdsD4n7Uqm7rc9yJUMxfVGfwiJhKn3HFmSL0HI7mVt+mT0cPRRrylj1V3lX wC94Upo82VynZJ6ta0Dh2vz0D1W2FG1K4CJbmEco= Received: by mail-wr1-f41.google.com with SMTP id y7so4185059wrn.11; Sun, 24 Mar 2019 19:45:12 -0700 (PDT) X-Gm-Message-State: APjAAAU1s72/vnua6o35IVU/n4qhU8Y5V1v8pVLJGek4a/Zw+TUHLETW Jvvw+/mfZHvs31OREqWw274UQ7QQIVu0vEiZSWk= X-Received: by 2002:adf:ec11:: with SMTP id x17mr13478902wrn.120.1553481911134; Sun, 24 Mar 2019 19:45:11 -0700 (PDT) MIME-Version: 1.0 References: <20190321084850.20769-1-wens@kernel.org> <20190321084850.20769-4-wens@kernel.org> <20190321093012.kg72voxs5kw5xtzu@flea> In-Reply-To: <20190321093012.kg72voxs5kw5xtzu@flea> From: Chen-Yu Tsai Date: Mon, 25 Mar 2019 10:45:01 +0800 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: [linux-sunxi] Re: [PATCH v3 3/9] power: supply: axp20x_usb_power: allow disabling input current limiting To: Maxime Ripard Cc: Chen-Yu Tsai , Lee Jones , Sebastian Reichel , devicetree , linux-arm-kernel , "open list:THERMAL" , linux-kernel , linux-sunxi , Hans de Goede 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 Thu, Mar 21, 2019 at 5:30 PM Maxime Ripard wrote: > > Hi, > > The rest of the series is > Acked-by: Maxime Ripard > > On Thu, Mar 21, 2019 at 04:48:44PM +0800, Chen-Yu Tsai wrote: > > From: Chen-Yu Tsai > > > > The AXP PMICs allow the user to disable current limiting on the VBUS > > input. While read-out of this setting was already supported by the > > driver, it did not allow the user to configure the PMIC to disable > > current limiting. > > > > Add support for this. > > > > Signed-off-by: Chen-Yu Tsai > > Do we really want to do that though? That could have some pretty bad > consequences. If I understand the manual correctly, the PMIC has two mode of operation with regards to VBUS. Normal operation means the PMIC will try to limit the current draw to maintain VBUS above the set V_hold (defaults to 4.4V). This is in addition to the current limit set in this patch. The other mode of operation is bypass, where it ignores the voltage limit. Not sure if it also ignores the current limit, but probably not. In any case we don't support this mode in the driver. So I can think of a few cases where this might be bad: 1. High current draw results in excessive voltage drop and heating over line / traces due to insufficient conductor area. This should be covered by the voltage holding mechanism. 2. Over taxing the external power supply. This should also result in some voltage drop for simple power bricks. Advanced ones would either have current limiting or over-current protection. What bad consequences are you thinking of? ChenYu