From: shawn.guo@freescale.com (Shawn Guo)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: mx6: Fix suspend/resume with PCI
Date: Thu, 7 Aug 2014 11:30:49 +0800 [thread overview]
Message-ID: <20140807033048.GP2167@dragon> (raw)
In-Reply-To: <CAOMZO5DZEvKLLjU_V645S=yGP7ePUFyyHzQPp56sUA-mDGkFzA@mail.gmail.com>
On Thu, Aug 07, 2014 at 12:24:37AM -0300, Fabio Estevam wrote:
> On Thu, Aug 7, 2014 at 12:08 AM, Shawn Guo <shawn.guo@freescale.com> wrote:
> > On Wed, Aug 06, 2014 at 11:52:29PM -0300, Fabio Estevam wrote:
> >> On Wed, Aug 6, 2014 at 11:18 PM, Shawn Guo <shawn.guo@freescale.com> wrote:
> >>
> >> > I intend to agree with Lucas that we should align our testing and
> >> > understanding on the issue before trying to fix it.
> >> >
> >> > Again, I do not see this issue on my TO1.2 chip, but only TO1.5,
> >> > aka Rev 1.3, one.
> >>
> >> Which version is your sabresd with TO1.2? Mine is rev C2 and the
> >> suspend/resume issue happens 100%.
> >
> > The label on the board says it's Rev B.
>
> If I remember correctly you are testing suspend/resume with no PCI
> card connected to the TO1.2 board, right?
Right. I do not have any PCIe device on hands, so all my testing are
without PCIe device connected, and TO1.2 works while TO1.5 doesn't.
Shawn
>
> I have just tried suspend/resume without any PCI card connect and it
> does work fine.
>
> Only when I have the PCI card connected I get the hang.
next prev parent reply other threads:[~2014-08-07 3:30 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-07 0:39 [PATCH] ARM: mx6: Fix suspend/resume with PCI Fabio Estevam
2014-08-07 2:18 ` Shawn Guo
2014-08-07 2:52 ` Fabio Estevam
2014-08-07 3:08 ` Shawn Guo
2014-08-07 3:24 ` Fabio Estevam
2014-08-07 3:30 ` Shawn Guo [this message]
2014-08-07 10:04 ` Lucas Stach
2014-08-07 11:55 ` Fabio Estevam
2014-09-30 10:12 ` Bjørn Erik Nilsen
[not found] ` <E1XYuVl-0006Jx-Mh@bombadil.infradead.org>
2014-09-30 11:42 ` Fabio Estevam
2014-10-22 17:13 ` Fabio Estevam
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=20140807033048.GP2167@dragon \
--to=shawn.guo@freescale.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).