From: Brendan Higgins <brendanhiggins@google.com>
To: minyard@acm.org, benjaminfair@google.com, clg@kaod.org,
joel@jms.id.au, andrew@aj.id.au
Cc: openipmi-developer@lists.sourceforge.net,
openbmc@lists.ozlabs.org, linux-kernel@vger.kernel.org
Subject: [RFC v1 0/4] ipmi_bmc: framework for IPMI on BMCs
Date: Mon, 7 Aug 2017 20:52:57 -0700 [thread overview]
Message-ID: <20170808035301.1980-1-brendanhiggins@google.com> (raw)
This introduces a framework for implementing the BMC side of the IPMI protocol,
roughly mirroring the host side OpenIPMI framework; it attempts to abstract away
hardware interfaces, such as Block Transfer interface hardware implementations
from IPMI command handlers.
It does this by implementing the traditional driver model of a bus with devices;
however, in this case a struct ipmi_bmc_bus represents a hardware interface,
where a struct ipmi_bmc_device represents a handler. A handler filters messages
by registering a function which returns whether a given message matches the
handler; it also has the concept of a default handler which is forwarded all
messages which are not matched by some other interface.
In this patchset, we introduce an example of a default handler: a misc device
file interface which implements the same interface as the the device file
interface used by the Aspeed BT driver.
Currently, OpenBMC handles all IPMI message routing and handling in userland;
the existing drivers simply provide a file interface for the hardware on the
device. In this patchset, we propose a common file interface to be shared by all
IPMI hardware interfaces, but also a framework for implementing handlers at the
kernel level, similar to how the existing OpenIPMI framework supports both
kernel users, as well as misc device file interface.
This patchset depends on the "ipmi: bt-i2c: added IPMI Block Transfer over I2C"
patchset, which can be found here:
https://www.mail-archive.com/linux-kernel@vger.kernel.org/msg1461960.html
However, I can fix this if desired.
Tested on the AST2500 EVB.
next reply other threads:[~2017-08-08 3:53 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-08 3:52 Brendan Higgins [this message]
2017-08-08 3:52 ` [RFC v1 1/4] ipmi_bmc: framework for BT " Brendan Higgins
2017-08-10 13:58 ` Corey Minyard
2017-08-11 1:06 ` Brendan Higgins
2017-08-08 3:52 ` [RFC v1 2/4] ipmi_bmc: device interface to IPMI BMC framework Brendan Higgins
2017-08-08 3:53 ` [RFC v1 3/4] ipmi_bmc: bt-i2c: port driver " Brendan Higgins
2017-08-08 3:53 ` [RFC v1 4/4] ipmi_bmc: bt-aspeed: " Brendan Higgins
2017-08-10 2:31 ` Jeremy Kerr
2017-08-10 5:29 ` Brendan Higgins
2017-08-10 7:20 ` Cédric Le Goater
2017-08-14 16:03 ` [RFC v1 0/4] ipmi_bmc: framework for IPMI on BMCs Patrick Williams
2017-08-14 22:28 ` Brendan Higgins
2017-08-23 6:12 ` Brendan Higgins
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=20170808035301.1980-1-brendanhiggins@google.com \
--to=brendanhiggins@google.com \
--cc=andrew@aj.id.au \
--cc=benjaminfair@google.com \
--cc=clg@kaod.org \
--cc=joel@jms.id.au \
--cc=linux-kernel@vger.kernel.org \
--cc=minyard@acm.org \
--cc=openbmc@lists.ozlabs.org \
--cc=openipmi-developer@lists.sourceforge.net \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®