[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <1371446435.2776.122@driftwood>
Date: Mon, 17 Jun 2013 00:20:35 -0500
From: Rob Landley <rob@...dley.net>
To: Linus Walleij <linus.walleij@...ricsson.com>
Cc: linux-kernel@...r.kernel.org, linux-arm-kernel@...ts.infradead.org,
Stephen Warren <swarren@...dia.com>,
Anmar Oueja <anmar.oueja@...aro.org>,
Linus Walleij <linus.walleij@...aro.org>,
Christian Ruppert <christian.ruppert@...lis.com>
Subject: Re: [PATCH] pinctrl: update GPIO range doc
On 06/16/2013 05:18:29 AM, Linus Walleij wrote:
> From: Linus Walleij <linus.walleij@...aro.org>
>
> This updates the GPIO range documentation with the API changes
> for sparse/random/arbitrary pin-to-GPIO mappings.
Acked-by: Rob Landley <rob@...dley.net>
Why isn't this part of the pinctrl series you posted right afterwards?
(It should go in through that maintainer...)
> For all functionalities dealing with pin biasing, pin muxing etc,
> the pin
> -controller subsystem will subtract the range's .base offset from the
> passed
> -in gpio number, and add the ranges's .pin_base offset to retrive a
> pin number.
> -After that, the subsystem passes it on to the pin control driver, so
> the driver
> +controller subsystem will look up the corresponding pin number from
> the passed
> +in gpio number, and use the ranges internals to retrive a pin
> number. After
Range's perhaps?
Rob--
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