From mboxrd@z Thu Jan 1 00:00:00 1970 From: Felipe Balbi Subject: Re: [PATCH] ARM: OMAP: Fix board data to support device only, host only and OTG roles. Date: Mon, 31 May 2010 12:56:37 +0300 Message-ID: <20100531095637.GF16504@nokia.com> References: <987022.25256.qm@web180303.mail.gq1.yahoo.com> Reply-To: felipe.balbi@nokia.com Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Return-path: Received: from smtp.nokia.com ([192.100.122.230]:52460 "EHLO mgw-mx03.nokia.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755985Ab0EaJ5Y (ORCPT ); Mon, 31 May 2010 05:57:24 -0400 Content-Disposition: inline In-Reply-To: Sender: linux-omap-owner@vger.kernel.org List-Id: linux-omap@vger.kernel.org To: ext Grazvydas Ignotas Cc: David Brownell , Steve Sakoman , "linux-omap@vger.kernel.org" , Maulik Mankad , "linux-usb@vger.kernel.org" , "Balbi Felipe (Nokia-D/Helsinki)" , Tony Lindgren On Mon, May 31, 2010 at 11:44:05AM +0200, ext Grazvydas Ignotas wrote: >If a board is configured as host and driver is set to only support >peripheral it is perfectly fine for the driver not to allow that. But >why is the driver refusing OTG board setting if it's compiled to only >support host/peripheral? If I apply [1], it works perfectly fine for >me. What's wrong with degrading OTG to host/peripheral, did you really >mean to NAK [1], David? Why can't I compile musb in a >periperal/host-only mode if I have OTG connector? otg depends on usb suspend, which depends on runtime pm (I guess), without suspend, host negotiation protocol will never work which is required on OTG. I believe that was Dave's reasoning. -- balbi DefectiveByDesign.org