From: Rob Herring <robh@kernel.org>
To: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
Cc: "Konrad Dybcio" <konrad.dybcio@linaro.org>,
"Conor Dooley" <conor+dt@kernel.org>,
"Manivannan Sadhasivam" <manivannan.sadhasivam@linaro.org>,
"Rob Herring" <robh+dt@kernel.org>,
linux-arm-msm@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-pci@vger.kernel.org,
"Krzysztof Kozlowski" <krzysztof.kozlowski+dt@linaro.org>,
"Manivannan Sadhasivam" <mani@kernel.org>,
devicetree@vger.kernel.org,
"Bjorn Andersson" <andersson@kernel.org>,
"Krzysztof Wilczyński" <kw@linux.com>,
"Lorenzo Pieralisi" <lpieralisi@kernel.org>,
"Bjorn Helgaas" <bhelgaas@google.com>
Subject: Re: [PATCH v3 2/6] dt-bindings: PCI: qcom,pcie-sm8450: move SM8450 to dedicated schema
Date: Tue, 30 Jan 2024 16:49:15 -0600 [thread overview]
Message-ID: <170665495522.2559069.14002850909301395083.robh@kernel.org> (raw)
In-Reply-To: <20240126-dt-bindings-pci-qcom-split-v3-2-f23cda4d74c0@linaro.org>
On Fri, 26 Jan 2024 09:56:43 +0100, Krzysztof Kozlowski wrote:
> Move SM8450 PCIe devices from qcom,pcie.yaml binding to a dedicated file
> to make reviewing easier.
>
> This creates equivalent schema file, except:
> - Missing required compatible which is actually redundant.
> - Expecting eight MSI interrupts, instead of only one, which was
> incomplete hardware description.
>
> Acked-by: Manivannan Sadhasivam <manivannan.sadhasivam@linaro.org>
> Signed-off-by: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
> ---
> .../devicetree/bindings/pci/qcom,pcie-sm8450.yaml | 178 +++++++++++++++++++++
> .../devicetree/bindings/pci/qcom,pcie.yaml | 67 --------
> 2 files changed, 178 insertions(+), 67 deletions(-)
>
Reviewed-by: Rob Herring <robh@kernel.org>
next prev parent reply other threads:[~2024-01-30 22:49 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-26 8:56 [PATCH v3 0/6] dt-bindings: PCI: qcom: move to dedicated schema (part one) Krzysztof Kozlowski
2024-01-26 8:56 ` [PATCH v3 1/6] dt-bindings: PCI: qcom,pcie-sm8550: move SM8550 to dedicated schema Krzysztof Kozlowski
2024-01-26 8:56 ` [PATCH v3 2/6] dt-bindings: PCI: qcom,pcie-sm8450: move SM8450 " Krzysztof Kozlowski
2024-01-30 22:49 ` Rob Herring [this message]
2024-01-26 8:56 ` [PATCH v3 3/6] dt-bindings: PCI: qcom,pcie-sm8250: move SM8250 " Krzysztof Kozlowski
2024-01-26 8:56 ` [PATCH v3 4/6] dt-bindings: PCI: qcom,pcie-sm8150: move SM8150 " Krzysztof Kozlowski
2024-01-26 8:56 ` [PATCH v3 5/6] dt-bindings: PCI: qcom,pcie-sm8350: move SM8350 " Krzysztof Kozlowski
2024-01-26 8:56 ` [PATCH v3 6/6] dt-bindings: PCI: qcom,pcie-sc8280xp: move SC8280XP " Krzysztof Kozlowski
2024-02-14 11:56 ` [PATCH v3 0/6] dt-bindings: PCI: qcom: move to dedicated schema (part one) Krzysztof Kozlowski
2024-03-09 16:34 ` Krzysztof Wilczyński
2024-03-09 16:27 ` Krzysztof Wilczyński
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=170665495522.2559069.14002850909301395083.robh@kernel.org \
--to=robh@kernel.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=krzysztof.kozlowski@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=mani@kernel.org \
--cc=manivannan.sadhasivam@linaro.org \
--cc=robh+dt@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).