linux-pci.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Richard Zhu <r65037@freescale.com>
To: <linux-pci-owner@vger.kernel.org>
Cc: <linux-pci@vger.kernel.org>, <shawn.guo@freescale.com>,
	<festevam@gmail.com>, <l.stach@pengutronix.de>,
	<tharvey@gateworks.com>
Subject: [PATCH v2]PCI: imx6: enable pcie on imx6sx sdb and imx6qdl sabreauto.
Date: Tue, 23 Sep 2014 12:11:33 +0800	[thread overview]
Message-ID: <1411445498-20250-1-git-send-email-r65037@freescale.com> (raw)

Hi Tim:
After I changed the wait clocks stabilize delay after pcie_ref_en is set
in this patch-set.
Can you help to make a double check whether it's ok or not at your side?

Thanks in advanced.

Main changes since the v1:
1. Regarding to Lucas' comments, seperated the enalbe pcie on
imx6qdl sabreauto patch.
2. Add the description why the wait clock stabilize delay should
be run after pcie_ref_en is set.
3. Return 0 directly in suspend call back.

Main changes since the RFC:
Thanks for quick review from Lucas.
1. seperate the smashed patch-set.
2. remove the "power-on-gpio".
3. add/update the pcie-supply of the dts and binding.
4. 

[PATCH v2 1/5] PCI: imx6: enable pcie on imx6qdl sabreauto
[PATCH v2 2/5] PCI: imx6: wait the clocks to stabilize after ref_en
[PATCH v2 3/5] PCI: imx6: update dts and binding for imx6sx pcie
[PATCH v2 4/5] PCI: imx6: add imx6sx pcie related gpr bits
[PATCH v2 5/5] PCI: imx6: add imx6sx pcie support

             reply	other threads:[~2014-09-23  4:39 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-23  4:11 Richard Zhu [this message]
2014-09-23  4:11 ` [PATCH v2 1/5] PCI: imx6: enable pcie on imx6qdl sabreauto Richard Zhu
2014-09-23  9:19   ` Lucas Stach
2014-09-23 12:40   ` Fabio Estevam
2014-09-24  2:54     ` Hong-Xing.Zhu
2014-09-24 21:04       ` Fabio Estevam
2014-09-25  1:21         ` Hong-Xing.Zhu
2014-09-25  1:39           ` Fabio Estevam
2014-09-25  2:02             ` Hong-Xing.Zhu
2014-09-23  4:11 ` [PATCH v2 2/5] PCI: imx6: wait the clocks to stabilize after ref_en Richard Zhu
2014-09-23  9:56   ` Lucas Stach
2014-09-23 12:28     ` Tim Harvey
2014-09-25  5:21       ` Hong-Xing.Zhu
2014-10-01 18:00       ` Tim Harvey
2014-10-02  2:26         ` Hong-Xing.Zhu
2014-09-23 12:45   ` Fabio Estevam
2014-10-24  1:51   ` Fabio Estevam
2014-10-24  2:46     ` Richard.Zhu
2014-09-23  4:11 ` [PATCH v2 3/5] PCI: imx6: update dts and binding for imx6sx pcie Richard Zhu
2014-09-23 10:19   ` Lucas Stach
2014-09-24  9:43     ` Hong-Xing.Zhu
2014-09-23  4:11 ` [PATCH v2 4/5] PCI: imx6: add imx6sx pcie related gpr bits definitions Richard Zhu
2014-09-23 10:21   ` Lucas Stach
2014-09-24  4:45     ` Hong-Xing.Zhu
2014-09-23  4:11 ` [PATCH v2 5/5] PCI: imx6: add imx6sx pcie support Richard Zhu
2014-09-23 11:00   ` Lucas Stach
2014-09-24  7:09     ` Hong-Xing.Zhu
2014-09-24  9:46       ` Lucas Stach
2014-09-24 10:15         ` Hong-Xing.Zhu
2014-09-23  9:18 ` [PATCH v2]PCI: imx6: enable pcie on imx6sx sdb and imx6qdl sabreauto Lucas Stach
2014-09-23  9:29   ` Hong-Xing.Zhu

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=1411445498-20250-1-git-send-email-r65037@freescale.com \
    --to=r65037@freescale.com \
    --cc=festevam@gmail.com \
    --cc=l.stach@pengutronix.de \
    --cc=linux-pci-owner@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=shawn.guo@freescale.com \
    --cc=tharvey@gateworks.com \
    /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).