From: Ilya Ledvich <ilya@compulab.co.il>
To: Lucas Stach <l.stach@pengutronix.de>, Richard Zhu <hongxing.zhu@nxp.com>
Cc: Bjorn Helgaas <bhelgaas@google.com>,
Rob Herring <robh+dt@kernel.org>,
linux-pci@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, devicetree@vger.kernel.org
Subject: Re: [PATCH v3] PCI: imx6: Add PHY reference clock source support
Date: Wed, 10 Jan 2018 15:43:41 +0200 [thread overview]
Message-ID: <498e20c0-7b86-0f86-7555-64a012b85b9e@compulab.co.il> (raw)
In-Reply-To: <1515408232.12538.7.camel@pengutronix.de>
Hi Lucas,
On 01/08/2018 12:43 PM, Lucas Stach wrote:
> Am Donnerstag, den 04.01.2018, 15:52 +0200 schrieb Ilya Ledvich:
>> i.MX7D variant of the IP can use either Crystal Oscillator input
>> or internal clock input as a Reference Clock input for PCIe PHY.
>> Add support for an optional property 'fsl,pcie-phy-refclk-internal'.
>> If present then an internal clock input is used as PCIe PHY
>> reference clock source. By default an external oscillator input
>> is still used.
>>
>> Verified on Compulab SBC-iMX7 Single Board Computer.
>
> Sorry to get in late here, but I would rather have the external clock
> input modeled as a real clock and only use the internal clock if that
> isn't present.
>
I tried to follow the logic described in the iMX7 TRM, where external
oscillator is a default option. Additionally, the external clock input
model you've suggested, requires additional changes in the iMX7 SabreSD
board (and probably other boards which use an external input too)
devicetree files.
> Are you even sure that the i.MX7 clock you mention isn't the already
> documented "pcie_bus" clock? This one is also allowed to be sourced
> externally on the i.MX6.
To the best of my understanding it's not the pcie_bus clock, but I'm
absolutely sure. Could anybody from the BSP team guys elaborate on this
issue? Thanks a lot!
Best regards,
Ilya.
>> ---
>> changes since V2:
>> add a vendor prefix 'fsl' to a new property
>>
>> Documentation/devicetree/bindings/pci/fsl,imx6q-pcie.txt | 5 +++++
>> drivers/pci/dwc/pci-imx6.c | 8
>> +++++++-
>> 2 files changed, 12 insertions(+), 1 deletion(-)
>>
>> diff --git a/Documentation/devicetree/bindings/pci/fsl,imx6q-pcie.txt
>> b/Documentation/devicetree/bindings/pci/fsl,imx6q-pcie.txt
>> index 7b1e48b..1591a6a 100644
>> --- a/Documentation/devicetree/bindings/pci/fsl,imx6q-pcie.txt
>> +++ b/Documentation/devicetree/bindings/pci/fsl,imx6q-pcie.txt
>> @@ -50,6 +50,11 @@ Additional required properties for imx7d-pcie:
>> - "pciephy"
>> - "apps"
>>
>> +Additional optional properties for imx7d-pcie:
>> +- fsl,pcie-phy-refclk-internal: If present then an internal PLL
>> input is used
>> + as PCIe PHY reference clock source. By default an external
>> oscillator input
>> + is used.
>> +
>> Example:
>>
>> pcie@0x01000000 {
>> diff --git a/drivers/pci/dwc/pci-imx6.c b/drivers/pci/dwc/pci-imx6.c
>> index b734835..36812d3 100644
>> --- a/drivers/pci/dwc/pci-imx6.c
>> +++ b/drivers/pci/dwc/pci-imx6.c
>> @@ -61,6 +61,7 @@ struct imx6_pcie {
>> u32 tx_swing_low;
>> int link_gen;
>> struct regulator *vpcie;
>> + bool pciephy_refclk_sel;
>> };
>>
>> /* Parameters for the waiting for PCIe PHY PLL to lock on i.MX7 */
>> @@ -474,7 +475,9 @@ static void imx6_pcie_init_phy(struct imx6_pcie
>> *imx6_pcie)
>> switch (imx6_pcie->variant) {
>> case IMX7D:
>> regmap_update_bits(imx6_pcie->iomuxc_gpr,
>> IOMUXC_GPR12,
>> - IMX7D_GPR12_PCIE_PHY_REFCLK_SEL,
>> 0);
>> + IMX7D_GPR12_PCIE_PHY_REFCLK_SEL,
>> + imx6_pcie->pciephy_refclk_sel ?
>> + IMX7D_GPR12_PCIE_PHY_REFCLK_SEL :
>> 0);
>> break;
>> case IMX6SX:
>> regmap_update_bits(imx6_pcie->iomuxc_gpr,
>> IOMUXC_GPR12,
>> @@ -840,6 +843,9 @@ static int imx6_pcie_probe(struct platform_device
>> *pdev)
>> imx6_pcie->vpcie = NULL;
>> }
>>
>> + imx6_pcie->pciephy_refclk_sel =
>> + of_property_read_bool(node, "fsl,pcie-phy-refclk-
>> internal");
>> +
>> platform_set_drvdata(pdev, imx6_pcie);
>>
>> ret = imx6_add_pcie_port(imx6_pcie, pdev);
next prev parent reply other threads:[~2018-01-10 13:44 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-27 10:05 [PATCH] " Ilya Ledvich
2017-12-28 10:05 ` Richard Zhu
2017-12-31 8:31 ` [PATCH v2] " Ilya Ledvich
2018-01-02 22:54 ` Fabio Estevam
2018-01-04 13:52 ` [PATCH v3] " Ilya Ledvich
2018-01-08 3:13 ` Richard Zhu
2018-01-08 10:43 ` Lucas Stach
2018-01-10 13:43 ` Ilya Ledvich [this message]
2018-01-15 2:19 ` Richard Zhu
2018-03-07 11:54 ` Lorenzo Pieralisi
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=498e20c0-7b86-0f86-7555-64a012b85b9e@compulab.co.il \
--to=ilya@compulab.co.il \
--cc=bhelgaas@google.com \
--cc=devicetree@vger.kernel.org \
--cc=hongxing.zhu@nxp.com \
--cc=l.stach@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=robh+dt@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
all inboxes | Powered by JetHome®