From: Bryan O'Donoghue <bryan.odonoghue@linaro.org>
To: agross@kernel.org, bjorn.andersson@linaro.org,
jassisinghbrar@gmail.com, robh+dt@kernel.org,
krzysztof.kozlowski+dt@linaro.org
Cc: linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
bryan.odonoghue@linaro.org
Subject: [PATCH 2/2] dt-bindings: mailbox: qcom: Add clock-output-names
Date: Thu, 30 Jun 2022 05:35:36 +0100 [thread overview]
Message-ID: <20220630043536.3308546-3-bryan.odonoghue@linaro.org> (raw)
In-Reply-To: <20220630043536.3308546-1-bryan.odonoghue@linaro.org>
Add clock-output-names as optional so that SoCs such as the msm8939 which
have multiple a53 PLLs can latch the appropriate output name in
drivers/clk/qcom/apcs-msm8916.c.
Signed-off-by: Bryan O'Donoghue <bryan.odonoghue@linaro.org>
---
.../devicetree/bindings/mailbox/qcom,apcs-kpss-global.yaml | 5 +++++
1 file changed, 5 insertions(+)
diff --git a/Documentation/devicetree/bindings/mailbox/qcom,apcs-kpss-global.yaml b/Documentation/devicetree/bindings/mailbox/qcom,apcs-kpss-global.yaml
index f342494fd6108..7f3816cbc0353 100644
--- a/Documentation/devicetree/bindings/mailbox/qcom,apcs-kpss-global.yaml
+++ b/Documentation/devicetree/bindings/mailbox/qcom,apcs-kpss-global.yaml
@@ -63,6 +63,11 @@ properties:
- const: aux
- const: ref
+ clock-output-names:
+ Usage: optional
+ Value type: <string>
+ Definition: Name of the output clock.
+
required:
- compatible
- reg
--
2.36.1
next prev parent reply other threads:[~2022-06-30 4:35 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-30 4:35 [PATCH 0/2] Two apcs-kpss-global.yaml fixes Bryan O'Donoghue
2022-06-30 4:35 ` [PATCH 1/2] dt-bindings: mailbox: qcom: Add syscon const for relevant entries Bryan O'Donoghue
2022-06-30 13:44 ` Rob Herring
2022-06-30 13:51 ` Bryan O'Donoghue
2022-06-30 18:37 ` Krzysztof Kozlowski
2022-06-30 4:35 ` Bryan O'Donoghue [this message]
2022-06-30 13:44 ` [PATCH 2/2] dt-bindings: mailbox: qcom: Add clock-output-names Rob Herring
2022-06-30 18:38 ` Krzysztof Kozlowski
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=20220630043536.3308546-3-bryan.odonoghue@linaro.org \
--to=bryan.odonoghue@linaro.org \
--cc=agross@kernel.org \
--cc=bjorn.andersson@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=jassisinghbrar@gmail.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-msm@vger.kernel.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).