public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>
To: Szilard Fabian <szfabian@bluemarch.art>
Cc: LKML <linux-kernel@vger.kernel.org>,
	platform-driver-x86@vger.kernel.org,  jwoithe@just42.net,
	Hans de Goede <hdegoede@redhat.com>,
	W_Armin@gmx.de
Subject: Re: [PATCH v5] platform/x86/fujitsu-laptop: Add battery charge control support
Date: Tue, 27 Feb 2024 14:53:47 +0200 (EET)	[thread overview]
Message-ID: <b797d581-a2a7-b95c-4853-b874667c1df5@linux.intel.com> (raw)
In-Reply-To: <20240227120435.429687-2-szfabian@bluemarch.art>

On Tue, 27 Feb 2024, Szilard Fabian wrote:

> This patch adds battery charge control support on Fujitsu notebooks
> via the S006 method of the FUJ02E3 ACPI device. With this method it's
> possible to set charge_control_end_threshold between 50 and 100%.
> 
> Tested on Lifebook E5411 and Lifebook U728. Sadly I can't test this
> patch on a dual battery one, but I didn't find any clue about
> independent battery charge control on dual battery Fujitsu notebooks
> either. And by that I mean checking the DSDT table of various Lifebook
> notebooks and reverse engineering FUJ02E3.dll.
> 
> Signed-off-by: Szilard Fabian <szfabian@bluemarch.art>
> ---
> v5:
> * add ACPI_BATTERY dependency into Kconfig

Thanks. My intention was that you'd send a new patch on top of what is 
already applied. But it doesn't matter anymore, I took the relevant line 
out of it and squashed it into the original commit.


-- 
 i.


  reply	other threads:[~2024-02-27 12:53 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-29 16:36 [RFC PATCH] platform/x86/fujitsu-laptop: Add battery charge control support Szilard Fabian
2024-01-29 18:00 ` [RFC PATCH v2] " Szilard Fabian
2024-01-30  2:02   ` Armin Wolf
2024-02-03  0:17     ` Szilard Fabian
2024-02-05 17:07       ` Armin Wolf
2024-02-05 23:37         ` Jonathan Woithe
2024-02-07  2:32   ` [RFC PATCH v3] " Szilard Fabian
2024-02-07  8:57     ` Hans de Goede
2024-02-08  1:56       ` Szilard Fabian
2024-02-08  9:11         ` Hans de Goede
2024-02-15 11:34     ` Ilpo Järvinen
2024-02-15 20:12       ` Szilard Fabian
2024-02-16  9:27         ` Ilpo Järvinen
2024-02-15 20:31     ` [PATCH v4] " Szilard Fabian
2024-02-18  4:47       ` Jonathan Woithe
2024-02-19 12:06       ` Ilpo Järvinen
2024-02-27 10:18         ` Ilpo Järvinen
2024-02-27 12:04           ` Szilard Fabian
2024-02-27 12:05       ` [PATCH v5] " Szilard Fabian
2024-02-27 12:53         ` Ilpo Järvinen [this message]
2024-02-27 21:47         ` Jonathan Woithe

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=b797d581-a2a7-b95c-4853-b874667c1df5@linux.intel.com \
    --to=ilpo.jarvinen@linux.intel.com \
    --cc=W_Armin@gmx.de \
    --cc=hdegoede@redhat.com \
    --cc=jwoithe@just42.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=platform-driver-x86@vger.kernel.org \
    --cc=szfabian@bluemarch.art \
    /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