platform-driver-x86.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Hans de Goede <hdegoede@redhat.com>
To: "Thomas Koch" <linrunner@gmx.net>,
	"Nicolò Piazzalunga" <nicolopiazzalunga@gmail.com>,
	"Mark Pearson" <markpearson@lenovo.com>,
	platform-driver-x86@vger.kernel.org,
	"Nitin Joshi1" <njoshi1@lenovo.com>,
	"Sebastian Reichel" <sre@kernel.org>,
	"Bastien Nocera" <hadess@hadess.net>,
	"Benjamin Berg" <bberg@redhat.com>
Cc: jwrdegoede@fedoraproject.org, smclt30p@gmail.com
Subject: Re: [PATCH 1/3] thinkpad_acpi: add support for force_discharge
Date: Wed, 29 Sep 2021 12:56:34 +0200	[thread overview]
Message-ID: <d486c621-2464-8763-553b-3543d0578b58@redhat.com> (raw)
In-Reply-To: <a6c448f7-d0c5-2652-46df-590085b47bd1@gmx.net>

Hi,

On 9/29/21 12:45 PM, Thomas Koch wrote:
> Hi Hans,
> 
> 
> On 29.09.21 11:55, Hans de Goede wrote:
> 
>> Hi,
> 
>>
> 
>> On 9/29/21 7:47 AM, Thomas Koch wrote:
> 
>>> Hi Hans,
> 
>>>
> 
>>> On 27.09.21 17:12, Hans de Goede wrote:
> 
>>>> Hi Nicolò,
> 
>>>>
> 
>>>> On 9/27/21 5:00 PM, Nicolò Piazzalunga wrote:
> 
>>>>> Hi,
> 
>>>>>
> 
>>>>> On 9/27/21 3:59 PM, Mark Pearson wrote:
> 
>>>>>> Do let me know if there are some important use cases for these so
> I can go back to the FW team and discuss supporting them properly.
> 
>>>>>
> 
>>>>> The important use cases are force discharge and inhibit charge.
> 
>>>>> These at present are dealt with using tpacpi-bat, which relies on
> (out of tree) acpi_call.
> 
>>>>> See also your previous reply.
> 
>>>>
> 
>>>> I can see how those can be useful in certain circumstances.
> 
>>>>
> 
>>>> I can also understand how Lenovo does not want these to be
> 
>>>> available by default everywhere.
> 
>>>>
> 
>>>> I think a good compromise would be to add a bool module option
> 
>>>> which defaults to false to enable these.
> 
>>>
> 
>>>  From the user perspective, I don't agree that this is a good
> 
>>> compromise. Users simply want to recalibrate their battery.
> 
>>
> 
>> But can't they already do this by just unplugging the AC and
> 
>> then let the machine die ?Of course, but who wants that?
> 
>> How is this different, does it somehow magically flicks on the
> 
>> AC just before the battery deep-discharge protection kicks in
> 
>> so no unsaved work is lost ?
> 
> But this is exactly how it works. There is no risk of data loss.
> 
> 
> 
> The EC resets the force_discharge flag at the end of the discharge and
> the ThinkPad is seamlessly switched back to AC power. Just magical. No
> power interruptions.

Interesting. So what I get from this is that we really only want
force_discharge support. At least that is the major one. So maybe
we should focus on just that one.

Anyways lets wait and see what Mark has to say about this. As
I mentioned before doing battery calibration certainly is something
which is desirable to do under Windows too, so perhaps this option
is actually fine and it was the other 2 which are more
"testing only" firmware features.

Regards,

Hans


  reply	other threads:[~2021-09-29 10:56 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-17 14:01 [PATCH 1/3] thinkpad_acpi: add support for force_discharge Nicolo' Piazzalunga
2021-04-07 10:24 ` Hans de Goede
2021-04-07 10:33   ` Barnabás Pőcze
2021-04-08 13:51     ` Sebastian Reichel
2021-04-08 18:18       ` Thomas Koch
2021-04-09 18:33       ` Thomas Koch
2021-04-13  8:05         ` Hans de Goede
2021-04-17 11:49           ` Thomas Koch
2021-04-17 17:03             ` Hans de Goede
2021-05-19 14:45               ` Nicolo' Piazzalunga
2021-04-07 12:19   ` Thomas Koch
2021-04-07 17:48     ` [External] " Mark Pearson
     [not found]       ` <VI1PR09MB2302B7C3AD8014CC98D36AA595759@VI1PR09MB2302.eurprd09.prod.outlook.com>
2021-04-12 17:10         ` Mark Pearson
2021-09-27 13:59   ` Mark Pearson
2021-09-27 15:00     ` Nicolò Piazzalunga
2021-09-27 15:12       ` Hans de Goede
2021-09-27 16:50         ` [External] " Mark Pearson
2021-09-29  5:47         ` Thomas Koch
2021-09-29  9:55           ` Hans de Goede
2021-09-29 10:45             ` Thomas Koch
2021-09-29 10:56               ` Hans de Goede [this message]
2021-09-29 13:45                 ` [External] " Mark Pearson

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=d486c621-2464-8763-553b-3543d0578b58@redhat.com \
    --to=hdegoede@redhat.com \
    --cc=bberg@redhat.com \
    --cc=hadess@hadess.net \
    --cc=jwrdegoede@fedoraproject.org \
    --cc=linrunner@gmx.net \
    --cc=markpearson@lenovo.com \
    --cc=nicolopiazzalunga@gmail.com \
    --cc=njoshi1@lenovo.com \
    --cc=platform-driver-x86@vger.kernel.org \
    --cc=smclt30p@gmail.com \
    --cc=sre@kernel.org \
    /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;
as well as URLs for NNTP newsgroup(s).