[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAEGpDub7-ou3YJAOxxK-vj9RYNMp5ER752XMFVLdB8zWWisV8Q@mail.gmail.com>
Date: Fri, 24 Feb 2017 14:01:30 +0100
From: Pau Espin Pedrol <pespin.shar@...il.com>
To: Dmitry Torokhov <dmitry.torokhov@...il.com>
Cc: Andy Shevchenko <andy.shevchenko@...il.com>,
Andy Shevchenko <andy@...radead.org>,
Platform Driver <platform-driver-x86@...r.kernel.org>,
Corentin Chary <corentin.chary@...il.com>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
acpi4asus-user <acpi4asus-user@...ts.sourceforge.net>,
"dvhart@...radead.org" <dvhart@...radead.org>
Subject: Re: [PATCH] eeepc-laptop: Skip unknown key messages 0x50 0x51
>> Dmitry, do we have special events for AC (un)plug? What is the best
>> approach in your opinion?
>
> Not route them through input as they not input events would be the best.
>
Is my patch good enough for this or would you recommend doing it another way?
> I'd look into hooking up power_supply class.
>
Whys is this necessay? All the related information required is already
present in my system.
I already have two power_supply instances:
* /sys/class/power_supply/AC0/ (provided by module "ac"), contains
property "online" which is correctly updated to 1 when AC is plugged
and 0 when AC is unplugged.
* /sys/class/power_supply/BAT0/ (provided by module "battery"),
contains property "status" which is correctly updated to "Charging"
when AC is plugged and "Discharging" when AC is unplugged.
Powered by blists - more mailing lists