From: Sergei Shtylyov <sshtylyov@mvista.com>
To: Paul Walmsley <paul@pwsan.com>
Cc: linux-omap@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
Tero Kristo <t-kristo@ti.com>
Subject: Re: [PATCHv3 6/7] ARM: OMAP2+: CM: increase the module disable timeout
Date: Tue, 19 Jun 2012 16:46:32 +0400 [thread overview]
Message-ID: <4FE074A8.5010109@mvista.com> (raw)
In-Reply-To: <20120618061611.30632.51094.stgit@dusk>
Hello.
On 18-06-2012 10:16, Paul Walmsley wrote:
> Increase the timeout for disabling an IP block to five milliseconds.
> This is to handle the usb_host_fs idle latency, which takes almost
> four milliseconds after a host controller reset.
> This is the second of two patches needed to resolve the following
> boot warning:
> omap_hwmod: usb_host_fs: _wait_target_disable failed
> Signed-off-by: Paul Walmsley<paul@pwsan.com>
> Cc: Tero Kristo<t-kristo@ti.com>
[...]
> diff --git a/arch/arm/mach-omap2/omap_hwmod_44xx_data.c b/arch/arm/mach-omap2/omap_hwmod_44xx_data.c
> index 6b0aedc..a428305 100644
> --- a/arch/arm/mach-omap2/omap_hwmod_44xx_data.c
> +++ b/arch/arm/mach-omap2/omap_hwmod_44xx_data.c
> @@ -30,6 +30,7 @@
> #include<plat/mmc.h>
> #include<plat/dmtimer.h>
> #include<plat/common.h>
> +#include<plat/usb.h>
How this hunk is related?
WBR, Sergei
WARNING: multiple messages have this Message-ID (diff)
From: sshtylyov@mvista.com (Sergei Shtylyov)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCHv3 6/7] ARM: OMAP2+: CM: increase the module disable timeout
Date: Tue, 19 Jun 2012 16:46:32 +0400 [thread overview]
Message-ID: <4FE074A8.5010109@mvista.com> (raw)
In-Reply-To: <20120618061611.30632.51094.stgit@dusk>
Hello.
On 18-06-2012 10:16, Paul Walmsley wrote:
> Increase the timeout for disabling an IP block to five milliseconds.
> This is to handle the usb_host_fs idle latency, which takes almost
> four milliseconds after a host controller reset.
> This is the second of two patches needed to resolve the following
> boot warning:
> omap_hwmod: usb_host_fs: _wait_target_disable failed
> Signed-off-by: Paul Walmsley<paul@pwsan.com>
> Cc: Tero Kristo<t-kristo@ti.com>
[...]
> diff --git a/arch/arm/mach-omap2/omap_hwmod_44xx_data.c b/arch/arm/mach-omap2/omap_hwmod_44xx_data.c
> index 6b0aedc..a428305 100644
> --- a/arch/arm/mach-omap2/omap_hwmod_44xx_data.c
> +++ b/arch/arm/mach-omap2/omap_hwmod_44xx_data.c
> @@ -30,6 +30,7 @@
> #include<plat/mmc.h>
> #include<plat/dmtimer.h>
> #include<plat/common.h>
> +#include<plat/usb.h>
How this hunk is related?
WBR, Sergei
next prev parent reply other threads:[~2012-06-19 12:47 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-18 6:15 [PATCHv3 0/7] ARM: OMAP: core/hwmod: first set of fixes for 3.5-rc Paul Walmsley
2012-06-18 6:15 ` Paul Walmsley
2012-06-18 6:15 ` [PATCHv3 1/7] ARM: OMAP: PM: Lock clocks list while generating summary Paul Walmsley
2012-06-18 6:15 ` Paul Walmsley
2012-06-18 6:16 ` [PATCHv3 2/7] ARM: OMAP2+: hwmod code/data: fix 32K sync timer Paul Walmsley
2012-06-18 6:16 ` Paul Walmsley
2012-06-18 6:16 ` [PATCHv3 3/7] ARM: OMAP4+: hwmod: fix issue causing IPs not going back to Smart-Standby Paul Walmsley
2012-06-18 6:16 ` Paul Walmsley
2012-06-18 6:16 ` [PATCHv3 4/7] ARM: OMAP4: hwmod data: fix 32k sync timer idle modes Paul Walmsley
2012-06-18 6:16 ` Paul Walmsley
2012-06-18 6:16 ` [PATCHv3 5/7] ARM: OMAP4: clock data: add clockdomains for clocks used as main clocks Paul Walmsley
2012-06-18 6:16 ` Paul Walmsley
2012-06-18 9:35 ` Cousson, Benoit
2012-06-18 9:35 ` Cousson, Benoit
2012-06-18 15:45 ` Paul Walmsley
2012-06-18 15:45 ` Paul Walmsley
2012-06-18 21:36 ` Cousson, Benoit
2012-06-18 21:36 ` Cousson, Benoit
2012-06-18 6:16 ` [PATCHv3 6/7] ARM: OMAP2+: CM: increase the module disable timeout Paul Walmsley
2012-06-18 6:16 ` Paul Walmsley
2012-06-19 12:46 ` Sergei Shtylyov [this message]
2012-06-19 12:46 ` Sergei Shtylyov
2012-06-21 21:10 ` Paul Walmsley
2012-06-21 21:10 ` Paul Walmsley
2012-06-18 6:16 ` [PATCHv3 7/7] ARM: OMAP2+: mux: fix sparse warning Paul Walmsley
2012-06-18 6:16 ` Paul Walmsley
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=4FE074A8.5010109@mvista.com \
--to=sshtylyov@mvista.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=paul@pwsan.com \
--cc=t-kristo@ti.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.