From: me@felipebalbi•com (Felipe Balbi)
To: linux-arm-kernel@lists•infradead.org
Subject: [PATCH 2/2] USB: musb: omap2430: add mode change from A to B
Date: Thu, 22 Jul 2010 19:40:44 +0300 [thread overview]
Message-ID: <4C48748C.8040307@felipebalbi.com> (raw)
In-Reply-To: <877hknwnrb.fsf@anar.kanru.info>
On 07/22/2010 06:16 PM, Kan-Ru Chen wrote:
> Just curious about how to do this in a more automatic way.
>
> I think setup a daemon to monitor the musb_hdrc mode and try to alter
> it's state via sysfs interface will work, but it may be error prone and
> not always desirable solution.
>
> Can we query the id pin state periodically in the kernel and change to
> corresponding role?
the transceiver has an interrupt for id pin changes. You can use that
instead of polling.
--
balbi
next prev parent reply other threads:[~2010-07-22 16:40 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-15 10:23 [PATCH 1/2] USB: musb: add two states to handle vbus error Wang Hui
2010-03-15 10:23 ` [PATCH 2/2] USB: musb: omap2430: add mode change from A to B Wang Hui
2010-03-15 11:22 ` Sergei Shtylyov
2010-03-15 16:10 ` Felipe Balbi
2010-03-16 10:13 ` wanghui
2010-03-16 14:46 ` Felipe Balbi
2010-07-22 15:16 ` Kan-Ru Chen
2010-07-22 16:40 ` Felipe Balbi [this message]
2010-07-23 4:38 ` Kan-Ru Chen
2010-03-16 10:49 ` [PATCH 1/2] USB: musb: add two states to handle vbus error wanghui
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4C48748C.8040307@felipebalbi.com \
--to=me@felipebalbi$(echo .)com \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox