From: Bjorn Helgaas <helgaas@kernel.org>
To: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>
Cc: Andy Gross <agross@kernel.org>,
Bjorn Andersson <bjorn.andersson@linaro.org>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzk@kernel.org>,
Jingoo Han <jingoohan1@gmail.com>,
Gustavo Pimentel <gustavo.pimentel@synopsys.com>,
Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>,
Bjorn Helgaas <bhelgaas@google.com>,
Stanimir Varbanov <svarbanov@mm-sol.com>,
Manivannan Sadhasivam <manivannan.sadhasivam@linaro.org>,
Vinod Koul <vkoul@kernel.org>,
linux-arm-msm@vger.kernel.org, linux-pci@vger.kernel.org,
devicetree@vger.kernel.org,
Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
Subject: Re: [PATCH v4 2/8] dt-bindings: pci/qcom,pcie: resets are not defined for msm8996
Date: Thu, 28 Apr 2022 09:35:08 -0500 [thread overview]
Message-ID: <20220428143508.GA12269@bhelgaas> (raw)
In-Reply-To: <20220428114113.3411536-3-dmitry.baryshkov@linaro.org>
Unlike the other patches in this series, this subject line mentions a
problem (actually, I don't even know whether it's a *problem* or just
a statement of fact), but doesn't say what this patch does.
Based on the patch, I guess this does something like:
Require resets except for MSM8996/APQ8096
I don't know whether you're changing the prefix convention for this
file, or just didn't look to see how it was done in the past, but it's
nice to have some consistency:
$ git log --oneline Documentation/devicetree/bindings/pci/qcom,pcie.txt
f52d2a0f0d32 dt-bindings: pci: qcom: Document PCIe bindings for SM8150 SoC
dddb4efa5192 dt-bindings: pci: qcom: Document PCIe bindings for SM8450
45a3ec891370 PCI: qcom: Add sc8180x compatible
320e10986ef7 dt-bindings: PCI: update references to Designware schema
9f7368ff1210 dt-bindings: pci: qcom: Document PCIe bindings for IPQ6018 SoC
c9f04600026f dt-bindings: PCI: qcom: Document ddrss_sf_tbu clock for sm8250
458168247ccc dt-bindings: pci: qcom: Document PCIe bindings for SM8250 SoC
d511580ea9c2 dt-bindings: PCI: qcom: Add ipq8064 rev 2 variant
b11b8cc161de dt-bindings: PCI: qcom: Add ext reset
736ae5c91712 dt-bindings: PCI: qcom: Add missing clks
5d28bee7c91e dt-bindings: PCI: qcom: Add support for SDM845 PCIe
29a50257a9d6 dt-bindings: PCI: qcom: Add QCS404 to the binding
f625b1ade245 PCI: qcom: Add missing supplies required for msm8996
8baf0151cd4b dt-bindings: PCI: qcom: Add support for IPQ8074
90d52d57ccac PCI: qcom: Add support for IPQ4019 PCIe controller
d0491fc39bdd PCI: qcom: Add support for MSM8996 PCIe controller
845d5ca26647 PCI: qcom: Document PCIe devicetree bindings
Including both "pci" and "pcie" in the prefix seems like overkill.
On Thu, Apr 28, 2022 at 02:41:07PM +0300, Dmitry Baryshkov wrote:
> On MSM8996/APQ8096 platforms the PCIe controller doesn't have any
> resets. So move the requirement stance under the corresponding if
> condition.
s/stance/stanza/
> Reviewed-by: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
> Signed-off-by: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>
> ---
> .../devicetree/bindings/pci/qcom,pcie.yaml | 14 ++++++++++++--
> 1 file changed, 12 insertions(+), 2 deletions(-)
>
> diff --git a/Documentation/devicetree/bindings/pci/qcom,pcie.yaml b/Documentation/devicetree/bindings/pci/qcom,pcie.yaml
> index 16f765e96128..ce4f53cdaba0 100644
> --- a/Documentation/devicetree/bindings/pci/qcom,pcie.yaml
> +++ b/Documentation/devicetree/bindings/pci/qcom,pcie.yaml
> @@ -114,8 +114,6 @@ required:
> - interrupt-map
> - clocks
> - clock-names
> - - resets
> - - reset-names
>
> allOf:
> - $ref: /schemas/pci/pci-bus.yaml#
> @@ -504,6 +502,18 @@ allOf:
> required:
> - power-domains
>
> + - if:
> + not:
> + properties:
> + compatibles:
> + contains:
> + enum:
> + - qcom,pcie-msm8996
> + then:
> + required:
> + - resets
> + - reset-names
> +
> unevaluatedProperties: false
>
> examples:
> --
> 2.35.1
>
next prev parent reply other threads:[~2022-04-28 14:35 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-28 11:41 [PATCH v4 0/8] dt-bindings: YAMLify pci/qcom,pcie schema Dmitry Baryshkov
2022-04-28 11:41 ` [PATCH v4 1/8] dt-bindings: pci/qcom,pcie: convert to YAML Dmitry Baryshkov
2022-04-28 11:41 ` [PATCH v4 2/8] dt-bindings: pci/qcom,pcie: resets are not defined for msm8996 Dmitry Baryshkov
2022-04-28 14:35 ` Bjorn Helgaas [this message]
2022-04-29 20:02 ` Dmitry Baryshkov
2022-04-28 11:41 ` [PATCH v4 3/8] dt-bindings: pci/qcom-pcie: specify reg-names explicitly Dmitry Baryshkov
2022-04-28 11:41 ` [PATCH v4 4/8] dt-bindings: pci/qcom,pcie: add schema for sc7280 chipset Dmitry Baryshkov
2022-04-28 11:41 ` [PATCH v4 5/8] arm64: dts: qcom: stop using snps,dw-pcie falback Dmitry Baryshkov
2022-04-28 11:41 ` [PATCH v4 6/8] arm: " Dmitry Baryshkov
2022-04-28 11:41 ` [PATCH v4 7/8] arm: dts: qcom-*: replace deprecated perst-gpio with perst-gpios Dmitry Baryshkov
2022-04-28 11:41 ` [PATCH v4 8/8] arm64: dts: qcom: " Dmitry Baryshkov
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=20220428143508.GA12269@bhelgaas \
--to=helgaas@kernel.org \
--cc=agross@kernel.org \
--cc=bhelgaas@google.com \
--cc=bjorn.andersson@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=dmitry.baryshkov@linaro.org \
--cc=gustavo.pimentel@synopsys.com \
--cc=jingoohan1@gmail.com \
--cc=krzk@kernel.org \
--cc=krzysztof.kozlowski@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=lorenzo.pieralisi@arm.com \
--cc=manivannan.sadhasivam@linaro.org \
--cc=robh+dt@kernel.org \
--cc=svarbanov@mm-sol.com \
--cc=vkoul@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