linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Jeremy Kerr <jk@ozlabs.org>
To: Corey Minyard <minyard@acm.org>,
	openipmi-developer@lists.sourceforge.net
Cc: linuxppc-dev@lists.ozlabs.org
Subject: [PATCH 0/4] ipmi: Allow dynamic device IDs
Date: Mon, 12 Sep 2016 16:55:33 +0800	[thread overview]
Message-ID: <1473670537-26428-1-git-send-email-jk@ozlabs.org> (raw)

This series implements a more dynamic method of reporting BMC version &
identification. The current method of registering versions and IDs
during ipmi_register_smi means that if a BMC is upgraded during a boot,
the IPMI core code will report old version information.

We do this by querying the BMC (using a Get Device ID request) at smi
registration in the IPMI core code, and when the sysfs version & id
attributes are accessed.

The core of the change is in patch 3/4. Patches 1 and 2 implement a
couple of minor API changes leading up to this.

Patch 4 converts the powernv IPMI driver to use the dynamic IDs; the
behaviour of the other SMIs is not changed by this series. However,
if there's interest, I'm happy to alter the existing SMIs too, in a
follow-up series.

Questions & comments most welcome.

Cheers,

	
Jeremy
---

Jeremy Kerr (4):
  ipmi: Add a reference from BMC devices to their interfaces
  ipmi: Make ipmi_demangle_device_id more generic
  ipmi: allow dynamic BMC version information
  ipmi/powernv: Use dynamic device ids

 drivers/char/ipmi/ipmi_msghandler.c | 160 ++++++++++++++++++++++++++++++++++--
 drivers/char/ipmi/ipmi_powernv.c    |   5 +-
 drivers/char/ipmi/ipmi_si_intf.c    |   3 +-
 drivers/char/ipmi/ipmi_ssif.c       |   3 +-
 include/linux/ipmi_smi.h            |  16 ++--
 5 files changed, 169 insertions(+), 18 deletions(-)

-- 
2.7.4

             reply	other threads:[~2016-09-12  8:57 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-12  8:55 Jeremy Kerr [this message]
2016-09-12  8:55 ` [PATCH 1/4] ipmi: Add a reference from BMC devices to their interfaces Jeremy Kerr
2016-09-12  8:55 ` [PATCH 2/4] ipmi: Make ipmi_demangle_device_id more generic Jeremy Kerr
2016-09-12  8:55 ` [PATCH 3/4] ipmi: allow dynamic BMC version information Jeremy Kerr
2016-09-12 16:38   ` [Openipmi-developer] " Corey Minyard
2016-09-13 10:14     ` Jeremy Kerr
2016-09-12  8:55 ` [PATCH 4/4] ipmi/powernv: Use dynamic device ids Jeremy Kerr

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=1473670537-26428-1-git-send-email-jk@ozlabs.org \
    --to=jk@ozlabs.org \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=minyard@acm.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;
as well as URLs for NNTP newsgroup(s).