From: "Ognjen Galić" <smclt30p-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: Henrique de Moraes Holschuh
<hmh-N3TV7GIv+o9fyO9Q7EP/yw@public.gmane.org>
Cc: "Platform Driver"
<platform-driver-x86-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
"ACPI Devel Maling List"
<linux-acpi-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
"Rafael J. Wysocki"
<rafael-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>,
"Henrique de Moraes Holschuh"
<ibm-acpi-N3TV7GIv+o9fyO9Q7EP/yw@public.gmane.org>,
"Linux PM" <linux-pm-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
"Rafael J. Wysocki" <rjw-LthD3rsA81gm4RdzfppkhA@public.gmane.org>,
"Robert Moore"
<robert.moore-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>,
"Sebastian Reichel" <sre-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>,
"Christoph Böhmwalder"
<christoph-KeW1gJXA36yNJhrcwGid2A@public.gmane.org>,
"Andy Shevchenko"
<andy.shevchenko-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
"Kevin Locke" <kevin-yFOG++GfaLUI8/NkjqMgMw@public.gmane.org>,
"Darren Hart" <dvhart-wEGCiKHe2LqWVfeAwA7xHQ@public.gmane.org>,
devel-E0kO6a4B6psdnm+yROfE0A@public.gmane.org,
ibm-acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org,
"Andy Shevchenko" <andy-wEGCiKHe2LqWVfeAwA7xHQ@public.gmane.org>,
"Len Brown" <lenb-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
Subject: Re: [PATCH 1/3] thinkpad_acpi: add support for inhibit_charge
Date: Mon, 14 May 2018 15:40:41 +0200 [thread overview]
Message-ID: <20180514134041.GC6417@thinkpad> (raw)
In-Reply-To: <20180514113928.dnsxjqov7l6rvorb-ZGHd14iZgfaRjzvQDGKj+xxZW9W5cXbT@public.gmane.org>
On Mon, May 14, 2018 at 08:39:28AM -0300, Henrique de Moraes Holschuh wrote:
> On Mon, 14 May 2018, Christoph Böhmwalder wrote:
> > > + case INHIBIT_CHARGE:
> > > + if ACPI_FAILURE(tpacpi_battery_acpi_eval(GET_INHIBIT, ret, battery))
> > > + return -ENODEV;
> > > +
> > > + /* The inhibit charge status is in the first bit */
> > > + *ret = *ret & 0x01;
> > > + return 0;
>
> Do we know what is in the other bits? If so, please document the ACPI
> method using a comment somewhere in the driver code, like you did for
> SET_INHIBIT.
I got the specs for the methods in a Lenovo doc I was told not to share
around, including information in it.
>
> > > default:
> > > pr_crit("wrong parameter: %d", what);
> > > return -EINVAL;
> > > @@ -9343,6 +9357,21 @@ static int tpacpi_battery_set(int what, int battery, int value)
> > > return -ENODEV;
> > > }
> > > return 0;
> > > + case INHIBIT_CHARGE:
> > > + /* When setting inhbitit charge, we set a default vaulue of
> >
> > This comment does not adhere to the Linux coding style
>
> Much on the driver doesn't, because it is _OLD_. But yeah, it is
> preferrable to fix this as we add code, so it would be good to have all
> new (and modified) comments switched to modern kernel style.
So what do you people want me to do? Should I fix the comments or leave
as-is?
>
> > > + case INHIBIT_CHARGE:
> > > + if (!battery_info.batteries[battery].inhibit_support)
> > > + return -ENODEV;
> > > + /* The only valid values are 1 and 0 */
> > > + if (value != 0 && value != 1)
> >
> > I'm not sure, but maybe `if (value < 2)` is better here?
>
> Indeed... with a comment that says 0 = main battery, 1 = extra/dock
> battery or something.
That seems like obfuscation to me, this way its clear that it must be
either 1 or 0. And inhibiting is set per-battery so 1 is on and not
battery 1.
>
> --
> Henrique Holschuh
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
next prev parent reply other threads:[~2018-05-14 13:40 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-13 15:29 [PATCH 1/3] thinkpad_acpi: add support for inhibit_charge Ognjen Galic
2018-05-14 9:46 ` Christoph Böhmwalder
2018-05-14 10:41 ` Andy Shevchenko
[not found] ` <CAHp75VdPOH7J1X4ZXmRsQ1yrB5n5RRmhPneWOnu7TFOAysgE6Q-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2018-05-14 13:38 ` Ognjen Galić
2018-05-14 11:39 ` Henrique de Moraes Holschuh
[not found] ` <20180514113928.dnsxjqov7l6rvorb-ZGHd14iZgfaRjzvQDGKj+xxZW9W5cXbT@public.gmane.org>
2018-05-14 13:40 ` Ognjen Galić [this message]
2018-05-14 15:41 ` Henrique de Moraes Holschuh
2018-05-14 13:36 ` Ognjen Galić
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=20180514134041.GC6417@thinkpad \
--to=smclt30p-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
--cc=andy-wEGCiKHe2LqWVfeAwA7xHQ@public.gmane.org \
--cc=andy.shevchenko-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
--cc=christoph-KeW1gJXA36yNJhrcwGid2A@public.gmane.org \
--cc=devel-E0kO6a4B6psdnm+yROfE0A@public.gmane.org \
--cc=dvhart-wEGCiKHe2LqWVfeAwA7xHQ@public.gmane.org \
--cc=hmh-N3TV7GIv+o9fyO9Q7EP/yw@public.gmane.org \
--cc=ibm-acpi-N3TV7GIv+o9fyO9Q7EP/yw@public.gmane.org \
--cc=ibm-acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
--cc=kevin-yFOG++GfaLUI8/NkjqMgMw@public.gmane.org \
--cc=lenb-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org \
--cc=linux-acpi-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-pm-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=platform-driver-x86-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=rafael-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org \
--cc=rjw-LthD3rsA81gm4RdzfppkhA@public.gmane.org \
--cc=robert.moore-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org \
--cc=sre-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.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