From: Rob Herring <robh@kernel.org>
To: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>
Cc: Andy Gross <agross@kernel.org>,
Bjorn Andersson <bjorn.andersson@linaro.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
Subject: Re: [PATCH v6 0/8] dt-bindings: YAMLify pci/qcom,pcie schema
Date: Tue, 10 May 2022 11:50:12 -0500 [thread overview]
Message-ID: <YnqXxNxFhf/odyka@robh.at.kernel.org> (raw)
In-Reply-To: <20220506152107.1527552-1-dmitry.baryshkov@linaro.org>
On Fri, May 06, 2022 at 06:20:59PM +0300, Dmitry Baryshkov wrote:
> Convert pci/qcom,pcie schema to YAML description. The first patch
> introduces several warnings which are fixed by the other patches in the
> series.
>
> Note regarding the snps,dw-pcie compatibility. The Qualcomm PCIe
> controller uses Synopsys PCIe IP core. However it is not just fused to
> the address space. Accessing PCIe registers requires several clocks and
> regulators to be powered up. Thus it can be assumed that the qcom,pcie
> bindings are not fully compatible with the snps,dw-pcie schema.
>
> Changes since v5:
> - s/stance/stanza (pointed out by Bjorn Helgaas)
>
> Changes since v4:
> - Change subjects to follow convention (suggested by Bjorn Helgaas)
>
> Changes since v3:
> - Rebase on linux-next to include sm8150 patches
>
> Changes since v2 (still kudos to Krzyshtof):
> - Readded reg-names conversion patch
> - Mention wake-gpio update in the commit message
> - Remove extra quotes in the schema
>
> Changes since v1 (all kudos to Krzyshtof):
> - Dropped the reg-names patch. It will be handled separately
> - Squashed the snps,dw-pcie removal (from schema) into the first patch
> - Replaced deprecated perst-gpio and wake-gpio with perst-gpios and
> wake-gpios in the examples and in DT files
> - Moved common clocks/clock-names, resets/reset-names and power-domains
> properties to the top level of the schema, leaving only platform
> specifics in the conditional branches
> - Dropped iommu-map/iommu-map-mask for now
> - Added (missed) interrupt-cells, clocks, clock-names, resets,
> reset-names properties to the required list (resets/reset-names are
> removed in the next patch, as they are not used on msm8996)
> - Fixed IRQ flags in the examples
> - Merged apq8064/ipq8064 into the single condition statement
> - Added extra empty lines
>
> Dmitry Baryshkov (8):
> dt-bindings: PCI: qcom: Convert to YAML
> dt-bindings: PCI: qcom: Do not require resets on msm8996 platforms
> dt-bindings: PCI: qcom: Specify reg-names explicitly
> dt-bindings: PCI: qcom: Add schema for sc7280 chipset
> arm64: dts: qcom: stop using snps,dw-pcie falback
> arm: dts: qcom: stop using snps,dw-pcie falback
> arm: dts: qcom-*: replace deprecated perst-gpio with perst-gpios
> arm64: dts: qcom: replace deprecated perst-gpio with perst-gpios
>
> .../devicetree/bindings/pci/qcom,pcie.txt | 398 ----------
> .../devicetree/bindings/pci/qcom,pcie.yaml | 714 ++++++++++++++++++
What tree do these apply to because they don't apply to rc1. I'm
assuming the PCI tree and Lorenzo should take them.
Rob
next prev parent reply other threads:[~2022-05-10 16:50 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-06 15:20 [PATCH v6 0/8] dt-bindings: YAMLify pci/qcom,pcie schema Dmitry Baryshkov
2022-05-06 15:21 ` [PATCH v6 1/8] dt-bindings: PCI: qcom: Convert to YAML Dmitry Baryshkov
2022-05-10 16:26 ` Rob Herring
2022-05-06 15:21 ` [PATCH v6 2/8] dt-bindings: PCI: qcom: Do not require resets on msm8996 platforms Dmitry Baryshkov
2022-05-10 16:46 ` Rob Herring
2022-05-06 15:21 ` [PATCH v6 3/8] dt-bindings: PCI: qcom: Specify reg-names explicitly Dmitry Baryshkov
2022-05-10 16:48 ` Rob Herring
2022-05-06 15:21 ` [PATCH v6 4/8] dt-bindings: PCI: qcom: Add schema for sc7280 chipset Dmitry Baryshkov
2022-05-10 16:50 ` Rob Herring
2022-05-06 15:21 ` [PATCH v6 5/8] arm64: dts: qcom: stop using snps,dw-pcie falback Dmitry Baryshkov
2022-05-06 15:21 ` [PATCH v6 6/8] arm: " Dmitry Baryshkov
2022-05-06 15:21 ` [PATCH v6 7/8] arm: dts: qcom-*: replace deprecated perst-gpio with perst-gpios Dmitry Baryshkov
2022-05-06 15:21 ` [PATCH v6 8/8] arm64: dts: qcom: " Dmitry Baryshkov
2022-05-10 16:50 ` Rob Herring [this message]
2022-05-11 10:13 ` [PATCH v6 0/8] dt-bindings: YAMLify pci/qcom,pcie schema Dmitry Baryshkov
2022-05-11 13:09 ` Lorenzo Pieralisi
2022-05-11 13:53 ` Dmitry Baryshkov
2022-05-11 14:00 ` Lorenzo Pieralisi
2022-05-11 14:09 ` Dmitry Baryshkov
2022-05-11 14:18 ` (subset) " Lorenzo Pieralisi
2022-08-29 23:45 ` Bjorn Andersson
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=YnqXxNxFhf/odyka@robh.at.kernel.org \
--to=robh@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=linux-arm-msm@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=lorenzo.pieralisi@arm.com \
--cc=manivannan.sadhasivam@linaro.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;
as well as URLs for NNTP newsgroup(s).