From: Lucas Stach <l.stach@pengutronix.de>
To: Roberto Fichera <kernel@tekno-soft.it>
Cc: linux-pci@vger.kernel.org
Subject: Re: iMX6q PCIe phy link never came up on kernel v4.4.x
Date: Thu, 03 Mar 2016 10:32:07 +0100 [thread overview]
Message-ID: <1456997527.3772.37.camel@pengutronix.de> (raw)
In-Reply-To: <56D5E3DF.9030906@tekno-soft.it>
Hi Roberto,
Am Dienstag, den 01.03.2016, 19:47 +0100 schrieb Roberto Fichera:
> Hi There,
>
> Working on a custom iMX6q board I'm getting a PCIe phy link never came up, even if uboot seems detecting
> everything ok. My DTS is enabling PCIe with
>
> &pcie {
> pinctrl-names = "default";
> pinctrl-0 = <&pinctrl_pcie_reset>;
> reset-gpio = <&gpio7 12 0>;
> status = "okay";
> };
>
> The PCIe is connected to a PCIe-to-PCI TI XIO2001. The XIO2001 power is controlled by GPIO_9 and
> the corresponding fixed regulator is set as
>
> reg_pcie: regulator@4 {
> compatible = "regulator-fixed";
> reg = <4>;
> pinctrl-names = "default";
> pinctrl-0 = <&pinctrl_pcie_reg>;
> regulator-name = "MPCIE_3V3";
> regulator-min-microvolt = <3300000>;
> regulator-max-microvolt = <3300000>;
> gpio = <&gpio1 9 0>;
> regulator-always-on;
> enable-active-high;
> };
>
> so I'd like to know if there is any other special setup to do in order to get it to work on a v4.4.x kernel.
> Or anyway how to debug it.
>
> Any suggestion?
Is this a regression from earlier kernel versions?
If so, can you please revert 5c5fb40de8f14 (PCI: imx6: Add support for
active-low reset GPIO) and see if this helps?
Regards,
Lucas
--
Pengutronix e.K. | Lucas Stach |
Industrial Linux Solutions | http://www.pengutronix.de/ |
next prev parent reply other threads:[~2016-03-03 9:32 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-01 18:47 iMX6q PCIe phy link never came up on kernel v4.4.x Roberto Fichera
2016-03-02 17:13 ` Roberto Fichera
2016-03-02 19:56 ` Bjorn Helgaas
2016-03-03 9:15 ` Richard Zhu
2016-03-03 9:30 ` Roberto Fichera
2016-03-03 9:39 ` Richard Zhu
2016-03-03 10:55 ` Roberto Fichera
2016-03-03 14:34 ` Roberto Fichera
2016-03-03 18:34 ` Roberto Fichera
2016-03-04 7:11 ` Richard Zhu
2016-03-04 8:09 ` Roberto Fichera
2016-03-08 14:39 ` Roberto Fichera
2016-03-08 14:53 ` Lucas Stach
2016-03-08 14:59 ` Roberto Fichera
2016-03-10 17:35 ` Roberto Fichera
2016-03-14 8:44 ` Roberto Fichera
2016-03-15 11:08 ` Roberto Fichera
2016-03-15 14:04 ` Bjorn Helgaas
2016-03-15 14:10 ` Fabio Estevam
2016-03-15 14:29 ` Roberto Fichera
2016-03-16 14:19 ` Fabio Estevam
2016-03-16 21:33 ` Tim Harvey
2016-03-16 22:12 ` Fabio Estevam
2016-03-17 8:32 ` Roberto Fichera
2016-03-17 13:28 ` Fabio Estevam
2016-03-17 14:14 ` Roberto Fichera
2016-03-17 21:09 ` Fabio Estevam
2016-03-17 8:20 ` Roberto Fichera
2016-03-16 2:07 ` Richard Zhu
2016-03-03 9:32 ` Lucas Stach [this message]
2016-03-03 9:38 ` Roberto Fichera
2016-03-08 15:02 ` Fabio Estevam
2016-03-08 15:06 ` Roberto Fichera
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=1456997527.3772.37.camel@pengutronix.de \
--to=l.stach@pengutronix.de \
--cc=kernel@tekno-soft.it \
--cc=linux-pci@vger.kernel.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).