On Wed, Aug 28, 2013 at 08:49:36PM +0200, Linus Walleij wrote:
> On Wed, Aug 21, 2013 at 5:57 PM, Christian Ruppert
> <christian.ruppert@xxxxxxxxxx> 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.
Greetings,
Christian
--
Christian Ruppert , <christian.ruppert@xxxxxxxxxx>
/|
Tel: +41/(0)22 816 19-42 //| 3, Chemin du Pré-Fleuri
_// | bilis Systems CH-1228 Plan-les-Ouates
--
To unsubscribe from this list: send the line "unsubscribe linux-doc" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
