From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: Bjorn Andersson <andersson@kernel.org>,
Konrad Dybcio <konrad.dybcio@linaro.org>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Conor Dooley <conor+dt@kernel.org>
Cc: linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org,
Dmitry Baryshkov <dmitry.baryshkov@linaro.org>,
Neil Armstrong <neil.armstrong@linaro.org>,
Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
Subject: [PATCH v2 0/7] arm64: dts: qcom: describe all PCIe MSI interrupts
Date: Fri, 26 Jan 2024 10:38:29 +0100 [thread overview]
Message-ID: <20240126-b4-dt-bindings-pci-qcom-split-dts-v2-0-0bb067f73adb@linaro.org> (raw)
Changes in v2:
1. Add tags.
2. Split interrupt-names: one entry per line.
3. New patch #7.
Bindings now expect 8 interrupts in PCIe nodes:
https://lore.kernel.org/r/20240126-dt-bindings-pci-qcom-split-v3-0-f23cda4d74c0@linaro.org
Best regards,
Krzysztof
---
Krzysztof Kozlowski (7):
arm64: dts: qcom: sm8150: describe all PCI MSI interrupts
arm64: dts: qcom: sm8250: describe all PCI MSI interrupts
arm64: dts: qcom: sm8350: describe all PCI MSI interrupts
arm64: dts: qcom: sm8450: describe all PCI MSI interrupts
arm64: dts: qcom: sm8550: describe all PCI MSI interrupts
arm64: dts: qcom: sm8650: describe all PCI MSI interrupts
arm64: dts: qcom: split PCIe interrupt-names entries per lines
arch/arm64/boot/dts/qcom/sm8150.dtsi | 36 ++++++++++++++++++++++++----
arch/arm64/boot/dts/qcom/sm8250.dtsi | 46 +++++++++++++++++++++++++++++++-----
arch/arm64/boot/dts/qcom/sm8350.dtsi | 28 ++++++++++++++++++----
arch/arm64/boot/dts/qcom/sm8450.dtsi | 36 ++++++++++++++++++++++++----
arch/arm64/boot/dts/qcom/sm8550.dtsi | 38 ++++++++++++++++++++++++-----
arch/arm64/boot/dts/qcom/sm8650.dtsi | 36 ++++++++++++++++++++++++----
6 files changed, 192 insertions(+), 28 deletions(-)
---
base-commit: 2c055cf9571d45d1438a6a3aadccb300edac1bce
change-id: 20240126-b4-dt-bindings-pci-qcom-split-dts-affe9e443a4e
Best regards,
--
Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
next reply other threads:[~2024-01-26 9:38 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-26 9:38 Krzysztof Kozlowski [this message]
2024-01-26 9:38 ` [PATCH v2 1/7] arm64: dts: qcom: sm8150: describe all PCI MSI interrupts Krzysztof Kozlowski
2024-01-26 9:38 ` [PATCH v2 2/7] arm64: dts: qcom: sm8250: " Krzysztof Kozlowski
2024-01-26 9:38 ` [PATCH v2 3/7] arm64: dts: qcom: sm8350: " Krzysztof Kozlowski
2024-01-26 9:38 ` [PATCH v2 4/7] arm64: dts: qcom: sm8450: " Krzysztof Kozlowski
2024-01-26 9:38 ` [PATCH v2 5/7] arm64: dts: qcom: sm8550: " Krzysztof Kozlowski
2024-01-26 9:38 ` [PATCH v2 6/7] arm64: dts: qcom: sm8650: " Krzysztof Kozlowski
2024-01-26 9:38 ` [PATCH v2 7/7] arm64: dts: qcom: split PCIe interrupt-names entries per lines Krzysztof Kozlowski
2024-01-28 17:45 ` [PATCH v2 0/7] arm64: dts: qcom: describe all PCIe MSI interrupts 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=20240126-b4-dt-bindings-pci-qcom-split-dts-v2-0-0bb067f73adb@linaro.org \
--to=krzysztof.kozlowski@linaro.org \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dmitry.baryshkov@linaro.org \
--cc=konrad.dybcio@linaro.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=neil.armstrong@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).