From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Andrew Jeffery <andrew@aj.id.au>,
Guenter Roeck <linux@roeck-us.net>,
Edward James <eajames@us.ibm.com>
Cc: corbet@lwn.net, devicetree@vger.kernel.org,
eajames.ibm@gmail.com, jdelvare@suse.com, joel@jms.id.au,
linux-doc@vger.kernel.org, linux-hwmon@vger.kernel.org,
linux-i2c@vger.kernel.org, linux-kernel@vger.kernel.org,
mark.rutland@arm.com, robh+dt@kernel.org, wsa@the-dreams.de
Subject: Re: [PATCH linux 2/6] hwmon: occ: Add sysfs interface
Date: Tue, 10 Jan 2017 11:45:08 -0600 [thread overview]
Message-ID: <1484070308.21117.31.camel@kernel.crashing.org> (raw)
In-Reply-To: <1483919532.2950.1.camel@aj.id.au>
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.
next prev parent reply other threads:[~2017-01-10 17:46 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-30 17:56 [PATCH linux 0/6] drivers: hwmon: Add On-Chip Controller driver eajames.ibm
2016-12-30 17:56 ` [PATCH linux 1/6] hwmon: Add core On-Chip Controller support for POWER CPUs eajames.ibm
2016-12-30 19:18 ` kbuild test robot
2016-12-30 19:18 ` kbuild test robot
2016-12-30 17:56 ` [PATCH linux 2/6] hwmon: occ: Add sysfs interface eajames.ibm
2016-12-30 19:34 ` Guenter Roeck
2017-01-03 14:30 ` Fwd: " Brad Bishop
2017-01-03 23:08 ` Eddie James
2017-01-03 23:49 ` Brad Bishop
2017-01-04 0:06 ` Joel Stanley
2017-01-04 0:13 ` Brad Bishop
2017-01-04 0:25 ` Andrew Jeffery
2017-01-04 1:53 ` Andrew Jeffery
2017-01-04 15:07 ` Eddie James
2017-01-06 22:17 ` Edward James
2017-01-07 17:15 ` Guenter Roeck
2017-01-08 23:52 ` Andrew Jeffery
2017-01-10 17:45 ` Benjamin Herrenschmidt [this message]
2017-01-10 17:41 ` Benjamin Herrenschmidt
2017-01-10 17:51 ` Guenter Roeck
2017-01-10 23:01 ` Edward James
2016-12-30 17:56 ` [PATCH linux 3/6] hwmon: occ: Add I2C transport implementation for SCOM operations eajames.ibm
2016-12-30 17:56 ` eajames.ibm-Re5JQEeQqe8AvxtiuMwx3w
2016-12-30 17:56 ` [PATCH linux 4/6] hwmon: occ: Add callbacks for parsing P8 OCC datastructures eajames.ibm
2016-12-30 17:56 ` eajames.ibm-Re5JQEeQqe8AvxtiuMwx3w
2016-12-30 17:56 ` [PATCH linux 5/6] hwmon: occ: Add hwmon implementation for the P8 OCC eajames.ibm
2016-12-30 17:56 ` eajames.ibm-Re5JQEeQqe8AvxtiuMwx3w
2017-01-01 0:25 ` kbuild test robot
2017-01-03 22:45 ` Rob Herring
2016-12-30 17:56 ` [PATCH linux 6/6] hwmon: occ: Add callbacks for parsing P9 OCC datastructures eajames.ibm
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1484070308.21117.31.camel@kernel.crashing.org \
--to=benh@kernel.crashing.org \
--cc=andrew@aj.id.au \
--cc=corbet@lwn.net \
--cc=devicetree@vger.kernel.org \
--cc=eajames.ibm@gmail.com \
--cc=eajames@us.ibm.com \
--cc=jdelvare@suse.com \
--cc=joel@jms.id.au \
--cc=linux-doc@vger.kernel.org \
--cc=linux-hwmon@vger.kernel.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=mark.rutland@arm.com \
--cc=robh+dt@kernel.org \
--cc=wsa@the-dreams.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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.