* sysfs charge thresholds for ThinkPads (and possibly others), preparation for second try
@ 2015-07-07 21:07 Julian Andres Klode
2015-07-07 23:51 ` Sebastian Reichel
0 siblings, 1 reply; 4+ messages in thread
From: Julian Andres Klode @ 2015-07-07 21:07 UTC (permalink / raw
To: Sebastian Reichel, Dmitry Eremin-Solenikov, David Woodhouse,
linux-pm, Henrique de Moraes Holschuh, ibm-acpi-devel,
platform-driver-x86, Rafael J. Wysocki, Len Brown, linux-acpi
Cc: evgeni
Hi everyone (Thinkpad-ACPI, ACPI, and Power supply maintainers),
some might know that I presented a patch set adding support for
charge thresholds to thinkpad_acpi about 1.5 years ago.
Back then, one of the major rejections was that the functionality
for setting charge thresholds should be integrated into the
power supply stack somehow. I did not know who to contact back
then, but know I re-read MAINTAINERS and found all your addresses,
so I give it a second try.
One issue with just integrating it in the current battery
directories would be that ThinkPads are able to set charge
thresholds for batteries that are currently not inserted.
Back then I wrote:
> The next step is to integrate this properly with power supply
> and/or acpi battery. One way would be to add additional power
> supply properties and then add get/set_property() pointers to
> the acpi battery which it can fall back to if it does not support
> a requested property (and we would locate the ACPI battery and
> set those pointers to new thinkpad_acpi functions).
If you, the ACPI and power supply people, have any preferred
way (or any idea at all how) to proceed, that would be useful,
so I don't start working on it again, and then somebody does
not like it.
Regards,
Julian
CCing evgeni@debian.org who keeps pushing me to follow up
on this - thanks :)
--
Julian Andres Klode - Debian Developer, Ubuntu Member
See http://wiki.debian.org/JulianAndresKlode and http://jak-linux.org/.
Be friendly, do not top-post, and follow RFC 1855 "Netiquette".
- If you don't I might ignore you.
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: sysfs charge thresholds for ThinkPads (and possibly others), preparation for second try
2015-07-07 21:07 sysfs charge thresholds for ThinkPads (and possibly others), preparation for second try Julian Andres Klode
@ 2015-07-07 23:51 ` Sebastian Reichel
2015-07-08 9:40 ` Julian Andres Klode
0 siblings, 1 reply; 4+ messages in thread
From: Sebastian Reichel @ 2015-07-07 23:51 UTC (permalink / raw
To: Julian Andres Klode
Cc: Dmitry Eremin-Solenikov, David Woodhouse, linux-pm,
Henrique de Moraes Holschuh, ibm-acpi-devel, platform-driver-x86,
Rafael J. Wysocki, Len Brown, linux-acpi, evgeni
[-- Attachment #1: Type: text/plain, Size: 1758 bytes --]
Hi,
On Tue, Jul 07, 2015 at 11:07:28PM +0200, Julian Andres Klode wrote:
> Hi everyone (Thinkpad-ACPI, ACPI, and Power supply maintainers),
>
> some might know that I presented a patch set adding support for
> charge thresholds to thinkpad_acpi about 1.5 years ago.
Can you provide a link to the patch set?
> Back then, one of the major rejections was that the functionality
> for setting charge thresholds should be integrated into the
> power supply stack somehow. I did not know who to contact back
> then, but know I re-read MAINTAINERS and found all your addresses,
> so I give it a second try.
>
> One issue with just integrating it in the current battery
> directories would be that ThinkPads are able to set charge
> thresholds for batteries that are currently not inserted.
So the power supply device should be kept with
POWER_SUPPLY_PROP_PRESENT being disabled (and most properties
returning -ENODATA). The ACPI SBS driver seems to implement
POWER_SUPPLY_PROP_PRESENT, but I didn't test it.
> Back then I wrote:
> > The next step is to integrate this properly with power supply
> > and/or acpi battery. One way would be to add additional power
> > supply properties and then add get/set_property() pointers to
> > the acpi battery which it can fall back to if it does not support
> > a requested property (and we would locate the ACPI battery and
> > set those pointers to new thinkpad_acpi functions).
>
> If you, the ACPI and power supply people, have any preferred
> way (or any idea at all how) to proceed, that would be useful,
> so I don't start working on it again, and then somebody does
> not like it.
Adding charging thresholds as power_supply_property sounds
fine to me.
-- Sebastian
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: sysfs charge thresholds for ThinkPads (and possibly others), preparation for second try
2015-07-07 23:51 ` Sebastian Reichel
@ 2015-07-08 9:40 ` Julian Andres Klode
2015-07-09 4:46 ` Sebastian Reichel
0 siblings, 1 reply; 4+ messages in thread
From: Julian Andres Klode @ 2015-07-08 9:40 UTC (permalink / raw
To: Sebastian Reichel
Cc: Dmitry Eremin-Solenikov, David Woodhouse, linux-pm,
Henrique de Moraes Holschuh, ibm-acpi-devel, platform-driver-x86,
Rafael J. Wysocki, Len Brown, linux-acpi, evgeni
On Wed, Jul 08, 2015 at 01:51:10AM +0200, Sebastian Reichel wrote:
> Hi,
>
> On Tue, Jul 07, 2015 at 11:07:28PM +0200, Julian Andres Klode wrote:
> > Hi everyone (Thinkpad-ACPI, ACPI, and Power supply maintainers),
> >
> > some might know that I presented a patch set adding support for
> > charge thresholds to thinkpad_acpi about 1.5 years ago.
>
> Can you provide a link to the patch set?
Sure:
http://thread.gmane.org/gmane.linux.acpi.ibm-acpi.devel/3175
(it was not on the ACPI and Power MLs back then)
>
> > Back then, one of the major rejections was that the functionality
> > for setting charge thresholds should be integrated into the
> > power supply stack somehow. I did not know who to contact back
> > then, but know I re-read MAINTAINERS and found all your addresses,
> > so I give it a second try.
> >
> > One issue with just integrating it in the current battery
> > directories would be that ThinkPads are able to set charge
> > thresholds for batteries that are currently not inserted.
>
> So the power supply device should be kept with
> POWER_SUPPLY_PROP_PRESENT being disabled (and most properties
> returning -ENODATA). The ACPI SBS driver seems to implement
> POWER_SUPPLY_PROP_PRESENT, but I didn't test it.
Yes, indeed.
>
> > Back then I wrote:
> > > The next step is to integrate this properly with power supply
> > > and/or acpi battery. One way would be to add additional power
> > > supply properties and then add get/set_property() pointers to
> > > the acpi battery which it can fall back to if it does not support
> > > a requested property (and we would locate the ACPI battery and
> > > set those pointers to new thinkpad_acpi functions).
> >
> > If you, the ACPI and power supply people, have any preferred
> > way (or any idea at all how) to proceed, that would be useful,
> > so I don't start working on it again, and then somebody does
> > not like it.
>
> Adding charging thresholds as power_supply_property sounds
> fine to me.
>
Right, it gets a bit more complicated though: Since the code is
platform-specific, it should live in the platform driver, so a
way is needed to extend the existing device with new properties
from the platform driver.
--
Julian Andres Klode - Debian Developer, Ubuntu Member
See http://wiki.debian.org/JulianAndresKlode and http://jak-linux.org/.
Be friendly, do not top-post, and follow RFC 1855 "Netiquette".
- If you don't I might ignore you.
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: sysfs charge thresholds for ThinkPads (and possibly others), preparation for second try
2015-07-08 9:40 ` Julian Andres Klode
@ 2015-07-09 4:46 ` Sebastian Reichel
0 siblings, 0 replies; 4+ messages in thread
From: Sebastian Reichel @ 2015-07-09 4:46 UTC (permalink / raw
To: Julian Andres Klode
Cc: Dmitry Eremin-Solenikov, David Woodhouse, linux-pm,
Henrique de Moraes Holschuh, ibm-acpi-devel, platform-driver-x86,
Rafael J. Wysocki, Len Brown, linux-acpi, evgeni
[-- Attachment #1: Type: text/plain, Size: 2235 bytes --]
Hi,
On Wed, Jul 08, 2015 at 11:40:00AM +0200, Julian Andres Klode wrote:
> On Wed, Jul 08, 2015 at 01:51:10AM +0200, Sebastian Reichel wrote:
> > Hi,
> >
> > On Tue, Jul 07, 2015 at 11:07:28PM +0200, Julian Andres Klode wrote:
> > > Hi everyone (Thinkpad-ACPI, ACPI, and Power supply maintainers),
> > >
> > > some might know that I presented a patch set adding support for
> > > charge thresholds to thinkpad_acpi about 1.5 years ago.
> >
> > Can you provide a link to the patch set?
>
> Sure:
> http://thread.gmane.org/gmane.linux.acpi.ibm-acpi.devel/3175
>
> (it was not on the ACPI and Power MLs back then)
Thanks.
> [...]
> > > Back then I wrote:
> > > > The next step is to integrate this properly with power supply
> > > > and/or acpi battery. One way would be to add additional power
> > > > supply properties and then add get/set_property() pointers to
> > > > the acpi battery which it can fall back to if it does not support
> > > > a requested property (and we would locate the ACPI battery and
> > > > set those pointers to new thinkpad_acpi functions).
> > >
> > > If you, the ACPI and power supply people, have any preferred
> > > way (or any idea at all how) to proceed, that would be useful,
> > > so I don't start working on it again, and then somebody does
> > > not like it.
> >
> > Adding charging thresholds as power_supply_property sounds
> > fine to me.
>
> Right, it gets a bit more complicated though: Since the code is
> platform-specific, it should live in the platform driver, so a
> way is needed to extend the existing device with new properties
> from the platform driver.
Yes, my answer was only from the power supply subsystem's point of
view, since I do not know much about the thinkpad-acpi and SBS
driver. It seems the SBS driver has already minimal support for
handling platform specifics via the acpi_sbs_dmi_table, though. I
suggest to add a Thinkpad entry and modify the SBS driver, so that
it calls your additional code.
It would be nice, if the Thinkpad specific code could also be used
to add a label to the batteries, so that it's easier to distinguish
batteries in case of multiple ones being available.
-- Sebastian
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2015-07-09 4:46 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2015-07-07 21:07 sysfs charge thresholds for ThinkPads (and possibly others), preparation for second try Julian Andres Klode
2015-07-07 23:51 ` Sebastian Reichel
2015-07-08 9:40 ` Julian Andres Klode
2015-07-09 4:46 ` Sebastian Reichel
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.