From: Lucas Stach <l.stach@pengutronix.de>
To: Roberto Fichera <kernel@tekno-soft.it>
Cc: Richard Zhu <hongxing.zhu@nxp.com>,
Bjorn Helgaas <helgaas@kernel.org>,
"linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>,
Richard Zhu <Richard.Zhu@freescale.com>
Subject: Re: iMX6q PCIe phy link never came up on kernel v4.4.x
Date: Tue, 08 Mar 2016 15:53:49 +0100 [thread overview]
Message-ID: <1457448829.3207.22.camel@pengutronix.de> (raw)
In-Reply-To: <56DEE426.8030902@tekno-soft.it>
Am Dienstag, den 08.03.2016, 15:39 +0100 schrieb Roberto Fichera:
> On 03/03/2016 07:34 PM, Roberto Fichera wrote:
> > On 03/03/2016 03:34 PM, Roberto Fichera wrote:
> >
> > I've also checked clock, pll, PMU_MISC1 and CCGR[45] registers, all looks fine
> > and exactly equal to uboot settings.
> >
> > However I'm investigating a possible HW issue in the LDVS pad wiring against
> > the bridge XIO2001. Let's see once this is also clarified.
>
> Our HW engineer has applied a fix to LVDS vs XIO2001 clock wiring. However I'm still getting the same problem.
>
> I've tried to boot a kernel with uboot not setting up the PCIe subsys and below there is the resulting kernel log.
> Note that the CCGR5 doesn't set the CG2 field associated to sata_clk_enable. I think this field should be set all 1 to
> enable the SATA ref at 100MHz, right?
>
No, the reference manual is a bit confusing about this, but the LVDS1
clock output is driven by sata_ref_100mhz, not the sata_clk gate.
So the only thing that needs to be enabled for LVDS clock output is the
100MHz clock output from PLL ENET. (Register CCM_ANALOG_PLL_ENETn bit
20).
Can you please try to revert the commit I pointed out in my last mail
and see if it helps? We might be holding the PCI device reset gpio at
the wrong level with this commit.
Regards,
Lucas
next prev parent reply other threads:[~2016-03-08 14:53 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 [this message]
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
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=1457448829.3207.22.camel@pengutronix.de \
--to=l.stach@pengutronix.de \
--cc=Richard.Zhu@freescale.com \
--cc=helgaas@kernel.org \
--cc=hongxing.zhu@nxp.com \
--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).