From: Krzysztof Kozlowski <krzk@kernel.org>
To: Richard Zhu <hongxing.zhu@nxp.com>
Cc: robh@kernel.org, krzk+dt@kernel.org, conor+dt@kernel.org,
bhelgaas@google.com, frank.li@nxp.com, l.stach@pengutronix.de,
lpieralisi@kernel.org, kwilczynski@kernel.org, mani@kernel.org,
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 v9 2/3] dt-bindings: PCI: pci-imx6: Add external reference clock input
Date: Sun, 2 Nov 2025 17:04:33 +0100 [thread overview]
Message-ID: <20251102-complex-placid-frog-09cbed@kuoka> (raw)
In-Reply-To: <20251031031907.1390870-3-hongxing.zhu@nxp.com>
On Fri, Oct 31, 2025 at 11:19:06AM +0800, Richard Zhu wrote:
> i.MX95 PCIes have two reference clock inputs: one from internal PLL, the
> other from off chip crystal oscillator. The "extref" clock refers to a
> reference clock from an external crystal oscillator.
>
> Add external reference clock input for i.MX95 PCIes.
>
> Signed-off-by: Richard Zhu <hongxing.zhu@nxp.com>
> Reviewed-by: Frank Li <Frank.Li@nxp.com>
> ---
> Documentation/devicetree/bindings/pci/fsl,imx6q-pcie.yaml | 7 +++++--
> 1 file changed, 5 insertions(+), 2 deletions(-)
>
> diff --git a/Documentation/devicetree/bindings/pci/fsl,imx6q-pcie.yaml b/Documentation/devicetree/bindings/pci/fsl,imx6q-pcie.yaml
> index ca5f2970f217c..703c776d28e6f 100644
> --- a/Documentation/devicetree/bindings/pci/fsl,imx6q-pcie.yaml
> +++ b/Documentation/devicetree/bindings/pci/fsl,imx6q-pcie.yaml
> @@ -44,7 +44,7 @@ properties:
>
> clock-names:
> minItems: 3
> - maxItems: 5
> + maxItems: 6
>
> interrupts:
> minItems: 1
> @@ -212,14 +212,17 @@ allOf:
> then:
> properties:
> clocks:
> - maxItems: 5
> + minItems: 4
> + maxItems: 6
> clock-names:
> + minItems: 4
> items:
> - const: pcie
> - const: pcie_bus
> - const: pcie_phy
> - const: pcie_aux
> - const: ref
This was required last time. Nothing in commit msg explained changing
that.
> + - const: extref # Optional
Drop the comment, do not repeat the schema. And why only this is marked
as optional if 'ref' is optional as well now.
It is v9, can you please really think thoroughly what you are sending,
so obvious issues won't be there?
Best regards,
Krzysztof
next prev parent reply other threads:[~2025-11-02 16:04 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-31 3:19 [PATCH v9 0/3] PCI: imx6: Add external reference clock mode support Richard Zhu
2025-10-31 3:19 ` [PATCH v9 1/3] dt-bindings: PCI: dwc: Add external reference clock input Richard Zhu
2025-10-31 3:19 ` [PATCH v9 2/3] dt-bindings: PCI: pci-imx6: " Richard Zhu
2025-11-02 16:04 ` Krzysztof Kozlowski [this message]
2025-11-04 9:02 ` Hongxing Zhu
2025-10-31 3:19 ` [PATCH v9 3/3] PCI: imx6: Add external reference clock input mode support 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=20251102-complex-placid-frog-09cbed@kuoka \
--to=krzk@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=robh@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