mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Rivera-Matos, Ricardo" <rriveram@opensource.cirrus.com>
To: Sebastian Reichel <sebastian.reichel@collabora.com>
Cc: <linux-pm@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
	<patches@opensource.cirrus.com>
Subject: Re: [RESEND v2 1/2] power: supply: Introduces bypass charging property
Date: Mon, 21 Feb 2022 11:50:35 -0600	[thread overview]
Message-ID: <FF4489C8-87D4-42CB-A347-1DF55A68A2AE@opensource.cirrus.com> (raw)
In-Reply-To: <20220212034400.kg4cy2t6g7espy6n@mercury.elektranox.org>

Hello,

> On Feb 11, 2022, at 9:44 PM, Sebastian Reichel <sebastian.reichel@collabora.com> wrote:
> 
> Hi,
> 
> On Fri, Feb 11, 2022 at 03:46:52PM -0600, Rivera-Matos, Ricardo wrote:
>>> I think your patch description is a good explanation for that file.
>>> Also I obviously missed to point this out for the "Long Life" charge
>>> type, so please also add a sentence for that so that the property
>>> is properly documented.
>> 
>> As I understand it “Long Life” means the charger reduces its
>> charging rate in order to prolong the battery health.
>> 
>> Is this a fit explanation?
> 
> Yes, thanks for taking care of it.

Ack.
> 
> -- Sebastian

Ricardo


  reply	other threads:[~2022-02-21 17:59 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-10 15:41 [RESEND v2 0/2] Introduces bypass charge type property Ricardo Rivera-Matos
2022-02-10 15:41 ` [RESEND v2 1/2] power: supply: Introduces bypass charging property Ricardo Rivera-Matos
2022-02-11 20:43   ` Sebastian Reichel
2022-02-11 21:46     ` Rivera-Matos, Ricardo
2022-02-12  3:44       ` Sebastian Reichel
2022-02-21 17:50         ` Rivera-Matos, Ricardo [this message]
2022-02-10 15:41 ` [RESEND v2 2/2] power: supply: bq25980: Implements POWER_SUPPLY_CHARGE_TYPE_BYPASS Ricardo Rivera-Matos

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=FF4489C8-87D4-42CB-A347-1DF55A68A2AE@opensource.cirrus.com \
    --to=rriveram@opensource.cirrus.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=patches@opensource.cirrus.com \
    --cc=sebastian.reichel@collabora.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®