[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CACRpkdaJB1JnThtY6ZmQKDMY3Naci8cEaaK7bXfDUC2pvdgLsA@mail.gmail.com>
Date: Thu, 10 Dec 2015 16:10:58 +0100
From: Linus Walleij <linus.walleij@...aro.org>
To: Robert Jarzmik <robert.jarzmik@...e.fr>
Cc: Daniel Mack <daniel@...que.org>,
Haojian Zhuang <haojian.zhuang@...il.com>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"linux-gpio@...r.kernel.org" <linux-gpio@...r.kernel.org>,
"linux-arm-kernel@...ts.infradead.org"
<linux-arm-kernel@...ts.infradead.org>
Subject: Re: [PATCH 2/6] pinctrl: pxa: pxa2xx: add pin control skeleton
On Sat, Nov 21, 2015 at 7:04 PM, Robert Jarzmik <robert.jarzmik@...e.fr> wrote:
> Add a pincontrol driver for pxa2xx architecture, encompassing all pxa25x
> and pxa27x variants. This is only the pin muxing part of the driver.
>
> One specific consideration is also the memory space (MMIO), which is
> intertwined with the GPIO registers. To make things worse, the GPIO
> direction register also affect pin muxing, as it chooses the "kind" of
> pin, ie. the 4 output functions or 4 input functions.
>
> The mapping between pinctrl notions and PXA Technical Reference Manual
> is as follows :
> - a pin is obviously a pin
> - a group is also a pin, ie. group P101 is the pin 101
> - a mux function is an alternate function
> (ie. gpio-in, gpio-out, MMCLK, BTRTS, etc ...)
>
> The individual architecture (pxa27x, pxa25x) instantiate a pin control
> by providing a table of pins, each pin being provided a list of
> PXA_FUNCTION (alternate functions).
>
> Signed-off-by: Robert Jarzmik <robert.jarzmik@...e.fr>
Patch applied.
Yours,
Linus Walleij
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists