On Tue, Mar 6, 2012 at 1:22 AM, Stephen Warren <[email protected]> wrote:
> Recent pinctrl discussions concluded that gpiolib APIs should in fact do > whatever is required to mux a GPIO onto pins, by calling pinctrl APIs if > required. This change implements this for the Tegra GPIO driver, and removes > calls to the Tegra-specific APIs from drivers and board files. > > Cc: Chris Ball <[email protected]> > Cc: [email protected] > Signed-off-by: Stephen Warren <[email protected]> Acked-by: Linus Walleij <[email protected]> > Merging note: The first two (or at least the 2nd) patches can go through > the pinctrl susbsystem without issue. I will give Grant a chance to comment on the GPIO interaction doc atleast, then I'll apply them. > This patch should probably be taken > through the Tegra tree. Once patch 2 is in pinctrl, and considered stable, > I can just use that as a dependency for the branch containing this Tegra > patch. I assume that this series will go into 3.5 not 3.4, but I'm willing > to be surprised:-) Should be possible if my pinctrl-tegra-for-next-diet branch is considered stable and could be pulled into the Tegra tree for further augmenting by this and other patches! But I guess you'd need to merge some stable development base for the rest of the pinctrl stuff as well, shall I freeze the for-next branch with tegra diet stuff merged on top now? I can promise to just add new patches on top of that if it helps you. Is Olof the one to ask? Yours, Linus Walleij -- To unsubscribe from this list: send the line "unsubscribe linux-mmc" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
