From: Krzysztof Kozlowski <krzk@kernel.org>
To: Varadarajan Narayanan <quic_varada@quicinc.com>,
bhelgaas@google.com, lpieralisi@kernel.org, kw@linux.com,
manivannan.sadhasivam@linaro.org, robh@kernel.org,
krzk+dt@kernel.org, conor+dt@kernel.org, andersson@kernel.org,
konradybcio@kernel.org, quic_srichara@quicinc.com,
quic_devipriy@quicinc.com, linux-arm-msm@vger.kernel.org,
linux-pci@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v12 1/4] dt-bindings: PCI: qcom: Add MHI registers for IPQ9574
Date: Wed, 12 Mar 2025 09:46:41 +0100 [thread overview]
Message-ID: <7b2d7f14-4274-4ff0-87a6-ac3dd649df4e@kernel.org> (raw)
In-Reply-To: <20250312084330.873994-2-quic_varada@quicinc.com>
On 12/03/2025 09:43, Varadarajan Narayanan wrote:
> Append the MHI register range to IPQ9574.
Why?
>
> Fixes: e0662dae178d ("dt-bindings: PCI: qcom: Document the IPQ9574 PCIe controller")
What is being fixed here?
> Signed-off-by: Varadarajan Narayanan <quic_varada@quicinc.com>
> ---
> New patch introduced in this patchset. MHI range was missed in the
> initial post
> ---
> Documentation/devicetree/bindings/pci/qcom,pcie.yaml | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/Documentation/devicetree/bindings/pci/qcom,pcie.yaml b/Documentation/devicetree/bindings/pci/qcom,pcie.yaml
> index 8f628939209e..77e66ab8764f 100644
> --- a/Documentation/devicetree/bindings/pci/qcom,pcie.yaml
> +++ b/Documentation/devicetree/bindings/pci/qcom,pcie.yaml
> @@ -175,7 +175,7 @@ allOf:
> properties:
> reg:
> minItems: 5
> - maxItems: 5
> + maxItems: 6
Why qcom,pcie-ipq6018 gets mhi? Nothing in commit msg mentions ipq6018.
> reg-names:
> items:
> - const: dbi # DesignWare PCIe registers
> @@ -183,6 +183,7 @@ allOf:
> - const: atu # ATU address space
> - const: parf # Qualcomm specific registers
> - const: config # PCIe configuration space
> + - const: mhi # MHI registers
Never tested - you introduce new warnings. AGAIN.
Properties xxx and xxx-names must have always the same constraints.
Best regards,
Krzysztof
next prev parent reply other threads:[~2025-03-12 8:46 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-12 8:43 [PATCH v12 0/4] Add PCIe support for Qualcomm IPQ5332 Varadarajan Narayanan
2025-03-12 8:43 ` [PATCH v12 1/4] dt-bindings: PCI: qcom: Add MHI registers for IPQ9574 Varadarajan Narayanan
2025-03-12 8:46 ` Krzysztof Kozlowski [this message]
2025-03-12 9:39 ` Varadarajan Narayanan
2025-03-12 10:38 ` Krzysztof Kozlowski
2025-03-12 8:43 ` [PATCH v12 2/4] arm64: dts: qcom: ipq9574: Add MHI to pcie nodes Varadarajan Narayanan
2025-03-12 8:43 ` [PATCH v12 3/4] arm64: dts: qcom: ipq5332: Add PCIe related nodes Varadarajan Narayanan
2025-03-12 8:43 ` [PATCH v12 4/4] arm64: dts: qcom: ipq5332-rdp441: Enable PCIe phys and controllers Varadarajan Narayanan
2025-03-12 13:07 ` [PATCH v12 0/4] Add PCIe support for Qualcomm IPQ5332 Rob Herring (Arm)
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=7b2d7f14-4274-4ff0-87a6-ac3dd649df4e@kernel.org \
--to=krzk@kernel.org \
--cc=andersson@kernel.org \
--cc=bhelgaas@google.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=konradybcio@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=kw@linux.com \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=lpieralisi@kernel.org \
--cc=manivannan.sadhasivam@linaro.org \
--cc=quic_devipriy@quicinc.com \
--cc=quic_srichara@quicinc.com \
--cc=quic_varada@quicinc.com \
--cc=robh@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