Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754128Ab2FMM2Z (ORCPT ); Wed, 13 Jun 2012 08:28:25 -0400 Received: from mail-ey0-f174.google.com ([209.85.215.174]:37739 "EHLO mail-ey0-f174.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754012Ab2FMM2W (ORCPT ); Wed, 13 Jun 2012 08:28:22 -0400 Message-ID: <4FD88761.9050703@linaro.org> Date: Wed, 13 Jun 2012 13:28:17 +0100 From: Lee Jones User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:11.0) Gecko/20120410 Thunderbird/11.0.1 MIME-Version: 1.0 To: Linus Walleij CC: linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org, linus.walleij@stericsson.com, arnd@arndb.de, grant.likely@secretlab.ca, linux-i2c@vger.kernel.org Subject: Re: [PATCH 09/14] i2c: Add Device Tree support to the Nomadik I2C driver References: <1339428307-3850-1-git-send-email-lee.jones@linaro.org> <1339428307-3850-10-git-send-email-lee.jones@linaro.org> <4FD6F0E8.5040606@linaro.org> <4FD83AAD.2010701@linaro.org> In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 2065 Lines: 46 On 13/06/12 09:12, Linus Walleij wrote: > On Wed, Jun 13, 2012 at 9:01 AM, Lee Jones wrote: > >> Board specific is fine, as the data is protected by a board specific >> property. Do you mean that the properties are *bus specific*? In which case >> I see your point and will apply the correct bindings. > > I cannot parse this, the board for me is a SoC, busses and a > number of components connected via e.g. I2C. > > Can you define what you mean with a "board specific property"? > It seems you are talking about what I would call an > "SoC-specific property", i.e. something out of a .dtsi file for > a certain SoC, whereas the .dts for an entire board is, > well, for a board, a set of components on a PCB. > > The arrangement of accelerometers and battery monitors on a > certain board is board-specific, and it is also by definition > bus-specific. Okay, let's put it another way. We can individualise any board, bus, platform, machine or system by placing all of the information in a DT node so long as we plonk it in the correct place within the Device Tree. However, we have just as much control by keeping them in separate structs in the C file and selecting the right one using the compatible sting. The real item for discussion is; if we have varying configurations for each of the i2c buses residing on the same SoC, do we really want to use different compatible strings to identify each one. If the answer is no, which I think it is, then I need to write the bindings and have everything individually configurable from Device Tree. While you're mulling this over, I'm just going to write the bindings anyway. -- Lee Jones Linaro ST-Ericsson Landing Team Lead M: +44 77 88 633 515 Linaro.org │ Open source software for ARM SoCs Follow Linaro: Facebook | Twitter | Blog -- 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/