From: Linus Walleij Date: Tue, 20 Nov 2012 11:40:15 +0000 (+0100) Subject: gpiolib: let gpiochip_add_pin_range() specify offset X-Git-Tag: omap-for-v3.8/fixes-for-merge-window-v4-signed~94^2~15 X-Git-Url: http://git.openpandora.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=3f0f8670608766ef26a178d4e80cad3ce030fecc;p=pandora-kernel.git gpiolib: let gpiochip_add_pin_range() specify offset Like with commit 3c739ad0df5eb41cd7adad879eda6aa09879eb76 it is not always enough to specify all the pins of a gpio_chip from offset zero to be added to a pin map range, since the mapping from GPIO to pin controller may not be linear at all, but need to be broken into a few consecutive sub-ranges or 1-pin entries for complicated cases. The ranges may also be sparse. This alters the signature of the function to accept offsets into both the GPIO-chip local pinspace and the pin controller local pinspace. Reviewed-by: Stephen Warren Reviewed-by: Viresh Kumar Signed-off-by: Linus Walleij --- Reading git-diff-tree failed