From: Hans de Goede <hdegoede@redhat.com>
To: Chris Chiu <chiu@endlessos.org>, sre@kernel.org, wens@csie.org
Cc: linux-pm@vger.kernel.org, linux-kernel@vger.kernel.org,
linux@endlessos.org
Subject: Re: [PATCH] power: supply: axp288_fuel_gauge: Add the ECS EF20EA to the blacklist
Date: Wed, 9 Dec 2020 15:57:47 +0100 [thread overview]
Message-ID: <d58351aa-14a9-2ea7-ee8b-946ba28a782e@redhat.com> (raw)
In-Reply-To: <20201209045057.9509-1-chiu@endlessos.org>
Hi,
On 12/9/20 5:50 AM, Chris Chiu wrote:
> The ECS EF20EA laptop ships an AXP288 but it is actually using a
> different, separate FG chip for AC and battery monitoring. On this
> laptop we need to keep using the regular ACPI driver and disable the
> AXP288 FG to avoid reporting two batteries to userspace.
>
> Signed-off-by: Chris Chiu <chiu@endlessos.org>
> ---
> drivers/power/supply/axp288_fuel_gauge.c | 6 ++++++
> 1 file changed, 6 insertions(+)
>
> diff --git a/drivers/power/supply/axp288_fuel_gauge.c b/drivers/power/supply/axp288_fuel_gauge.c
> index 148eb8105803..a15c322c79ea 100644
> --- a/drivers/power/supply/axp288_fuel_gauge.c
> +++ b/drivers/power/supply/axp288_fuel_gauge.c
> @@ -739,6 +739,12 @@ static const struct dmi_system_id axp288_fuel_gauge_blacklist[] = {
> DMI_MATCH(DMI_PRODUCT_NAME, "Z83-4"),
> }
> },
> + {
> + /* ECS EF20 */
> + .matches = {
> + DMI_MATCH(DMI_PRODUCT_NAME, "EF20"),
> + },
> + },
> {}
> };
The axp288_fuel_gauge_blacklist already has the following entry:
{
/* ECS EF20EA */
.matches = {
DMI_MATCH(DMI_PRODUCT_NAME, "EF20EA"),
},
},
So is this real entry really necessary? The existing entry
matches the quirk for this in drivers/acpi/battery.c:
{
/* ECS EF20EA, AXP288 PMIC but uses separate fuel-gauge */
.callback = battery_do_not_check_pmic_quirk,
.matches = {
DMI_MATCH(DMI_PRODUCT_NAME, "EF20EA"),
},
},
And the one in drivers/acpi/ac.c:
{
/* ECS EF20EA, AXP288 PMIC but uses separate fuel-gauge */
.callback = ac_do_not_check_pmic_quirk,
.matches = {
DMI_MATCH(DMI_PRODUCT_NAME, "EF20EA"),
},
},
So I don't think that this patch is necessary...
Regards,
Hans
next prev parent reply other threads:[~2020-12-09 14:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-09 4:50 [PATCH] power: supply: axp288_fuel_gauge: Add the ECS EF20EA to the blacklist Chris Chiu
2020-12-09 14:57 ` Hans de Goede [this message]
2020-12-10 3:25 ` Chris Chiu
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=d58351aa-14a9-2ea7-ee8b-946ba28a782e@redhat.com \
--to=hdegoede@redhat.com \
--cc=chiu@endlessos.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=linux@endlessos.org \
--cc=sre@kernel.org \
--cc=wens@csie.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).