Re: [PATCH] ARM: OMAP: Fix board data to support device only, host only and OTG roles.

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



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
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html


[Index of Archives]     [Linux Arm (vger)]     [ARM Kernel]     [ARM MSM]     [Linux Tegra]     [Linux WPAN Networking]     [Linux Wireless Networking]     [Maemo Users]     [Linux USB Devel]     [Video for Linux]     [Linux Audio Users]     [Yosemite Trails]     [Linux Kernel]     [Linux SCSI]

  Powered by Linux