From: minyard@acm.org
To: openipmi-developer@lists.sourceforge.net, linux-kernel@vger.kernel.org
Cc: Jean Delvare <jdelvare@suse.de>, Andy Lutomirski <luto@kernel.org>
Subject: [PATCH 0/4] dmi: Rework to get IPMI autoloading from DMI tables
Date: Fri, 29 Jan 2016 16:43:10 -0600 [thread overview]
Message-ID: <1454107394-8914-1-git-send-email-minyard@acm.org> (raw)
The IPMI driver would not auto-load from DMI tables. So these patches
creates a platform device from an IPMI DMI table entry, and then
modify the IPMI driver to handle all this.
I followed how ACPI works mostly, with a fwnode and such. But greatly
simplified, of course :).
I'm no sure if patch 4 is done in the right place. Maybe it would
be better in the IPMI driver directory? But it's pretty clean where
it is.
Also, I wasn't quite sure about the name of the device. If the device
was named ipmi_si or ipmi_ssif, the driver override would not be
required, but then you really couldn't tell it came from DMI.
You could also create a firmware_node like ACPI does, but that might
be overkill.
-corey
next reply other threads:[~2016-01-29 23:44 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-29 22:43 minyard [this message]
2016-01-29 22:43 ` [PATCH 1/4] dmi: remove const from return of dmi_find_device minyard
2016-01-29 22:43 ` [PATCH 2/4] dmi: Add a DMI firmware node and handling minyard
2016-01-29 23:59 ` kbuild test robot
2016-01-30 0:35 ` Corey Minyard
2016-01-30 0:41 ` kbuild test robot
2016-01-31 22:46 ` Andy Lutomirski
2016-02-01 0:36 ` Corey Minyard
2016-02-01 9:25 ` Jean Delvare
2016-02-02 13:37 ` Corey Minyard
2016-02-02 18:25 ` Andy Lutomirski
2016-02-03 16:51 ` Corey Minyard
2016-01-29 22:43 ` [PATCH 3/4] dmi: Move IPMI DMI scanning to the DMI code minyard
2016-01-29 22:43 ` [PATCH 4/4] dmi/ipmi: Add IPMI DMI devices as platform devices minyard
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=1454107394-8914-1-git-send-email-minyard@acm.org \
--to=minyard@acm.org \
--cc=jdelvare@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@kernel.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
Powered by JetHome