[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1484070308.21117.31.camel@kernel.crashing.org>
Date: Tue, 10 Jan 2017 11:45:08 -0600
From: Benjamin Herrenschmidt <benh@...nel.crashing.org>
To: Andrew Jeffery <andrew@...id.au>,
Guenter Roeck <linux@...ck-us.net>,
Edward James <eajames@...ibm.com>
Cc: corbet@....net, devicetree@...r.kernel.org, eajames.ibm@...il.com,
jdelvare@...e.com, joel@....id.au, linux-doc@...r.kernel.org,
linux-hwmon@...r.kernel.org, linux-i2c@...r.kernel.org,
linux-kernel@...r.kernel.org, mark.rutland@....com,
robh+dt@...nel.org, wsa@...-dreams.de
Subject: Re: [PATCH linux 2/6] hwmon: occ: Add sysfs interface
On Mon, 2017-01-09 at 10:22 +1030, Andrew Jeffery wrote:
> Alternatively, in the style of your first para, we could push the
> host
> CPU state management into the kernel and expose a boot/reboot/power-
> offÂ
> API to userspace. That would give us a place to hook calls for
> configuring and cleaning up any host-dependent drivers on the BMC.
That's nasty. Each machine has a subtly different way of controller
host power, that would mean a different kernel driver for each of them,
which we are trying to avoid.
This is userspace policy.
Cheers,
Ben.
Powered by blists - more mailing lists