[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20150309161608.GF3739@saruman.tx.rr.com>
Date: Mon, 9 Mar 2015 11:16:08 -0500
From: Felipe Balbi <balbi@...com>
To: Linus Walleij <linus.walleij@...aro.org>
CC: David Cohen <david.a.cohen@...ux.intel.com>,
Robert Baldyga <r.baldyga@...sung.com>,
Heikki Krogerus <heikki.krogerus@...ux.intel.com>,
MyungJoo Ham <myungjoo.ham@...sung.com>,
Chanwoo Choi <cw00.choi@...sung.com>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"linux-usb@...r.kernel.org" <linux-usb@...r.kernel.org>,
<baolu.lu@...ux.intel.com>, Felipe Balbi <balbi@...com>
Subject: Re: [PATCH v2] extcon: otg_gpio: add driver for USB OTG port
controlled by GPIO(s)
On Sat, Mar 07, 2015 at 09:06:22PM +0100, Linus Walleij wrote:
> On Fri, Feb 20, 2015 at 8:17 PM, David Cohen
> <david.a.cohen@...ux.intel.com> wrote:
> > On Fri, Feb 20, 2015 at 10:53:44AM +0100, Linus Walleij wrote:
>
> >> I would put this adjacent to the phy driver somewhere in drivers/usb/*
> >> and make the actual USB-driver thing handle its GPIOs directly.
> >> But I guess David and Felipe have already discussed that as we're
> >> seeing this patch?
> >
> > - The mux functions would be controlled by a possible new pinctrl-gpio
> > driver (Linus, your input here would be nice :)
>
> I don't understand what this means, does it mean a pin control function
> somewhere else controlled by a GPIO pin?
>
> Or do you mean a new combined pin control and GPIO driver (we have
> plenty of these).
>
> If you elaborate on what you need to do in that driver I might
> understand it better.
there's a discrete mux (not something integrated in the SoC) whose
select signal is tied to a GPIO (in some cases, more than one, but
usually people use 2-state muxes).
--
balbi
Download attachment "signature.asc" of type "application/pgp-signature" (820 bytes)
Powered by blists - more mailing lists