From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: mr.nuke.me@gmail.com, "Bjorn Andersson" <andersson@kernel.org>,
"Konrad Dybcio" <konrad.dybcio@linaro.org>,
"Lorenzo Pieralisi" <lpieralisi@kernel.org>,
"Krzysztof Wilczyński" <kw@linux.com>,
"Rob Herring" <robh@kernel.org>,
"Bjorn Helgaas" <bhelgaas@google.com>,
"Krzysztof Kozlowski" <krzysztof.kozlowski+dt@linaro.org>,
"Conor Dooley" <conor+dt@kernel.org>,
"Manivannan Sadhasivam" <manivannan.sadhasivam@linaro.org>
Cc: linux-arm-msm@vger.kernel.org, linux-pci@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 3/7] dt-bindings: PCI: qcom: Add IPQ9574 PCIe controller
Date: Thu, 11 Apr 2024 21:09:42 +0200 [thread overview]
Message-ID: <dcf612e6-cfe6-4a4d-8001-2e9912534807@linaro.org> (raw)
In-Reply-To: <bcb03c7d-f566-11cc-21e2-47e5c5a0776a@gmail.com>
On 11/04/2024 20:00, mr.nuke.me@gmail.com wrote:
>
>
> On 4/9/24 15:08, Krzysztof Kozlowski wrote:
>> On 09/04/2024 21:08, Alexandru Gagniuc wrote:
>>> IPQ9574 has PCIe controllers which are almost identical to IPQ6018.
>>> The only difference is that the "iface" clock is not required.
>>> Document this difference along with the compatible string.
>>>
>>> Signed-off-by: Alexandru Gagniuc <mr.nuke.me@gmail.com>
>>> ---
>>> .../devicetree/bindings/pci/qcom,pcie.yaml | 34 +++++++++++++++++++
>>> 1 file changed, 34 insertions(+)
>>>
>>> diff --git a/Documentation/devicetree/bindings/pci/qcom,pcie.yaml b/Documentation/devicetree/bindings/pci/qcom,pcie.yaml
>>> index cf9a6910b542..1915bea580d3 100644
>>> --- a/Documentation/devicetree/bindings/pci/qcom,pcie.yaml
>>> +++ b/Documentation/devicetree/bindings/pci/qcom,pcie.yaml
>>> @@ -26,6 +26,7 @@ properties:
>>> - qcom,pcie-ipq8064-v2
>>> - qcom,pcie-ipq8074
>>> - qcom,pcie-ipq8074-gen3
>>> + - qcom,pcie-ipq9574
>>> - qcom,pcie-msm8996
>>> - qcom,pcie-qcs404
>>> - qcom,pcie-sdm845
>>> @@ -397,6 +398,37 @@ allOf:
>>> - const: axi_m_sticky # AXI Master Sticky reset
>>> - const: axi_s_sticky # AXI Slave Sticky reset
>>>
>>
>> Where do you constrain the reg?
>
> I didn't realize that was also required -- the make checks should have
> picked this up too? I might be invoking the tests incorrectly.
>
> I should add the ipq9574 in the same list as ipq8074-gen3 and ipq6018,
> correct?
If you add new variant, look at existing compatibles where they appear.
If there is a if: constraining compatibles, then it's a hint you should
do the same for your device. So yes, you must constrain all properties
which are made flexible in top-level properties.
Best regards,
Krzysztof
next prev parent reply other threads:[~2024-04-11 19:09 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240409190833.3485824-1-mr.nuke.me@gmail.com>
2024-04-09 19:08 ` [PATCH v2 1/7] dt-bindings: clock: Add PCIe pipe related clocks for IPQ9574 Alexandru Gagniuc
2024-04-09 19:08 ` [PATCH v2 2/7] clk: qcom: gcc-ipq9574: Add PCIe pipe clocks Alexandru Gagniuc
2024-04-09 19:08 ` [PATCH v2 3/7] dt-bindings: PCI: qcom: Add IPQ9574 PCIe controller Alexandru Gagniuc
2024-04-09 20:08 ` Krzysztof Kozlowski
2024-04-11 18:00 ` mr.nuke.me
2024-04-11 19:09 ` Krzysztof Kozlowski [this message]
2024-04-09 19:08 ` [PATCH v2 4/7] PCI: qcom: Add support for IPQ9574 Alexandru Gagniuc
2024-04-10 11:50 ` Konrad Dybcio
2024-04-17 7:05 ` Manivannan Sadhasivam
2024-04-09 19:08 ` [PATCH v2 5/7] dt-bindings: phy: qcom,ipq8074-qmp-pcie: add ipq9574 gen3x2 PHY Alexandru Gagniuc
2024-04-09 20:09 ` Krzysztof Kozlowski
2024-04-09 20:19 ` mr.nuke.me
2024-04-09 20:28 ` Krzysztof Kozlowski
2024-04-10 6:59 ` Krzysztof Kozlowski
2024-04-10 7:02 ` Krzysztof Kozlowski
2024-04-10 16:29 ` mr.nuke.me
2024-04-10 19:36 ` Krzysztof Kozlowski
2024-04-11 17:24 ` mr.nuke.me
2024-04-11 19:08 ` Krzysztof Kozlowski
2024-04-09 20:49 ` Rob Herring
2024-04-09 19:08 ` [PATCH v2 6/7] phy: qcom-qmp-pcie: add support for " Alexandru Gagniuc
2024-04-09 19:08 ` [PATCH v2 7/7] arm64: dts: qcom: ipq9574: add PCIe2 nodes Alexandru Gagniuc
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=dcf612e6-cfe6-4a4d-8001-2e9912534807@linaro.org \
--to=krzysztof.kozlowski@linaro.org \
--cc=andersson@kernel.org \
--cc=bhelgaas@google.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=konrad.dybcio@linaro.org \
--cc=krzysztof.kozlowski+dt@linaro.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=mr.nuke.me@gmail.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