From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932556AbcA2XoL (ORCPT ); Fri, 29 Jan 2016 18:44:11 -0500 Received: from vms173017pub.verizon.net ([206.46.173.17]:51991 "EHLO vms173017pub.verizon.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1756276AbcA2XoH (ORCPT ); Fri, 29 Jan 2016 18:44:07 -0500 X-Greylist: delayed 3615 seconds by postgrey-1.27 at vger.kernel.org; Fri, 29 Jan 2016 18:44:07 EST X-CMAE-Score: 0 X-CMAE-Analysis: v=2.1 cv=btqxfxui c=1 sm=1 tr=0 a=bXmWQgKa9n63w7XTPFb8JQ==:117 a=xqWC_Br6kY4A:10 a=7aQ_Q-yQQ-AA:10 a=53LRPBCSU0hQmdlcNXQA:9 From: minyard@acm.org To: openipmi-developer@lists.sourceforge.net, linux-kernel@vger.kernel.org Cc: Jean Delvare , Andy Lutomirski Subject: [PATCH 0/4] dmi: Rework to get IPMI autoloading from DMI tables Date: Fri, 29 Jan 2016 16:43:10 -0600 Message-id: <1454107394-8914-1-git-send-email-minyard@acm.org> X-Mailer: git-send-email 2.5.0 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 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