Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754277Ab3H3ITm (ORCPT ); Fri, 30 Aug 2013 04:19:42 -0400 Received: from mail.abilis.ch ([195.70.19.74]:19058 "EHLO mail.abilis.ch" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752529Ab3H3ITj (ORCPT ); Fri, 30 Aug 2013 04:19:39 -0400 Date: Fri, 30 Aug 2013 10:19:06 +0200 From: Christian Ruppert To: Linus Walleij Cc: Stephen Warren , 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 Message-ID: <20130830081905.GB6766@ab42.lan> References: <20130618092516.GC18663@ab42.lan> <1371547751-13873-2-git-send-email-christian.ruppert@abilis.com> <20130805115118.GF20936@ab42.lan> <20130821155751.GB3046@ab42.lan> <20130829073542.GA23079@ab42.lan> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.20 (2009-12-10) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 2037 Lines: 45 On Thu, Aug 29, 2013 at 10:24:30AM +0200, Linus Walleij wrote: > On Thu, Aug 29, 2013 at 9:35 AM, Christian Ruppert > wrote: > > On Wed, Aug 28, 2013 at 08:49:36PM +0200, Linus Walleij wrote: > >> On Wed, Aug 21, 2013 at 5:57 PM, Christian Ruppert > >> wrote: > >> > On Wed, Aug 14, 2013 at 06:53:56PM +0200, Linus Walleij wrote: > >> >> > >> >> OK, that can also be called a "bank" or "register" but whatever. > >> > > >> > As you suggested below I re-read Documentation/pinctrl.txt and it got me > >> > even more confused: > >> > Am I right in my understanding that the whole concept of a > >> > "port/bank/register" or whatever we would like to call it does not exist > >> > in the pinctrl framework? > >> > >> Not that I know :-) > >> > >> If what it means is a number of registers from address x thru x+n > >> words in memory that is called a register range usually, the > >> Device Tree "regs" property. > >> > >> If you're referring to a subset of registers dealing with a batch > >> of pins or a single pin that can use whatever terminology you > >> want, I consider it a driver-internal detail. Some GPIO drivers > >> talk about "ports" when they have e.g. 2 x 32bit registers > >> handling a total of 64 pins, then that is port 0 and port 1 or > >> something like this, but it's really up to the driver. > > > > Actually, it's a set of pins the muxing of which is controlled by the > > same register. E.g. Port A is the set of all the pins which are > > controlled by register field A. > > What is wrong with calling that a "pin-set register" or something? Nothing. Except perhaps that I hope we can confine that concept to the driver and thus eliminate the need to talk about it altogether ;) Greetings, Christian -- 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/