Received: by 2002:a05:6358:11c7:b0:104:8066:f915 with SMTP id i7csp2178703rwl; Thu, 13 Apr 2023 02:47:58 -0700 (PDT) X-Google-Smtp-Source: AKy350Zy/XTm92RNLomEB1KLgXbKXtza1V1wdjzgmM9J5RQuHKyq3+aJtJ7RrtVz+TCW6T804mRr X-Received: by 2002:a17:906:3a42:b0:947:a6d7:e2b4 with SMTP id a2-20020a1709063a4200b00947a6d7e2b4mr1943323ejf.8.1681379278425; Thu, 13 Apr 2023 02:47:58 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1681379278; cv=none; d=google.com; s=arc-20160816; b=Id5oW1xIuIasZJ7XJ6SMpYAhjLSUFEaVMwMspw4KVU0BlRJAk/SfqZ1fCveUQ66Z8+ uHTCCdyy4bgKWxVZGijiMSvhlWhLis8RZ95udLIkYbh/vZco4LqP/43EAupo4KfQcUEE 1/jiOdBCuik1JWFd2CXQeRg/q+lcTEaHYszyJX4nAEft/Qlfb3pw3lRTLASD+4tPUpGQ IGKAxJfxanhsgrFpYqRQhzs1cl3ambe3rmp+zA8Bfd7d2sqnY1sLijnQTF0Lu5SK+zZo 2wA6zorJKn+3JmY8zrVcPIFycvMc8U5yyU9LiNT4FEy0L0RDMQPsK/SvIW6dvsn3PgUc QGqQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:in-reply-to:content-disposition:mime-version :references:message-id:subject:cc:to:from:date; bh=GA4TVMxdsmtS96KkQdLL7e/FnI4QWjLp5uwNoNcdIMs=; b=w6dz/Mbs1MCfSboHfmbe3V33t5oCE80bfULTyZtVS/bUyEASBTAUJoChk1trIWViMe MEMkkUZ7XiuFUFOaCca6b1y6WCuzY7rsZAbsUB/dii0hjCqk4NYtCbano9s35f2EGim7 wd8U/64lbyVZAMhaXMyu5ZcO13WOZtJL0wqdGZ7vETK3qAktmHzYY6+2xSnvgosDiKXt iLTy8CXQJ2LhbmZn5X/bb0hpvXnGCz41s7wWFV0dUrd0ijay5pJ+0NGXm3BMo5BHzfTc KPmm7ZvMjP9p46iawzPQZNrHTGJy0inJ3v+hyHopsfDR8kys1cjlVbLmIshMuK2DcyoZ cZWw== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id k13-20020a05640212cd00b00501da4e8642si1371704edx.165.2023.04.13.02.47.33; Thu, 13 Apr 2023 02:47:58 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20; Authentication-Results: mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S229904AbjDMJqD (ORCPT + 99 others); Thu, 13 Apr 2023 05:46:03 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:37402 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229965AbjDMJpz (ORCPT ); Thu, 13 Apr 2023 05:45:55 -0400 Received: from muru.com (muru.com [72.249.23.125]) by lindbergh.monkeyblade.net (Postfix) with ESMTP id B26DA9EE2; Thu, 13 Apr 2023 02:45:46 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by muru.com (Postfix) with ESMTPS id BFD6C80F0; Thu, 13 Apr 2023 09:45:45 +0000 (UTC) Date: Thu, 13 Apr 2023 12:45:44 +0300 From: Tony Lindgren To: Pavel Machek Cc: Ivaylo Dimitrov , kernel list , linux-arm-kernel , linux-omap@vger.kernel.org, sre@kernel.org, nekit1000@gmail.com, mpartap@gmx.net, merlijn@wizzup.org, martin_rysavy@centrum.cz, phone-devel@vger.kernel.org, maemo-leste@lists.dyne.org Subject: Re: Motorola Droid 4 -- Stopping charger when battery is full Message-ID: <20230413094544.GD36234@atomide.com> References: <20230309071443.GF7501@atomide.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00,SPF_HELO_NONE, SPF_NONE autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on lindbergh.monkeyblade.net Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org * Pavel Machek [230413 09:37]: > > > * Ivaylo Dimitrov [230307 14:10]: > > > Also, some guys have concerns about charging (and keeping it charged) @4.35, > > > because of the possibly reduced battery life. > > > > Yes for devices connected to a charger for long periods the battery will > > bloat up within some weeks or months. This happens easily when using a > > lapdock for example. > > > > A simple and safe solution here might be that we allow charging up to > > 4.35V only once when the charger is connected. Then we let the voltage > > decrease to 4.2V (or whatever known good maintenance voltage) if the > > charger stays connected. > > Optimum solution would be user specifying "I want battery full > tommorow at 8am" and doing the right thing. I think you can already do that via sysfs with cron or at :) > > For folks wanting to force the charge voltage higher we have the sysfs > > interface. > > Yep, we just need to make sure it is usable for this. It should be but I have not tried for years. You need to first configure the allowed voltage for battery via sysfs, then set the charge voltage for the charger. Regards, Tony