From: Shawn Guo <shawn.guo@freescale.com>
To: Fabio Estevam <festevam@gmail.com>
Cc: Lucas Stach <l.stach@pengutronix.de>,
"Hong-Xing.Zhu@freescale.com" <Hong-Xing.Zhu@freescale.com>,
"linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>,
Sascha Hauer <kernel@pengutronix.de>,
"Bjorn Helgaas" <bhelgaas@google.com>,
Shawn Guo <shawn.guo@linaro.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>
Subject: Re: The imx6q suspend/resume is broken on 3.16-rc due to PCIe
Date: Mon, 21 Jul 2014 11:19:38 +0800 [thread overview]
Message-ID: <20140721031937.GI8537@dragon> (raw)
In-Reply-To: <CAOMZO5DS2NR57kzrjzMBSh8urxSB84Y0TPSJCaGjf7q3cPZPmg@mail.gmail.com>
On Sun, Jul 20, 2014 at 11:55:42PM -0300, Fabio Estevam wrote:
> On Sun, Jul 20, 2014 at 11:50 PM, Shawn Guo <shawn.guo@freescale.com> wrote:
> > On Fri, Jul 18, 2014 at 11:21:48AM +0200, Lucas Stach wrote:
> >> However I seem to have a board with rev 1.1 silicon and although the pci
> >> driver starts up it never establishes a link. So my board may just work
> >> by chance as I don't really know the differences between rev 1.1 silicon
> >> and later revisions.
> >
> > Lucas, thanks for the info.
> >
> > I just checked my board on which the issue is seen, and found it has a
> > rev 1.3 silicon. I just tested on a board with rev 1.2 and did not even
> > see the issue.
> >
> > Richard,
> >
> > Is this an issue only with rev 1.3?
>
> I could see this issue on my board with rev 1.2.
Hmm, that's strange. I tested two imx6q-sabresd boards with rev 1.2
silicon, and did not see this issue. Hopefully, someone else can also
test.
Shawn
WARNING: multiple messages have this Message-ID (diff)
From: shawn.guo@freescale.com (Shawn Guo)
To: linux-arm-kernel@lists.infradead.org
Subject: The imx6q suspend/resume is broken on 3.16-rc due to PCIe
Date: Mon, 21 Jul 2014 11:19:38 +0800 [thread overview]
Message-ID: <20140721031937.GI8537@dragon> (raw)
In-Reply-To: <CAOMZO5DS2NR57kzrjzMBSh8urxSB84Y0TPSJCaGjf7q3cPZPmg@mail.gmail.com>
On Sun, Jul 20, 2014 at 11:55:42PM -0300, Fabio Estevam wrote:
> On Sun, Jul 20, 2014 at 11:50 PM, Shawn Guo <shawn.guo@freescale.com> wrote:
> > On Fri, Jul 18, 2014 at 11:21:48AM +0200, Lucas Stach wrote:
> >> However I seem to have a board with rev 1.1 silicon and although the pci
> >> driver starts up it never establishes a link. So my board may just work
> >> by chance as I don't really know the differences between rev 1.1 silicon
> >> and later revisions.
> >
> > Lucas, thanks for the info.
> >
> > I just checked my board on which the issue is seen, and found it has a
> > rev 1.3 silicon. I just tested on a board with rev 1.2 and did not even
> > see the issue.
> >
> > Richard,
> >
> > Is this an issue only with rev 1.3?
>
> I could see this issue on my board with rev 1.2.
Hmm, that's strange. I tested two imx6q-sabresd boards with rev 1.2
silicon, and did not see this issue. Hopefully, someone else can also
test.
Shawn
next prev parent reply other threads:[~2014-07-21 3:19 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-24 15:36 The imx6q suspend/resume is broken on 3.16-rc due to PCIe Shawn Guo
2014-06-24 15:36 ` Shawn Guo
2014-06-24 16:13 ` Lucas Stach
2014-06-24 16:13 ` Lucas Stach
2014-06-25 6:12 ` Shawn Guo
2014-06-25 6:12 ` Shawn Guo
2014-06-24 19:37 ` Fabio Estevam
2014-06-24 19:37 ` Fabio Estevam
2014-06-25 6:22 ` Shawn Guo
2014-06-25 6:22 ` Shawn Guo
2014-06-25 10:50 ` Fabio Estevam
2014-06-25 10:50 ` Fabio Estevam
2014-06-25 10:50 ` Lucas Stach
2014-06-25 10:50 ` Lucas Stach
2014-06-25 12:53 ` Shawn Guo
2014-06-25 12:53 ` Shawn Guo
2014-06-26 8:43 ` Lucas Stach
2014-06-26 8:43 ` Lucas Stach
2014-06-28 14:37 ` Shawn Guo
2014-06-28 14:37 ` Shawn Guo
2014-06-30 13:44 ` Lucas Stach
2014-06-30 13:44 ` Lucas Stach
2014-07-01 6:51 ` Shawn Guo
2014-07-01 6:51 ` Shawn Guo
2014-07-07 9:10 ` Lucas Stach
2014-07-07 9:10 ` Lucas Stach
2014-07-07 13:55 ` Shawn Guo
2014-07-07 13:55 ` Shawn Guo
2014-07-16 6:55 ` Shawn Guo
2014-07-16 6:55 ` Shawn Guo
2014-07-17 13:55 ` Lucas Stach
2014-07-17 13:55 ` Lucas Stach
2014-07-18 2:11 ` Hong-Xing.Zhu
2014-07-18 2:11 ` Hong-Xing.Zhu at freescale.com
2014-07-18 9:21 ` Lucas Stach
2014-07-18 9:21 ` Lucas Stach
2014-07-21 2:50 ` Shawn Guo
2014-07-21 2:50 ` Shawn Guo
2014-07-21 2:55 ` Fabio Estevam
2014-07-21 2:55 ` Fabio Estevam
2014-07-21 3:19 ` Shawn Guo [this message]
2014-07-21 3:19 ` Shawn Guo
2014-06-25 12:46 ` Shawn Guo
2014-06-25 12:46 ` Shawn Guo
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=20140721031937.GI8537@dragon \
--to=shawn.guo@freescale.com \
--cc=Hong-Xing.Zhu@freescale.com \
--cc=bhelgaas@google.com \
--cc=festevam@gmail.com \
--cc=kernel@pengutronix.de \
--cc=l.stach@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-pci@vger.kernel.org \
--cc=shawn.guo@linaro.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 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.