SUPERH platform development
 help / color / mirror / Atom feed
From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: linux-sh@vger.kernel.org
Subject: Re: [PATCH] ARM: shmobile: Add Lager clock workarounds for SDHI and MMCIF
Date: Wed, 19 Mar 2014 10:01:57 +0000	[thread overview]
Message-ID: <1613079.afJ2ECLXhd@avalon> (raw)
In-Reply-To: <20140318125247.21670.94176.sendpatchset@w520>

Hi Magnus,

On Wednesday 19 March 2014 10:03:32 Magnus Damm wrote:
> On Tue, Mar 18, 2014 at 10:25 PM, Laurent Pinchart wrote:
> > On Tuesday 18 March 2014 21:52:47 Magnus Damm wrote:
> >> From: Magnus Damm <damm@opensource.se>
> >> 
> >> Add MMCIF1, SDHI0 and SDHI2 to the clock workaround list for
> >> Lager multiplatform. Without these additional lines wakeup
> >> from Suspend-to-RAM never happens.
> > 
> > What about fixing the root cause instead of piling up hacks ?
> 
> -ENOPATCH? =)
> 
> Perhaps we need to learn what the root cause is before making a proper
> patch?

Sure :-) Could you elaborate a bit on what issue the patch fixes ? Is S2R 
broken completely, only with multiplatform kernels, only when runtime PM is 
enabled ? The commit message isn't very explicit about that.

Ben mentioned that he was working on a workaround to use 
drivers/sh/pm_runtime.c as-is with multi-platform kernels. Assuming the S2R 
problem is limited to multi-platform kernels, I would prefer that workaround 
if that's fine with you as well.

-- 
Regards,

Laurent Pinchart


  parent reply	other threads:[~2014-03-19 10:01 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-18 12:52 [PATCH] ARM: shmobile: Add Lager clock workarounds for SDHI and MMCIF Magnus Damm
2014-03-18 13:25 ` Laurent Pinchart
2014-03-18 13:48 ` Ben Dooks
2014-03-18 13:59 ` Laurent Pinchart
2014-03-18 14:31 ` Ben Dooks
2014-03-18 15:27 ` Geert Uytterhoeven
2014-03-18 16:03 ` Laurent Pinchart
2014-03-19  0:02 ` Simon Horman
2014-03-19  0:07 ` Simon Horman
2014-03-19  1:03 ` Magnus Damm
2014-03-19 10:01 ` Laurent Pinchart [this message]
2014-03-19 12:30 ` Magnus Damm

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=1613079.afJ2ECLXhd@avalon \
    --to=laurent.pinchart@ideasonboard.com \
    --cc=linux-sh@vger.kernel.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