From: Kevin Hilman <khilman@deeprootsystems.com>
To: Ming Lei <tom.leiming@gmail.com>
Cc: Govindraj <govindraj.ti@gmail.com>, Pramod <pramod.gurav@ti.com>,
"Premi, Sanjeev" <premi@ti.com>,
"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>
Subject: Re: beagle hangs in uart3 disabling clocks
Date: Mon, 04 Oct 2010 11:54:29 -0700 [thread overview]
Message-ID: <87iq1hzt3u.fsf@deeprootsystems.com> (raw)
In-Reply-To: <AANLkTi=k+aZ2t2ZgXMcwuoBVPEjzyiGov1ZmSxe+Pe4-@mail.gmail.com> (Ming Lei's message of "Tue, 5 Oct 2010 00:17:23 +0800")
Ming Lei <tom.leiming@gmail.com> writes:
> 2010/10/4 Kevin Hilman <khilman@deeprootsystems.com>:
>>
>> Why? What do you need from the PM branch that is not in l-o master?
>
> Seems master branch works fine for me, my beagle board doesn't hang
> uart3 disabling clocks.
Master branch and PM branch have exactly the same functionality for
UART hwmods. The problem was that you manually enabled DEBUG in
omap_hwmod.c.
> I only want to have a try of the runtime pm feature of omap3, so use
> PM branch to do the test.
master branch and PM branch have exactly the same functionality for
runtime PM
Kevin
--
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
next prev parent reply other threads:[~2010-10-04 18:54 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-03 9:04 beagle hangs in uart3 disabling clocks Ming Lei
2010-10-03 17:27 ` Premi, Sanjeev
2010-10-04 12:13 ` Ming Lei
2010-10-04 12:17 ` Pramod
2010-10-04 12:38 ` Govindraj
2010-10-04 15:18 ` Ming Lei
2010-10-04 15:44 ` Kevin Hilman
2010-10-04 16:17 ` Ming Lei
2010-10-04 18:54 ` Kevin Hilman [this message]
2010-10-05 5:36 ` Ming Lei
2010-10-05 6:14 ` Paul Walmsley
2010-10-05 6:47 ` Ming Lei
2010-10-05 7:13 ` Pramod
2010-10-05 7:19 ` Paul Walmsley
2010-10-05 9:34 ` Pramod
2010-10-05 9:47 ` Paul Walmsley
2010-10-05 9:58 ` Pramod
2010-10-05 10:03 ` Paul Walmsley
2010-10-05 11:09 ` Pramod
2010-10-05 17:26 ` Paul Walmsley
2010-10-05 17:33 ` Kevin Hilman
2010-10-04 15:25 ` Kevin Hilman
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=87iq1hzt3u.fsf@deeprootsystems.com \
--to=khilman@deeprootsystems.com \
--cc=govindraj.ti@gmail.com \
--cc=linux-omap@vger.kernel.org \
--cc=pramod.gurav@ti.com \
--cc=premi@ti.com \
--cc=tom.leiming@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.