> -----Original Message----- > From: Greg KH [mailto:gregkh@xxxxxxxxxxxxxxxxxxx] > Sent: Monday, September 22, 2014 9:16 PM > To: Zhu Richard-R65037 > Cc: linux-pci-owner@xxxxxxxxxxxxxxx; stable@xxxxxxxxxxxxxxx; linux- > pci@xxxxxxxxxxxxxxx; l.stach@xxxxxxxxxxxxxx > Subject: Re: [PATCH RFC 2/2] PCI: imx6: add imx6sx pcie support > > On Mon, Sep 22, 2014 at 05:01:38PM +0800, Richard Zhu wrote: > > - imx6sx pcie has its own standalone pcie power supply. > > In order to turn on the imx6sx pcie power during initialization. Add > > the pcie regulator and the gpc regmap into the imx6sx pcie structure. > > - imx6sx pcie has the new added reset mechanism, add the reset > > operations into the initialization. > > - another dis_axi clk is mandatory required by imx6sx pcie. > > Add one new clk named pcie_sec into imx6_pcie structure. > > - pcie_ref_125m is not used as pcie_phy clk anymore on imx6sx. > > The parent clk (pcie_ref) of the pcie_bus(lvds1_gate) is used as > > pcie_phy clk. > > - Register one PM call-back, enter/exit L2 state of the ASPM during > > system suspend/resume. > > - wait the clocks to stabilize after the pcie_ref_en > > (IMX6Q_GPR1_PCIE_REF_CLK_EN) is set. > > > > Signed-off-by: Richard Zhu <r65037@xxxxxxxxxxxxx> > > --- > > arch/arm/boot/dts/imx6sx-sdb.dts | 15 ++ > > arch/arm/boot/dts/imx6sx.dtsi | 33 ++-- > > arch/arm/mach-imx/Kconfig | 1 + > > drivers/pci/host/pci-imx6.c | 228 ++++++++++++++++++++++++- > --- > > include/linux/mfd/syscon/imx6q-iomuxc-gpr.h | 14 ++ > > 5 files changed, 249 insertions(+), 42 deletions(-) > > <formletter> > > This is not the correct way to submit patches for inclusion in the stable > kernel tree. Please read Documentation/stable_kernel_rules.txt > for how to do this properly. > > </formletter> [Richard] Roger that, thanks for your reminder. It's my fault to make a mistake to send the patch review to table kernel mail-list. Sorry about that. Best Regards Richard Zhu -- To unsubscribe from this list: send the line "unsubscribe stable" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html