From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754857AbcAYBpf (ORCPT ); Sun, 24 Jan 2016 20:45:35 -0500 Received: from mail.kernel.org ([198.145.29.136]:47384 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754209AbcAYBp3 (ORCPT ); Sun, 24 Jan 2016 20:45:29 -0500 MIME-Version: 1.0 From: Andy Lutomirski Date: Sun, 24 Jan 2016 17:45:07 -0800 X-Gmail-Original-Message-ID: Message-ID: Subject: ipmi_si feature request: SMBIOS-based autoloading To: Corey Minyard , OpenIPMI Developers , "linux-kernel@vger.kernel.org" , brijeshkumar.singh@amd.com, Jean Delvare Content-Type: text/plain; charset=UTF-8 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org ipmi_si doesn't autoload on systems where it's found via SMBIOS. Could that be fixed? If I were doing it, I'd suggest rigging up some code that's compiled in to the main kernel even if ipmi_si is a module that creates the platform device if the dmi device is there and then set up a modalias so that the platofrm device causes ipmi_si to load. (In general, having the same driver create the platform device and register the platform driver means that autoloading is unlikely to work right. See arch/x86/kernel/pmem.c for an example of a weird legacy device that gets this right.) Alternatively, maybe /sys/firmware/dmi could learn how to advertise modaliases. But that might be a giant mess to solve a tiny problem. --Andy