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 v3]PCI: imx6: enable pcie on imx6sx sdb and imx6qdl sabreauto.
Date: Mon, 29 Sep 2014 13:03:08 +0800 [thread overview]
Message-ID: <1411966997-27118-1-git-send-email-r65037@freescale.com> (raw)
Main changes since the v2:
1. the async reset input need ref clock to sync internally, add one
10us delay between clks enable and the set of the pcie_ref_clk_en.
2. reformat imx6sx pcie dts, and split the dts changes into three part,
imx6sx pcie,imx6sx-sdb board, gpc dts.
3. add the pcie_phy-supply for imx6sx in dts and binding document.
4. figure out that display_axi clock is required by imx6sx pcie inbount
axi port. Add one more clk for imx6sx pcie.
5. Regarding to Lucas' suggestion, move "program correct class for RC"
from dw_pcie_host_init(), to dw_pcie_setup_rc().
6. add one re-store msi data function. Because that pcie controller
maybe powered off during system suspend, and the msi data configuration
would be lost. this functions can be used to restore the msi data
during the resume callback.
7. fix one possible dead lock during imx6sx pcie suspend resume
stress tests.
[PATCH v3 1/9] PCI: imx6: wait the clocks to stabilize after ref_en
[PATCH v3 2/9] PCI: imx6: enable pcie on imx6qdl sabreauto
[PATCH v3 3/9] PCI: imx6: update dts and binding for imx6sx pcie
[PATCH v3 4/9] PCI: imx6: add syscon into gpc dts
[PATCH v3 5/9] PCI: imx6: add imx6sx pcie related gpr bits
[PATCH v3 6/9] PCI: imx6: enable pcie on imx6sx sdb board
[PATCH v3 7/9] PCI: imx6: add imx6sx pcie support
[PATCH v3 8/9] PCI: designware: refine setup_rc and add msi data
[PATCH v3 9/9] PCI: imx6: Fix possible dead lock
next reply other threads:[~2014-09-29 5:33 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-29 5:03 Richard Zhu [this message]
2014-09-29 5:03 ` [PATCH v3 1/9] PCI: imx6: wait the clocks to stabilize after ref_en Richard Zhu
2014-09-29 5:03 ` [PATCH v3 2/9] PCI: imx6: enable pcie on imx6qdl sabreauto Richard Zhu
2014-09-29 9:56 ` Lucas Stach
2014-09-30 2:18 ` Hong-Xing.Zhu
2014-09-29 5:03 ` [PATCH v3 3/9] PCI: imx6: update dts and binding for imx6sx pcie Richard Zhu
2014-09-29 10:13 ` Lucas Stach
2014-09-30 2:58 ` Hong-Xing.Zhu
2014-09-29 5:03 ` [PATCH v3 4/9] PCI: imx6: add syscon into gpc dts Richard Zhu
2014-09-29 5:03 ` [PATCH v3 5/9] PCI: imx6: add imx6sx pcie related gpr bits definitions Richard Zhu
2014-09-29 5:03 ` [PATCH v3 6/9] PCI: imx6: enable pcie on imx6sx sdb board Richard Zhu
2014-09-29 5:03 ` [PATCH v3 7/9] PCI: imx6: add imx6sx pcie support Richard Zhu
2014-09-29 10:18 ` Lucas Stach
2014-09-30 2:37 ` Hong-Xing.Zhu
2014-09-29 5:03 ` [PATCH v3 8/9] PCI: designware: refine setup_rc and add msi data restore Richard Zhu
2014-09-29 10:26 ` Lucas Stach
2014-09-29 5:03 ` [PATCH v3 9/9] PCI: imx6: Fix possible dead lock Richard Zhu
2014-09-29 10:38 ` Lucas Stach
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=1411966997-27118-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).