Linux-ARM-Kernel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: mgreer@animalcreek.com (Mark A. Greer)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: OMAP AM3517/05: hwmod data: block WFI when EMAC active
Date: Tue, 8 Jan 2013 13:43:47 -0700	[thread overview]
Message-ID: <20130108204347.GC1876@animalcreek.com> (raw)
In-Reply-To: <alpine.DEB.2.00.1301081916190.18536@utopia.booyaka.com>

On Tue, Jan 08, 2013 at 07:21:16PM +0000, Paul Walmsley wrote:
> On Sun, 30 Dec 2012, Paul Walmsley wrote:

Hi Paul.

> > However, for some reason, we don't have an EMAC hwmod -- probably some 
> > bug in the data -- so set the flag on the MDIO hwmod data instead.
> 
> Mark and I discussed this in private E-mail.  Looks like I managed to 
> confuse AM33xx and AM3517 :-(  Here's the updated patch.
> 
> 
> - Paul
> 
> 
> From: Paul Walmsley <paul@pwsan.com>
> Date: Sun, 30 Dec 2012 10:36:36 -0700
> Subject: [PATCH] ARM: OMAP AM3517/05: hwmod data: block WFI when EMAC active
> 
> According to Mark Greer, on OMAP AM3517/3505 chips, the EMAC is unable
> to wake the ARM up from WFI:
> 
>     http://www.spinics.net/lists/arm-kernel/msg174734.html
> 
> Further troubleshooting was unable to narrow the problem down.  So we
> don't have much choice other than to block WFI when the EMAC is active
> with the HWMOD_BLOCK_WFI flag.
> 
> Based on Mark's original patch.  We're removing the omap_device-based
> pm_lats code, so a different approach was needed.
> 
> This second version contains some corrections thanks to Mark's review.
> 
> Signed-off-by: Paul Walmsley <paul@pwsan.com>
> Cc: Mark A. Greer <mgreer@animalcreek.com>
> ---
>  arch/arm/mach-omap2/omap_hwmod_3xxx_data.c |    8 +++++++-
>  1 file changed, 7 insertions(+), 1 deletion(-)
> 
> diff --git a/arch/arm/mach-omap2/omap_hwmod_3xxx_data.c b/arch/arm/mach-omap2/omap_hwmod_3xxx_data.c
> index 8bb2628..7af28b7 100644
> --- a/arch/arm/mach-omap2/omap_hwmod_3xxx_data.c
> +++ b/arch/arm/mach-omap2/omap_hwmod_3xxx_data.c
> @@ -3493,7 +3493,13 @@ static struct omap_hwmod am35xx_emac_hwmod = {
>  	.name		= "davinci_emac",
>  	.mpu_irqs	= am35xx_emac_mpu_irqs,
>  	.class		= &am35xx_emac_class,
> -	.flags		= HWMOD_NO_IDLEST,
> +	/*
> +	 * According to Mark Greer, the MPU will not return from WFI
> +	 * when the EMAC signals an interrupt.  We're missing an EMAC
> +	 * hwmod for some reason, so add the flag to the MDIO instead.
> +	 * http://www.spinics.net/lists/arm-kernel/msg174734.html
> +	 */
> +	.flags		= (HWMOD_NO_IDLEST | HWMOD_BLOCK_WFI),
>  };

Sorry to nag but I think the comment needs to be updated to remove the
sentence about the missing EMAC hwmod.

Mark
--

  reply	other threads:[~2013-01-08 20:43 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-12-30 18:31 [PATCH] ARM: OMAP AM3517/05: hwmod data: block WFI when EMAC active Paul Walmsley
2013-01-08 19:21 ` Paul Walmsley
2013-01-08 20:43   ` Mark A. Greer [this message]
2013-01-17 19:21     ` Paul Walmsley
2013-01-17 22:31       ` Mark A. Greer

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=20130108204347.GC1876@animalcreek.com \
    --to=mgreer@animalcreek.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    /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