devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Brendan Higgins <brendanhiggins@google.com>
To: corbet@lwn.net, robh+dt@kernel.org, mark.rutland@arm.com,
	arnd@arndb.de, gregkh@linuxfoundation.org, minyard@acm.org,
	joel@jms.id.au, benh@kernel.crashing.org
Cc: linux-doc@vger.kernel.org, devicetree@vger.kernel.org,
	openipmi-developer@lists.sourceforge.net,
	openbmc@lists.ozlabs.org, linux-kernel@vger.kernel.org
Subject: [PATCH v1 0/3] ipmi: bt-i2c: added IPMI Block Transfer over I2C
Date: Fri,  4 Aug 2017 16:18:51 -0700	[thread overview]
Message-ID: <20170804231854.19730-1-brendanhiggins@google.com> (raw)

This patchset introduces IPMI Block Transfer over I2C (BT-I2C), which has the
same semantics as IPMI Block Transfer except it done over I2C.

The documentation discusses the reason for this in greater detail, suffice it to
say SSIF cannot be correctly implemented on some naive I2C devices. There are
some additional reasons why we don't like SSIF, but those are again covered in
the documentation for all those who are interested.

In addition, since I am adding both host side and BMC side support, I figured
that now is a good time to resolve the problem of where to put BMC side IPMI
drivers; right now we have it (there is only one) in drivers/char/ipmi/ with the
rest of the host side IPMI drivers, but I think it makes sense to put all of the
host side IPMI drivers in one directory and all of the BMC side drivers in
another, preferably in a way that does not effect all of the current OpenIPMI
users. I have not created a MAINTAINERS entry for the new directory yet, as I
figured there might be some discussion to be had about it.

I have tested this patchset on the Aspeed 2500 EVB.

             reply	other threads:[~2017-08-04 23:18 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-04 23:18 Brendan Higgins [this message]
2017-08-04 23:18 ` [PATCH v1 1/3] ipmi: bt-i2c: added documentation for bt-i2c drivers Brendan Higgins
     [not found] ` <20170804231854.19730-1-brendanhiggins-hpIqsD4AKlfQT0dZR+AlfA@public.gmane.org>
2017-08-04 23:18   ` [PATCH v1 2/3] ipmi: bt-i2c: added IPMI Block Transfer over I2C host side Brendan Higgins
2017-08-05 21:37     ` kbuild test robot
2017-08-04 23:18   ` [PATCH v1 3/3] ipmi: bt-i2c: added IPMI Block Transfer over I2C BMC side Brendan Higgins
2017-08-04 23:25 ` [PATCH v1 0/3] ipmi: bt-i2c: added IPMI Block Transfer over I2C Brendan Higgins
2017-08-09 10:56 ` Anton D. Kachalov
     [not found]   ` <57021502276176-OEmCjAEqX0ITMcy66jKROkXOewmhPV1Zh13vi7wywA4@public.gmane.org>
2017-08-10  1:14     ` 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=20170804231854.19730-1-brendanhiggins@google.com \
    --to=brendanhiggins@google.com \
    --cc=arnd@arndb.de \
    --cc=benh@kernel.crashing.org \
    --cc=corbet@lwn.net \
    --cc=devicetree@vger.kernel.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=joel@jms.id.au \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=minyard@acm.org \
    --cc=openbmc@lists.ozlabs.org \
    --cc=openipmi-developer@lists.sourceforge.net \
    --cc=robh+dt@kernel.org \
    /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;
as well as URLs for NNTP newsgroup(s).