From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756007AbbCaRUp (ORCPT ); Tue, 31 Mar 2015 13:20:45 -0400 Received: from mail-qg0-f42.google.com ([209.85.192.42]:36335 "EHLO mail-qg0-f42.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753992AbbCaRUi (ORCPT ); Tue, 31 Mar 2015 13:20:38 -0400 MIME-Version: 1.0 In-Reply-To: <20150331140034.GE28951@linux-mips.org> References: <1427757416-14491-1-git-send-email-abrestic@chromium.org> <20150331140034.GE28951@linux-mips.org> Date: Tue, 31 Mar 2015 10:20:37 -0700 X-Google-Sender-Auth: U_POoJEBNBQcw1MNtBR4sE1lJmM Message-ID: Subject: Re: [PATCH V2 0/3] pinctrl: Support for IMG Pistachio From: Andrew Bresticker To: Ralf Baechle Cc: Linus Walleij , Alexandre Courbot , "devicetree@vger.kernel.org" , "linux-gpio@vger.kernel.org" , Linux-MIPS , "linux-kernel@vger.kernel.org" , Ezequiel Garcia , James Hartley , James Hogan Content-Type: text/plain; charset=UTF-8 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, Mar 31, 2015 at 7:00 AM, Ralf Baechle wrote: > On Mon, Mar 30, 2015 at 04:16:53PM -0700, Andrew Bresticker wrote: > >> This series adds support for the system pin and GPIO controller on the IMG >> Pistachio SoC. Pistachio's system pin controller manages 99 pins, 90 of >> which are MFIOs which can be muxed between multiple functions or used >> as GPIOs. The GPIO control for the 90 MFIOs is broken up into banks >> of 16. Pistachio also has a second pin controller, the RPU pin controller, >> which will be supported by a future patchset through an extension to this >> driver. >> >> Test on an IMG Pistachio BuB. Based on mips-for-linux-next which inluces my >> series adding Pistachio platform support [1]. A branch with this series is >> available at [2]. > > Does this mean you want me to funnel this through the MIPS tree? If so, > could I have an Ack from the maintainers? Linus mentioned in v1 that if the only dependency was a Kconfig symbol that he could take it through his tree. I'm fine either way, though it would be slightly more convenient for it to go through the MIPS tree. Linus? Thanks, Andrew