From: Rob Herring <robh@kernel.org>
To: Richard Zhu <hongxing.zhu@nxp.com>
Cc: frank.li@nxp.com, l.stach@pengutronix.de, lpieralisi@kernel.org,
kwilczynski@kernel.org, mani@kernel.org, krzk+dt@kernel.org,
conor+dt@kernel.org, bhelgaas@google.com, shawnguo@kernel.org,
s.hauer@pengutronix.de, kernel@pengutronix.de,
festevam@gmail.com, linux-pci@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org,
imx@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v6 1/3] dt-bindings: PCI: dwc: Add one more reference clock
Date: Mon, 22 Sep 2025 11:50:47 -0500 [thread overview]
Message-ID: <20250922165047.GA436960-robh@kernel.org> (raw)
In-Reply-To: <20250917045238.1048484-2-hongxing.zhu@nxp.com>
On Wed, Sep 17, 2025 at 12:52:36PM +0800, Richard Zhu wrote:
> Add one more reference clock "extref" for a reference clock that comes
> from external crystal oscillator.
See what I just commented on v5.
>
> Signed-off-by: Richard Zhu <hongxing.zhu@nxp.com>
> Reviewed-by: Frank Li <Frank.Li@nxp.com>
> ---
> .../devicetree/bindings/pci/snps,dw-pcie-common.yaml | 6 ++++++
> 1 file changed, 6 insertions(+)
>
> diff --git a/Documentation/devicetree/bindings/pci/snps,dw-pcie-common.yaml b/Documentation/devicetree/bindings/pci/snps,dw-pcie-common.yaml
> index 34594972d8db..0134a759185e 100644
> --- a/Documentation/devicetree/bindings/pci/snps,dw-pcie-common.yaml
> +++ b/Documentation/devicetree/bindings/pci/snps,dw-pcie-common.yaml
> @@ -105,6 +105,12 @@ properties:
> define it with this name (for instance pipe, core and aux can
> be connected to a single source of the periodic signal).
> const: ref
> + - description:
> + Some dwc wrappers (like i.MX95 PCIes) have two reference clock
> + inputs, one from an internal PLL, the other from an off-chip crystal
> + oscillator. If present, 'extref' refers to a reference clock from
> + an external oscillator.
> + const: extref
> - description:
> Clock for the PHY registers interface. Originally this is
> a PHY-viewport-based interface, but some platform may have
> --
> 2.37.1
>
next prev parent reply other threads:[~2025-09-22 16:50 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-17 4:52 [PATCH v6 0/3] PCI: imx6: Add external reference clock mode support Richard Zhu
2025-09-17 4:52 ` [PATCH v6 1/3] dt-bindings: PCI: dwc: Add one more reference clock Richard Zhu
2025-09-17 22:13 ` Bjorn Helgaas
2025-09-22 16:50 ` Rob Herring [this message]
2025-09-17 4:52 ` [PATCH v6 2/3] dt-bindings: pci-imx6: Add one more external " Richard Zhu
2025-09-17 22:17 ` Bjorn Helgaas
2025-09-17 4:52 ` [PATCH v6 3/3] PCI: imx6: Add external reference clock mode support Richard Zhu
-- strict thread matches above, loose matches on Subject: below --
2025-09-17 3:51 [PATCH v6 0/3] " Richard Zhu
2025-09-17 3:51 ` [PATCH v6 1/3] dt-bindings: PCI: dwc: Add one more reference clock Richard Zhu
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=20250922165047.GA436960-robh@kernel.org \
--to=robh@kernel.org \
--cc=bhelgaas@google.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=festevam@gmail.com \
--cc=frank.li@nxp.com \
--cc=hongxing.zhu@nxp.com \
--cc=imx@lists.linux.dev \
--cc=kernel@pengutronix.de \
--cc=krzk+dt@kernel.org \
--cc=kwilczynski@kernel.org \
--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=lpieralisi@kernel.org \
--cc=mani@kernel.org \
--cc=s.hauer@pengutronix.de \
--cc=shawnguo@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).