Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752672AbcCYHlG (ORCPT ); Fri, 25 Mar 2016 03:41:06 -0400 Received: from mail-pa0-f67.google.com ([209.85.220.67]:33084 "EHLO mail-pa0-f67.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752008AbcCYHlE (ORCPT ); Fri, 25 Mar 2016 03:41:04 -0400 Date: Fri, 25 Mar 2016 15:40:51 +0800 From: Peter Chen To: Sanchayan Maity Cc: Peter.Chen@nxp.com, linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org, stefan@agner.ch, ivan.ivanov@linaro.org, linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org, shawnguo@kernel.org, marcel@ziswiler.com Subject: Re: [RFC PATCH 0/4] Implement USB device/host switch for Vybrid Message-ID: <20160325074051.GB22398@peterchendt> References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 862 Lines: 22 On Tue, Mar 15, 2016 at 02:08:26PM +0530, Sanchayan Maity wrote: > Hello Peter, > > The existing usage of extcon in Chipidea driver relies on OTG > registers. In case of SoC with dual role device but not a true > OTG controller, this does not work. Such SoC's should specify > the existing CI_HDRC_DUAL_ROLE_NOT_OTG flag and do the role > switch without checking any of the OTG registers in my opinion. > This is the case for Vybrid which uses a Chipidea IP but does > not have a true 5 pin OTG implemented. Sorry to reply you late due to my new born baby. Are you sure Vybrid is NOT OTG core? Afaik, it is uses the same IP base with other Freescale SoCs, just the IP core is 2.40a. When working at device mode, can you read vbus status through OTGSC? And if there is an ID pin (input pin) for Vybrid? I mean SoC, not the board. -- Best Regards, Peter Chen