From: Rebecca Schultz Zavin <rschultz@google.com>
To: "Eugeny S. Mints" <eugeny.mints@gmail.com>
Cc: Peter Barada <peterb@logicpd.com>,
linux-omap <linux-omap@vger.kernel.org>
Subject: Re: Anyone have MUSB working on PM branch?
Date: Mon, 4 May 2009 18:05:12 -0700 [thread overview]
Message-ID: <aed62de90905041805s74cba19cu2db014fa4f792cc4@mail.gmail.com> (raw)
In-Reply-To: <49FC137F.70809@gmail.com>
I'm pretty sure we do, though I doubt we have it doing the right thing
across power events, we're still in the process of getting all our
drivers to behave. Check out the android omap tree:
http://android.git.kernel.org/?p=kernel/omap.git;a=shortlog;h=refs/heads/android-omap-2.6.29
Rebecca
On Sat, May 2, 2009 at 2:33 AM, Eugeny S. Mints <eugeny.mints@gmail.com> wrote:
> Peter,
>
> Peter Barada wrote:
>>
>> All,
>>
>>
>
> [skip]
>>
>> 1) Has anyone gotten the MUSB in the latest PM branch working?
>>
>
> I believe MUSB has not yet been validated on the PM branch as of 4/29
> according to Kevin.
>
> Eugeny
>>
>> 2) Outside of setting up the pinmux, is there anything else necessary to
>> get the MUSB to come up?
>>
>> 3) Any ideas on how to fix this?
>>
>>
>>
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-omap" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2009-05-05 1:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-01 18:06 Anyone have MUSB working on PM branch? Peter Barada
2009-05-02 9:33 ` Eugeny S. Mints
2009-05-05 1:05 ` Rebecca Schultz Zavin [this message]
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=aed62de90905041805s74cba19cu2db014fa4f792cc4@mail.gmail.com \
--to=rschultz@google.com \
--cc=eugeny.mints@gmail.com \
--cc=linux-omap@vger.kernel.org \
--cc=peterb@logicpd.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
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