Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754350Ab3HVULD (ORCPT ); Thu, 22 Aug 2013 16:11:03 -0400 Received: from avon.wwwdotorg.org ([70.85.31.133]:35293 "EHLO avon.wwwdotorg.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754263Ab3HVUK7 (ORCPT ); Thu, 22 Aug 2013 16:10:59 -0400 Message-ID: <5216704F.60007@wwwdotorg.org> Date: Thu, 22 Aug 2013 14:10:55 -0600 From: Stephen Warren User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130803 Thunderbird/17.0.8 MIME-Version: 1.0 To: Christian Ruppert CC: Linus Walleij , Patrice CHOTARD , "linux-kernel@vger.kernel.org" , Grant Likely , Rob Herring , Rob Landley , Sascha Leuenberger , Pierrick Hascoet , "linux-doc@vger.kernel.org" , Alexandre Courbot , "devicetree@vger.kernel.org" Subject: Re: [PATCH 2/4] pinmux: Add TB10x pinmux driver References: <20130618092516.GC18663@ab42.lan> <1371547751-13873-2-git-send-email-christian.ruppert@abilis.com> <20130805115118.GF20936@ab42.lan> <20130821155751.GB3046@ab42.lan> In-Reply-To: <20130821155751.GB3046@ab42.lan> X-Enigmail-Version: 1.4.6 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1791 Lines: 37 On 08/21/2013 09:57 AM, Christian Ruppert wrote: > On Wed, Aug 14, 2013 at 06:53:56PM +0200, Linus Walleij wrote: >> On Mon, Aug 5, 2013 at 1:51 PM, Christian Ruppert >> wrote: >>> [Me] >>>> I don't see any of the port concept creeping into the device tree >>>> in this version and that is how I think it should be kept: >>>> the "port" particulars is a thing for the driver and not the >>>> device tree. ... >>> In the driver under discussion, pin groups are defined for every >>> "interface" to make sure that interfaces can be requested in an >>> orthogonal way by different modules and modules don't have to be "aware" >>> of which interfaces are grouped into which port (and which other modules >>> request which other interfaces). A request either succeeds or fails. >>> Resource management (which interfaces can be mapped simultaneously) is >>> done inside the pinctrl driver. >> >> OK > > This actually looks 100% coherent with Documentation/pinctrl.txt. But > then I don't understand Stephen's request to introduce the concept of > "ports" in the device tree. IMHO ports are a hardware limitation which > should be managed inside the pinctrl driver and if possible not leak > out of it. Also (as stated above), the concept of "ports" does not even > exist in the pinmux framework so why introduce it for DT? > > I might have thoroughly misunderstood you here, Stephen. Please be > patient with me and explain once more. I don't think I asked for ports to be represented in DT. Do you have more context? -- 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/