From: David Brownell <david-b@pacbell.net>
To: Kalle Jokiniemi <kalle.jokiniemi@digia.com>
Cc: lrg@slimlogic.co.uk, linux-usb@vger.kernel.org,
linux-omap@vger.kernel.org, jouni.hogander@nokia.com,
broonie@sirena.org.uk
Subject: Re: [PATCH 0/2] TWL: USB: Start using twl4030/5030 regulator driver
Date: Fri, 13 Feb 2009 14:35:58 -0800 [thread overview]
Message-ID: <200902131435.58674.david-b@pacbell.net> (raw)
In-Reply-To: <1234519020.17391.167.camel@ubuntu>
On Friday 13 February 2009, Kalle Jokiniemi wrote:
> I ran into some trouble with the merged fix. For some reason clearing
> the VUSB3V1_DEV_GRP register causes VUSB_DEDICATED2.VUSB3V1_SLEEP bit to
> be enabled. This means that once VUSB3V1_DEV_GRP is put back to enabled
> state (VUSB3V1 changed to be part of P1 group again), VUSB3V1 does not
> go ACTIVE, but SLEEP state instead.
>
> Anyone have a clue what might cause this?
Curious. No ... is that specific to some TWL revision?
I'll poke around after I get this new board working better for me.
- Dave
next prev parent reply other threads:[~2009-02-13 22:36 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-11 7:06 [PATCH 0/2] TWL: USB: Start using twl4030/5030 regulator driver Kalle Jokiniemi
[not found] ` <1234336002-26372-1-git-send-email-kalle.jokiniemi-sMOQStClEysAvxtiuMwx3w@public.gmane.org>
2009-02-11 7:06 ` [PATCH 1/2] TWL: USB: disable VUSB regulators when cable unplugged Kalle Jokiniemi
2009-02-11 7:06 ` [PATCH 2/2] USB: OTG: Twl4030 depends on REGULATOR_TWL4030 Kalle Jokiniemi
2009-02-11 7:23 ` [PATCH 0/2] TWL: USB: Start using twl4030/5030 regulator driver David Brownell
[not found] ` <200902102323.30395.david-b-yBeKhBN/0LDR7s880joybQ@public.gmane.org>
2009-02-11 10:47 ` Kalle Jokiniemi
2009-02-13 9:57 ` Kalle Jokiniemi
2009-02-13 22:35 ` David Brownell [this message]
2009-02-20 8:56 ` Kalle Jokiniemi
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=200902131435.58674.david-b@pacbell.net \
--to=david-b@pacbell.net \
--cc=broonie@sirena.org.uk \
--cc=jouni.hogander@nokia.com \
--cc=kalle.jokiniemi@digia.com \
--cc=linux-omap@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=lrg@slimlogic.co.uk \
/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