From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <linux-kernel-owner@vger.kernel.org>
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
	id S1752685AbbCGUGY (ORCPT <rfc822;w@1wt.eu>);
	Sat, 7 Mar 2015 15:06:24 -0500
Received: from mail-ob0-f181.google.com ([209.85.214.181]:36353 "EHLO
	mail-ob0-f181.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
	with ESMTP id S1752446AbbCGUGW (ORCPT
	<rfc822;linux-kernel@vger.kernel.org>);
	Sat, 7 Mar 2015 15:06:22 -0500
MIME-Version: 1.0
In-Reply-To: <20150220191700.GB15303@psi-dev26.jf.intel.com>
References: <1419288217-19262-1-git-send-email-david.a.cohen@linux.intel.com>
	<1424375984-26241-1-git-send-email-david.a.cohen@linux.intel.com>
	<54E6D721.9070107@samsung.com>
	<CACRpkdYkcjgvYQBuGtu2-JGvtM+y-zrMD=0xyiZLS=b3gEGMOw@mail.gmail.com>
	<20150220191700.GB15303@psi-dev26.jf.intel.com>
Date: Sat, 7 Mar 2015 21:06:22 +0100
Message-ID: <CACRpkdYq2oDewDKfcv9H_2Sio+s6R5H-4GugYTwA0+=-xqn3ZQ@mail.gmail.com>
Subject: Re: [PATCH v2] extcon: otg_gpio: add driver for USB OTG port
 controlled by GPIO(s)
From: Linus Walleij <linus.walleij@linaro.org>
To: David Cohen <david.a.cohen@linux.intel.com>
Cc: Robert Baldyga <r.baldyga@samsung.com>,
        Heikki Krogerus <heikki.krogerus@linux.intel.com>,
        MyungJoo Ham <myungjoo.ham@samsung.com>,
        Chanwoo Choi <cw00.choi@samsung.com>,
        "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
        "linux-usb@vger.kernel.org" <linux-usb@vger.kernel.org>,
        baolu.lu@linux.intel.com, Felipe Balbi <balbi@ti.com>
Content-Type: text/plain; charset=UTF-8
Sender: linux-kernel-owner@vger.kernel.org
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org

On Fri, Feb 20, 2015 at 8:17 PM, David Cohen
<david.a.cohen@linux.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.

Yours,
Linus Walleij