All of lore.kernel.org
 help / color / mirror / Atom feed
From: York Sun <york.sun@nxp.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] setup of PEX_GCLK_RATIO in E500 CPUs(P2010) missing ?
Date: Tue, 29 Aug 2017 15:43:52 +0000	[thread overview]
Message-ID: <VI1PR04MB2078BD88DFE745A5F69D39FB9A9F0@VI1PR04MB2078.eurprd04.prod.outlook.com> (raw)
In-Reply-To: <1504012881.32677.3.camel@infinera.com>

On 08/29/2017 06:21 AM, Joakim Tjernlund wrote:
> On Tue, 2017-08-29 at 12:47 +0200, Joakim Tjernlund wrote:
>> As we are looking at PCI stuff ATM I would like to ask
>> about PEX_GCLK_RATIO in E500 CPUs. I cannot find this is setup
>> at all for E500 but I THINK this is required.
>>
>> In 83xx one do:
>> get_clocks();
>> /* Configure the PCIE controller core clock ratio */
>> out_le32(hose_cfg_base + PEX_GCLK_RATIO,
> 
> A bit strange with out_le32 instead of out_be32 ?
> 
>> (((bus ? gd->arch.pciexp2_clk : gd->arch.pciexp1_clk)
>> / 1000000) * 16) / 333);
>> udelay(1000000);
>>
>> Any clues?
>>
>>   Jocke
> Seems like only 83xx is setting this parameter.
> 
> Anyhow, I put together this patch:
> 
> --- a/drivers/pci/fsl_pci_init.c
> +++ b/drivers/pci/fsl_pci_init.c
> @@ -322,6 +322,10 @@ void fsl_pci_init(struct pci_controller *hose, struct fsl_pci_info *pci_info)
>   
>          pci_setup_indirect(hose, cfg_addr, cfg_data);
>   
> +       /* Configure the PCIE controller core clock ratio */
> +       pci_hose_write_config_dword(hose, dev, 0x440, (gd->bus_clk / 333333333) * 16);
> +       /* udelay(1000000) needed here ?*/
> +
>          block_rev = in_be32(&pci->block_rev1);
>          if (PEX_IP_BLK_REV_2_2 <= block_rev) {
>                  pi = &pci->pit[2];      /* 0xDC0 */
> 
> Any chance this will work for all supported FSL PCIe controllers?
> 

Jocke,

You don't need to program this register if the actual PCIe clock is the 
same as default. Since SerDes reference clock has to be 100MHz for PCIe 
protocol, my guess is the PCIe clock is always correct. The bus_clk you 
are referring is not the PCIe clock. Again, I am not a PCIe expert, I 
could be wrong. Since PCIe (SerDes) has been working on multiple 
platforms, I guess the clock is correct.

York

  reply	other threads:[~2017-08-29 15:43 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-29 10:47 Joakim Tjernlund
2017-08-29 13:21 ` Joakim Tjernlund
2017-08-29 15:43   ` York Sun [this message]
2017-08-29 17:06     ` Joakim Tjernlund
2017-08-29 17:33       ` York Sun
2017-08-30 13:05         ` Joakim Tjernlund
2017-08-30 15:25           ` York Sun
2017-08-30 16:04             ` Joakim Tjernlund
2017-09-05 12:45             ` Joakim Tjernlund
2017-09-06  9:36               ` Mingkai Hu
2017-09-06 12:22                 ` Joakim Tjernlund
2017-09-07  6:45               ` Mingkai Hu
2017-09-07  6:55                 ` Joakim Tjernlund
2017-09-07  7:16                   ` Mingkai Hu
2017-08-29 14:59 ` York Sun

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=VI1PR04MB2078BD88DFE745A5F69D39FB9A9F0@VI1PR04MB2078.eurprd04.prod.outlook.com \
    --to=york.sun@nxp.com \
    --cc=u-boot@lists.denx.de \
    --subject='Re: [U-Boot] setup of PEX_GCLK_RATIO in E500 CPUs(P2010) missing ?' \
    /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

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.