linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: tomasz.figa@gmail.com (Tomasz Figa)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/2] ARM: EXYNOS: Support Suspend-to-RAM on EXYNOS5420
Date: Fri, 20 Dec 2013 22:23:41 +0100	[thread overview]
Message-ID: <1591935.tG52kkhDHl@flatron> (raw)
In-Reply-To: <CAOesGMjfcTki4qqD-ZP2zt3ERLRF9DX5_K5rfJXfx1KGa5bG-g@mail.gmail.com>

On Friday 20 of December 2013 13:22:06 Olof Johansson wrote:
> On Fri, Dec 20, 2013 at 3:38 AM, Abhilash Kesavan
> <kesavan.abhilash@gmail.com> wrote:
> > Hi Sunil,
> >
> > On Fri, Dec 20, 2013 at 3:56 PM, sunil joshi <sjoshi.open@gmail.com> wrote:
> >> Hi Abhilash,
> >> I saw another patch in chrome tree ..by Andrew Bresticker
> >> which may be relevant here ..
> >>
> >> Just wondering if you missed adding this ? or this is not needed ?
> >> You did not face any issue in getting core to suspend ?
> >
> > This has not been added for Exynos5250 in mainline yet. We did notice
> > that the system would fail to suspend on the rare occasion (~1% of the
> > time on exynos5250) when we repeatedly suspended and resumed the
> > system.
> >
> > I have not run s2r stress tests, but have had no issues suspending the
> > system in my limited testing. We can probably let this be for now as
> > the system would resume fine even on a failed suspend. I will do some
> > stress testing and then post if needed.
> 
> Hold on, you're claiming that this patch you've posted has only seen
> very limited testing, and that you are aware of failures?
> 
> Don't merge known-broken code into the mainline kernel.

I'm afraid that a "failed suspend" does not really mean a failure here,
but let me wait for clarification of things I asked in another part of
this thread.

Best regards,
Tomasz

  reply	other threads:[~2013-12-20 21:23 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-16 12:01 [PATCH 1/2] ARM: EXYNOS: Support Suspend-to-RAM on EXYNOS5420 Abhilash Kesavan
2013-12-16 12:01 ` [PATCH 2/2] ARM: dts: Add node for GPIO keys on SMDK5420 Abhilash Kesavan
2013-12-16 12:48 ` [PATCH 1/2] ARM: EXYNOS: Support Suspend-to-RAM on EXYNOS5420 Bartlomiej Zolnierkiewicz
2013-12-17  3:10   ` Abhilash Kesavan
2013-12-20 10:26     ` sunil joshi
2013-12-20 11:38       ` Abhilash Kesavan
2013-12-20 11:53         ` sunil joshi
2013-12-20 21:22         ` Olof Johansson
2013-12-20 21:23           ` Tomasz Figa [this message]
2013-12-20 21:25             ` Olof Johansson
2013-12-20 21:25               ` Tomasz Figa
2013-12-21  7:06           ` Abhilash Kesavan
2013-12-20 21:19       ` Tomasz Figa
2013-12-20 21:37         ` Olof Johansson
2013-12-20 21:53           ` Tomasz Figa
2013-12-21  7:40             ` Abhilash Kesavan
2013-12-21  1:15         ` Doug Anderson
     [not found]           ` <CAPQV+nO=Xe=z669QxCJSerrm-xP0b=WtyPveyh2uTcM2B3i5KQ@mail.gmail.com>
2014-01-18  2:44             ` Abhilash Kesavan
2013-12-16 13:27 ` Vaibhav Bedia
2013-12-16 16:15   ` Tomasz Figa
2013-12-20 21:37 ` Tomasz Figa
2013-12-21  7:18   ` Abhilash Kesavan

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=1591935.tG52kkhDHl@flatron \
    --to=tomasz.figa@gmail.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;
as well as URLs for NNTP newsgroup(s).