From: Richard Acayan <mailingradian@gmail.com>
To: robh@kernel.org
Cc: andersson@kernel.org, agross@kernel.org,
konrad.dybcio@somainline.org, mturquette@baylibre.com,
sboyd@kernel.org, robh+dt@kernel.org,
krzysztof.kozlowski+dt@linaro.org, tdas@codeaurora.org,
linux-arm-msm@vger.kernel.org, linux-clk@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
~postmarketos/upstreaming@lists.sr.ht, caleb@connolly.tech,
jo@jsfamily.in, Richard Acayan <mailingradian@gmail.com>
Subject: Re: [PATCH 1/3] dt-bindings: clock: gcc-sdm845: add sdm670 global clocks
Date: Wed, 7 Sep 2022 18:18:33 -0400 [thread overview]
Message-ID: <20220907221832.136715-1-mailingradian@gmail.com> (raw)
In-Reply-To: <20220907175300.GA3779566-robh@kernel.org>
> You just changed the clocks from 5 to 3. Please test your changes:
Right. I'll make sure to set up CI locally before my next series.
> What you want here I think is 'minItems: 3' and then restrict the clocks
> to 3 or 5 in the if/then schema.
Yes, thanks for directing me. I found what I needed in
Documentation/devicetree/bindings/clock/qcom,rpmcc.yaml.
next prev parent reply other threads:[~2022-09-07 22:19 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-07 2:50 [PATCH 0/3] SDM670 Global Clocks Richard Acayan
2022-09-07 2:50 ` [PATCH 1/3] dt-bindings: clock: gcc-sdm845: add sdm670 global clocks Richard Acayan
2022-09-07 17:53 ` Rob Herring
2022-09-07 22:18 ` Richard Acayan [this message]
2022-09-07 2:50 ` [PATCH 2/3] clk: qcom: gcc-sdm845: use device tree match data Richard Acayan
2022-09-07 2:50 ` [PATCH 3/3] clk: qcom: gcc-sdm845: add sdm670 global clock data Richard Acayan
2022-09-07 14:18 ` kernel test robot
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=20220907221832.136715-1-mailingradian@gmail.com \
--to=mailingradian@gmail.com \
--cc=agross@kernel.org \
--cc=andersson@kernel.org \
--cc=caleb@connolly.tech \
--cc=devicetree@vger.kernel.org \
--cc=jo@jsfamily.in \
--cc=konrad.dybcio@somainline.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mturquette@baylibre.com \
--cc=robh+dt@kernel.org \
--cc=robh@kernel.org \
--cc=sboyd@kernel.org \
--cc=tdas@codeaurora.org \
--cc=~postmarketos/upstreaming@lists.sr.ht \
/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).