linux-kernel - Re: [PATCH 14/16] usb: musb: dsps: add MUSB_DEVCTL

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: <20130726154450.GA29819@linutronix.de>
Date:	Fri, 26 Jul 2013 17:44:50 +0200
From:	Sebastian Andrzej Siewior <bigeasy@...utronix.de>
To:	Bin Liu <binmlist@...il.com>
Cc:	linux-usb@...r.kernel.org, linux-kernel@...r.kernel.org,
	balbi@...com, george.cherian@...com
Subject: Re: [PATCH 14/16] usb: musb: dsps: add MUSB_DEVCTL_SESSION back
 after removal

* Bin Liu | 2013-07-23 13:55:27 [-0500]:

>Hi Sebastian,
Hi Bin,

>> In my testing the bit remains set. How is the bit supposed to come back
>> after I connect a host device?
>The bit remains even when no device is plugged and ID ping is float?
After I set it, it remains set yes.

>what platform do you use to test it?
AM335x evm

>'a host device'? you meant a usb device? By the otg specs, the session
>will not automatically start. The user/app has to issue the command,
>either by SRP or HNP, or something else. In TI 3.2 kernel, there is
>workaround in otg_timer() to _toggle_ the SESSION bit to detect if ID
>pin is grounded, which means a USB device is connected.

I see. Let me check that TI kernel. The same thing happens however if
the musb is configured as host (not OTG). 

>Regards,
>-Bin.

Sebastian
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/