Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932914AbaFLJ26 (ORCPT ); Thu, 12 Jun 2014 05:28:58 -0400 Received: from mout.gmx.net ([212.227.17.21]:51523 "EHLO mout.gmx.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S932553AbaFLJ24 (ORCPT ); Thu, 12 Jun 2014 05:28:56 -0400 Message-ID: <539972CD.1010004@gmx.de> Date: Thu, 12 Jun 2014 11:28:45 +0200 From: Michael Lawnick User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.6.0 MIME-Version: 1.0 To: Linus Walleij CC: Wolfram Sang , Grant Likely , Lee Jones , "linux-arm-kernel@lists.infradead.org" , "linux-kernel@vger.kernel.org" , "linux-i2c@vger.kernel.org" Subject: Re: [PATCH] i2c: Make I2C ID tables non-mandatory for DT'ed and/or ACPI'ed devices References: <1401452797-29521-1-git-send-email-lee.jones@linaro.org> <1401452797-29521-2-git-send-email-lee.jones@linaro.org> <20140530123656.GC2742@katana> <20140530133405.GB29731@lee--X1> <20140530174800.GA4917@katana> <20140530192516.GA4319@lee--X1> <20140531134805.GA3287@katana> <538C8A59.2070907@gmx.de> <538EB81B.3090807@gmx.de> In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Provags-ID: V03:K0:PwevFaXsWexhCH09PHa33O57BGigKhlL4QQrbLg2TMCRdezR2wV y/5JbZZRN99rlmvlkWC14IDgJ1vAF3JpVE5D4ymX6IdCCuFsVL/GFVWT1DOPpW5ile7PM2Z xZ0RZEy/O9wMKojPUi3/E96y+9K+LA3Mc/XcBGIGY6PeckWzAq8Y6MJkcC6Vhwm3T69oF6J 7BJmwBo5aznTG9s9ztWvA== Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Am 12.06.2014 09:55, schrieb Linus Walleij: > On Wed, Jun 4, 2014 at 8:09 AM, Michael Lawnick wrote: >> Am 03.06.2014 13:18, schrieb Linus Walleij: >>> On Mon, Jun 2, 2014 at 4:29 PM, Michael Lawnick wrote: >>>> >>>> Am 02.06.2014 14:16, schrieb Linus Walleij: >>> >>> >>>>> Is this really so useful on embedded systems? >>>>> >>>>> I was under the impression that this method was something used >>>>> on say PC desktops with temperature monitors and EEPROMs >>>>> on some I2C link on the PCB, usage entirely optional and fun >>>>> for userspace hacks. >>>>> >>>> We use it for dynamic instantiating whole subsystems with multiplexers, >>>> sensors, controllers in an embedded system. The device list is taken from >>>> an >>>> I2C eeprom which gets read on hotplug. >>> >>> >>> Does this mean that you have stored the names (strings) that are used >>> by the Linux kernel for identifying the devices into your EEPROM? >>> >>> That means that you have made the kernel-internal device driver names >>> an ABI which is unfortunate :-/ >>> >>> This is one of the reasons to why we insist on device tree: OS neutral >>> hardware description. >> >> The eeprom contains a device tree that is dynamically merged. > > That is a kind of way of saying "yes we made the kernel-internal > driver named an ABI" I guess? Sorry, I fear I don't get you. Could you please rephrase? Of course it might be that I'm missing some fundamental idea of device tree. The mechanism we use started with K2.6 where device tree usage on MIPS wasn't that intensive. Anyway the original idea of removing i2c_table now moved towards non-mandatory usage. -- KR Michael -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/