From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1750973AbcL1HzW (ORCPT ); Wed, 28 Dec 2016 02:55:22 -0500 Received: from mail-oi0-f67.google.com ([209.85.218.67]:34927 "EHLO mail-oi0-f67.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750888AbcL1HzU (ORCPT ); Wed, 28 Dec 2016 02:55:20 -0500 MIME-Version: 1.0 In-Reply-To: <52345.1482878491@turing-police.cc.vt.edu> References: <1482843136-12838-1-git-send-email-pali.rohar@gmail.com> <21e8453f9ebd2955b2c5e499dc51efb0@the-dreams.de> <201612271451.01505@pali> <52345.1482878491@turing-police.cc.vt.edu> From: Andy Shevchenko Date: Wed, 28 Dec 2016 09:55:18 +0200 Message-ID: Subject: Re: [PATCH] i2c: i801: Register optional lis3lv02d i2c device on Dell machines To: Valdis.Kletnieks@vt.edu, Mika Westerberg Cc: =?UTF-8?Q?Pali_Roh=C3=A1r?= , Wolfram Sang , Jean Delvare , Steven Honeyman , Jochen Eisinger , Gabriele Mazzotta , Andy Lutomirski , Mario Limonciello , Alex Hung , =?UTF-8?B?TWljaGHDheKAmiBLw4TihKJwaWXDheKAng==?= , Takashi Iwai , linux-i2c@vger.kernel.org, "linux-kernel@vger.kernel.org" , platform-driver-x86@vger.kernel.org Content-Type: text/plain; charset=UTF-8 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by mail.home.local id uBS7tQgn029548 On Wed, Dec 28, 2016 at 12:41 AM, wrote: > On Wed, 28 Dec 2016 00:15:30 +0200, Andy Shevchenko said: >> On Tue, Dec 27, 2016 at 3:51 PM, Pali Rohár wrote: > >> > I have no idea how to do it (properly) outside of i2c-i801.c file. >> >> I doubt we need a single line of code for this. See [1] and perhaps >> create an EFI variable with necessary upgrade device node. >> >> > Same thing is done for Fujitsu machines, see function >> > i801_probe_optional_slaves() in i2c-i801.c file. So I did similar >> > approach for Dell machines. >> >> Perhaps, this also needs to be converted to use EFI variable. >> >> [1] https://lwn.net/Articles/693212/ > > There's no guarantee that the laptops in question are booted with UEFI, > as Dell still supports legacy boot. So assuming the presence of EFI variables > is somewhat problematic. > In addition, it requires the user (or something in userspace) to set the UEFI > variable or configfs tweak, rather than Just Working Out Of The Box. I have no strong opinion, though I don't support the idea to put all hacks in the world to the kernel. For example, we have user space tool to switch USB modem from storage to actual communication device and that is just working out of the box. Mika, Darren, what are your opinions? -- With Best Regards, Andy Shevchenko