From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752243AbbBVRz5 (ORCPT ); Sun, 22 Feb 2015 12:55:57 -0500 Received: from bh-25.webhostbox.net ([208.91.199.152]:37594 "EHLO bh-25.webhostbox.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752006AbbBVRz4 (ORCPT ); Sun, 22 Feb 2015 12:55:56 -0500 Message-ID: <54EA17F4.8000106@roeck-us.net> Date: Sun, 22 Feb 2015 09:55:00 -0800 From: Guenter Roeck User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.4.0 MIME-Version: 1.0 To: =?UTF-8?B?UGFsaSBSb2jDoXI=?= CC: Arnd Bergmann , Greg Kroah-Hartman , Steven Honeyman , Jean Delvare , Valdis.Kletnieks@vt.edu, Jochen Eisinger , Gabriele Mazzotta , linux-kernel@vger.kernel.org, lm-sensors@lm-sensors.org Subject: Re: i8k: move driver from char to hwmon References: <201502221250.49466@pali> <54EA12DC.1000403@roeck-us.net> <201502221844.54371@pali> In-Reply-To: <201502221844.54371@pali> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit X-Authenticated_sender: linux@roeck-us.net X-OutGoing-Spam-Status: No, score=-1.0 X-CTCH-PVer: 0000001 X-CTCH-Spam: Unknown X-CTCH-VOD: Unknown X-CTCH-Flags: 0 X-CTCH-RefID: str=0001.0A020202.54EA182B.0102,ss=1,re=0.001,recu=0.000,reip=0.000,cl=1,cld=1,fgs=0 X-CTCH-Score: 0.001 X-CTCH-ScoreCust: 0.000 X-CTCH-Rules: C_4847, X-CTCH-SenderID: linux@roeck-us.net X-CTCH-SenderID-Flags: 0 X-CTCH-SenderID-TotalMessages: 2 X-CTCH-SenderID-TotalSpam: 0 X-CTCH-SenderID-TotalSuspected: 0 X-CTCH-SenderID-TotalConfirmed: 0 X-CTCH-SenderID-TotalBulk: 0 X-CTCH-SenderID-TotalVirus: 0 X-CTCH-SenderID-TotalRecipients: 0 X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - bh-25.webhostbox.net X-AntiAbuse: Original Domain - vger.kernel.org X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - roeck-us.net X-Get-Message-Sender-Via: bh-25.webhostbox.net: mailgid no entry from get_relayhosts_entry X-Source: X-Source-Args: X-Source-Dir: Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 02/22/2015 09:44 AM, Pali Rohár wrote: > On Sunday 22 February 2015 18:33:16 Guenter Roeck wrote: >> On 02/22/2015 03:50 AM, Pali Rohár wrote: >>> Hello, >>> >>> currently i8k driver for DELLDIAG SMM operations (charger, >>> battery, hotkeys, temperature and fan control) supports two >>> interfaces: >>> >>> 1) old /proc/i8k char device >>> 2) new hwmon interface >>> >>> Driver now lives in char subsystem, but nowadays I think lot >>> of people are interested only in hwmon interface which >>> provides temperature & fan control. Power management and >>> hotkeys support (which is missing in 2) but provided by 1)) >>> is already handled by ACPI or input subsystem for new >>> laptops. >>> >>> Also name "i8k" is really non intuitive what it means and >>> supports... (I was told it is abbreviation for Inspirion >>> 8000 model which was probably first dell model supported by >>> that DELLDIAG interface). Now driver is used on Vostro, >>> Latitude and also Precision and XPS models. I think at >>> least "dell" should be part of driver name and config >>> option. >>> >>> So I have idea for some changes: >>> >>> 1) Move driver from char subsystem to hwmon >> >> I am ok with this one. >> >>> 2) Rename driver from i8k to something like delldiag or >>> dellsmm >> >> Might be problematic, as it would break existing >> configurations unless you keep the CONFIG_I8K but rename the >> driver. Driver names are never perfect, so I would just leave >> it as is. >> >>> 3) Add new CONFIG_ option to enable/disable /proc/i8k device >>> and compile only hwmon interface support >> >> Makes sense. I would suggest to make hwmon suppport the >> default and mandatory if the driver is enabled and add a new >> CONFIG_I8K_PROCIF or similar which should be enabled by >> default. >> > > What about CONFIG_DELLDIAG (or DELLSMM or CONFIG_SENSORS_*) for > mandatory core & hwmon code and (keep existing) CONFIG_I8K for > /proc/i8k? > CONFIG_SENSORS_DELL would probably be best, but that would still break backward compatibility for existing configurations unless you enable CONFIG_SENSORS_DELL by default which would not be a good idea. Guenter