From mboxrd@z Thu Jan 1 00:00:00 1970 From: Linus Walleij Subject: Re: [RFC/PATCH v2 2/2] gpio-rcar: Add DT support Date: Fri, 31 May 2013 09:01:44 +0200 Message-ID: References: <1369136406-23800-1-git-send-email-laurent.pinchart+renesas@ideasonboard.com> <1369136406-23800-3-git-send-email-laurent.pinchart+renesas@ideasonboard.com> <4678059.RuWR6CiQ8n@avalon> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Return-path: In-Reply-To: <4678059.RuWR6CiQ8n@avalon> Sender: linux-sh-owner@vger.kernel.org To: Laurent Pinchart Cc: Laurent Pinchart , "linux-sh@vger.kernel.org" , "devicetree-discuss@lists.ozlabs.org" , "linux-arm-kernel@lists.infradead.org" , Magnus Damm , Guennadi Liakhovetski List-Id: devicetree@vger.kernel.org On Fri, May 31, 2013 at 3:20 AM, Laurent Pinchart wrote: > I've so far pushed GPIO and pinctrl patches for SH through Simon's tree due to > the many cross-dependencies between SH arch code and the GPIO and pinctrl > drivers. As the situation now stabilizes, we could now push the patches > through their respective subsystem trees. > > Simon, Linus, any opinion/preference on that ? Depends, if they are still large patch sets I'd prefer Simon to take it, but once the drivers are in place and going to maintenance mode I'll handle them in pinctrl. >> The above ranges are part of that document. > > What about replacing that with > > - gpio-ranges: Range of pins managed by the GPIO controller. > > Please refer to gpio.txt in this directory for details of gpio-ranges property > and the common GPIO bindings used by client devices. Go for it! Yours, Linus Walleij