[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <DM6PR19MB2636C2298994F284C62924CEFA700@DM6PR19MB2636.namprd19.prod.outlook.com>
Date: Wed, 29 Jul 2020 13:14:58 +0000
From: "Limonciello, Mario" <Mario.Limonciello@...l.com>
To: Matthew Garrett <mjg59@...f.ucam.org>,
"Yuan, Perry" <Perry.Yuan@...l.com>
CC: "sre@...nel.org" <sre@...nel.org>,
"pali@...nel.org" <pali@...nel.org>,
"dvhart@...radead.org" <dvhart@...radead.org>,
"andy@...radead.org" <andy@...radead.org>,
"linux-pm@...r.kernel.org" <linux-pm@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"platform-driver-x86@...r.kernel.org"
<platform-driver-x86@...r.kernel.org>
Subject: Re: [PATCH] platform/x86:dell-laptop:Add battery charging thresholds
and charging mode switch.
> The values here seem very Dell specific, but this is going into a
> generic sysfs path. Really stuff here should be as vendor independent as
> possible. If these values don't correspond to a wider industry
> specification it probably makes sense to make this something Dell
> specific.
Worth pointing out that for wilco-ec they use this path:
Documentation/ABI/testing/sysfs-class-power-wilco
So that could be something good to model off for v2.
Powered by blists - more mailing lists