From: George Moussalem via B4 Relay <devnull+george.moussalem.outlook.com@kernel.org>
To: "Uwe Kleine-König" <ukleinek@kernel.org>,
"Rob Herring" <robh@kernel.org>,
"Krzysztof Kozlowski" <krzk+dt@kernel.org>,
"Conor Dooley" <conor+dt@kernel.org>,
"Baruch Siach" <baruch@tkos.co.il>,
"Bjorn Andersson" <andersson@kernel.org>,
"Konrad Dybcio" <konradybcio@kernel.org>
Cc: linux-arm-msm@vger.kernel.org, linux-pwm@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
George Moussalem <george.moussalem@outlook.com>
Subject: [PATCH v17 5/9] dt-bindings: pwm: qcom,ipq6018-pwm: Add compatible for ipq9574
Date: Wed, 08 Oct 2025 19:32:57 +0400 [thread overview]
Message-ID: <20251008-ipq-pwm-v17-5-9bd43edfc7f7@outlook.com> (raw)
In-Reply-To: <20251008-ipq-pwm-v17-0-9bd43edfc7f7@outlook.com>
From: George Moussalem <george.moussalem@outlook.com>
The IPQ9574 SoC contains a PWM block which is exactly the same as the
one found in IPQ6018. So let's add a compatible for IPQ9574 and use
IPQ6018 as the fallback.
Acked-by: Rob Herring (Arm) <robh@kernel.org>
Signed-off-by: George Moussalem <george.moussalem@outlook.com>
---
Documentation/devicetree/bindings/pwm/qcom,ipq6018-pwm.yaml | 1 +
1 file changed, 1 insertion(+)
diff --git a/Documentation/devicetree/bindings/pwm/qcom,ipq6018-pwm.yaml b/Documentation/devicetree/bindings/pwm/qcom,ipq6018-pwm.yaml
index e00b9e01f4f89dd0d08610772c984a0e2725d154..48dd7d1b8f511b0dd2cbebc07f33cafc3655ce50 100644
--- a/Documentation/devicetree/bindings/pwm/qcom,ipq6018-pwm.yaml
+++ b/Documentation/devicetree/bindings/pwm/qcom,ipq6018-pwm.yaml
@@ -16,6 +16,7 @@ properties:
- enum:
- qcom,ipq5018-pwm
- qcom,ipq5332-pwm
+ - qcom,ipq9574-pwm
- const: qcom,ipq6018-pwm
- const: qcom,ipq6018-pwm
--
2.51.0
next prev parent reply other threads:[~2025-10-08 15:33 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-08 15:32 [PATCH v17 0/9] Add PWM support for IPQ chipsets George Moussalem via B4 Relay
2025-10-08 15:32 ` [PATCH v17 1/9] dt-bindings: pwm: add IPQ6018 binding George Moussalem via B4 Relay
2025-10-08 16:08 ` Baruch Siach
2025-10-10 5:54 ` George Moussalem
2025-10-27 16:39 ` Bjorn Andersson
2025-10-08 15:32 ` [PATCH v17 2/9] pwm: driver for qualcomm ipq6018 pwm block George Moussalem via B4 Relay
2025-10-27 16:40 ` Bjorn Andersson
2025-10-08 15:32 ` [PATCH v17 3/9] dt-bindings: pwm: qcom,ipq6018-pwm: Add compatible for ipq5018 George Moussalem via B4 Relay
2025-10-08 15:32 ` [PATCH v17 4/9] dt-bindings: pwm: qcom,ipq6018-pwm: Add compatible for ipq5332 George Moussalem via B4 Relay
2025-10-08 15:32 ` George Moussalem via B4 Relay [this message]
2025-10-08 15:32 ` [PATCH v17 6/9] arm64: dts: qcom: ipq6018: add pwm node George Moussalem via B4 Relay
2025-10-08 15:32 ` [PATCH v17 7/9] arm64: dts: qcom: ipq5018: " George Moussalem via B4 Relay
2025-10-08 15:33 ` [PATCH v17 8/9] arm64: dts: qcom: ipq5332: " George Moussalem via B4 Relay
2025-10-08 15:33 ` [PATCH v17 9/9] arm64: dts: qcom: ipq9574: " George Moussalem via B4 Relay
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=20251008-ipq-pwm-v17-5-9bd43edfc7f7@outlook.com \
--to=devnull+george.moussalem.outlook.com@kernel.org \
--cc=andersson@kernel.org \
--cc=baruch@tkos.co.il \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=george.moussalem@outlook.com \
--cc=konradybcio@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pwm@vger.kernel.org \
--cc=robh@kernel.org \
--cc=ukleinek@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).