linux-kernel - Re: [RFC PATCH 0/4] Implement USB device/host switch for Vybrid

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20160325074051.GB22398@peterchendt>
Date:	Fri, 25 Mar 2016 15:40:51 +0800
From:	Peter Chen <hzpeterchen@...il.com>
To:	Sanchayan Maity <maitysanchayan@...il.com>
Cc:	Peter.Chen@....com, linux-usb@...r.kernel.org,
	linux-kernel@...r.kernel.org, stefan@...er.ch,
	ivan.ivanov@...aro.org, linux-arm-kernel@...ts.infradead.org,
	devicetree@...r.kernel.org, shawnguo@...nel.org,
	marcel@...wiler.com
Subject: Re: [RFC PATCH 0/4] Implement USB device/host switch for Vybrid

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