Re: A problem regarding asus-wmi and charging thresholds

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



+Cc: PDx86 mailing list

On Wed, Jul 15, 2020 at 5:40 AM Mark Enriquez <bugmenot.oss@xxxxxxxxx> wrote:
>
> TL;DR; On some "newer" asus laptops, the first battery is listed as BAT1 as if using the 1-index of counting, rather than "BATT", which prevents having a "charge_control_end_threshold" file present.

I believe we have a fix for this
http://git.infradead.org/linux-platform-drivers-x86.git/commit/a6146ab8a57b6a84e3643398605ec6f897a69365

>
> Good day,
> From this commit
> /6b3586d45bba14f6912f37488090c37a3710e7b4 "platform/x86: asus-wmi: Support laptops where the first battery is named BATT"
>
> I also have seen that on a "newer" asus laptop (vivobook x571gt) the first battery is "BAT1" rather than "BATT".
>
> Yet, the "charge_control_end_threshold" file does also work on the system ... well, after recompiling the kernel with this additional case in.
>
> Writing to this file does limit the RSOC of the battery and stops charging at the set threshold, albeit with the status "Unknown" instead of "Not Charging" but that's for another case.
>
> The corresponding bugzilla report is in https://bugzilla.kernel.org/show_bug.cgi?id=208385.
>
> Thank you.



-- 
With Best Regards,
Andy Shevchenko



[Index of Archives]     [Linux Kernel Development]     [Linux USB Devel]     [Video for Linux]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]

  Powered by Linux