devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Krzysztof Kozlowski <krzk@kernel.org>
To: Satya Priya Kakitapalli <quic_skakitap@quicinc.com>,
	Bjorn Andersson <andersson@kernel.org>,
	Michael Turquette <mturquette@baylibre.com>,
	Stephen Boyd <sboyd@kernel.org>, Rob Herring <robh@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>,
	Jeff Hugo <jeff.hugo@oss.qualcomm.com>,
	Srinivas Kandagatla <srini@kernel.org>
Cc: Ajit Pandey <quic_ajipan@quicinc.com>,
	Imran Shaik <quic_imrashai@quicinc.com>,
	Taniya Das <quic_tdas@quicinc.com>,
	Jagadeesh Kona <quic_jkona@quicinc.com>,
	linux-arm-msm@vger.kernel.org, linux-clk@vger.kernel.org,
	devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 4/8] dt-bindings: clock: qcom,qcs404-turingcc: Reference qcom,gcc.yaml
Date: Wed, 9 Jul 2025 12:07:09 +0200	[thread overview]
Message-ID: <74785dcd-6436-40a6-b747-a4890edc2113@kernel.org> (raw)
In-Reply-To: <20250709-gcc-ref-fixes-v1-4-ceddde06775b@quicinc.com>

On 09/07/2025 11:37, Satya Priya Kakitapalli wrote:
> Reference the common qcom,gcc.yaml schema to unify the common
> parts of the binding.
> 
> Signed-off-by: Satya Priya Kakitapalli <quic_skakitap@quicinc.com>
> ---
>  .../devicetree/bindings/clock/qcom,qcs404-turingcc.yaml | 17 ++++-------------
>  1 file changed, 4 insertions(+), 13 deletions(-)
> 
> diff --git a/Documentation/devicetree/bindings/clock/qcom,qcs404-turingcc.yaml b/Documentation/devicetree/bindings/clock/qcom,qcs404-turingcc.yaml
> index 033e010754a26bd03e02a364b0a6f36d87a3af62..794984f563fe3eb253aaf7524205097cf0c62711 100644
> --- a/Documentation/devicetree/bindings/clock/qcom,qcs404-turingcc.yaml
> +++ b/Documentation/devicetree/bindings/clock/qcom,qcs404-turingcc.yaml
> @@ -13,26 +13,17 @@ properties:
>    compatible:
>      const: qcom,qcs404-turingcc
>  
> -  reg:
> -    maxItems: 1
> -
>    clocks:
>      maxItems: 1
>  
> -  '#clock-cells':
> -    const: 1
> -
> -  '#reset-cells':
> -    const: 1
> -
>  required:
>    - compatible
> -  - reg
>    - clocks
> -  - '#clock-cells'
> -  - '#reset-cells'
No, this becomes now power domain provider without explanation.

Don't just blindly copy other people's commits without understanding them.

Best regards,
Krzysztof

  reply	other threads:[~2025-07-09 10:07 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-09  9:37 [PATCH 0/8] Reference the common qcom,gcc.yaml schema Satya Priya Kakitapalli
2025-07-09  9:37 ` [PATCH 1/8] dt-bindings: clock: qcom,sm8150-camcc: Reference qcom,gcc.yaml Satya Priya Kakitapalli
2025-07-09  9:46   ` Krzysztof Kozlowski
2025-07-09  9:37 ` [PATCH 2/8] dt-bindings: clock: qcom,lcc: " Satya Priya Kakitapalli
2025-07-09 10:08   ` Krzysztof Kozlowski
2025-07-09  9:37 ` [PATCH 3/8] dt-bindings: clock: qcom,mmcc: " Satya Priya Kakitapalli
2025-07-09  9:37 ` [PATCH 4/8] dt-bindings: clock: qcom,qcs404-turingcc: " Satya Priya Kakitapalli
2025-07-09 10:07   ` Krzysztof Kozlowski [this message]
2025-07-10 10:20     ` Satya Priya Kakitapalli
2025-07-09  9:37 ` [PATCH 5/8] dt-bindings: clock: qcom,qdu1000-ecpricc: " Satya Priya Kakitapalli
2025-07-09 10:09   ` Krzysztof Kozlowski
2025-07-09  9:37 ` [PATCH 6/8] dt-bindings: clock: qcom,sc8280xp-lpasscc: " Satya Priya Kakitapalli
2025-07-09 10:10   ` Krzysztof Kozlowski
2025-07-09  9:37 ` [PATCH 7/8] dt-bindings: clock: qcom,sm4450-camcc: " Satya Priya Kakitapalli
2025-07-09  9:37 ` [PATCH 8/8] dt-bindings: clock: qcom,sm4450-dispcc: " Satya Priya Kakitapalli

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=74785dcd-6436-40a6-b747-a4890edc2113@kernel.org \
    --to=krzk@kernel.org \
    --cc=andersson@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=jeff.hugo@oss.qualcomm.com \
    --cc=krzk+dt@kernel.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=quic_ajipan@quicinc.com \
    --cc=quic_imrashai@quicinc.com \
    --cc=quic_jkona@quicinc.com \
    --cc=quic_skakitap@quicinc.com \
    --cc=quic_tdas@quicinc.com \
    --cc=robh@kernel.org \
    --cc=sboyd@kernel.org \
    --cc=srini@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).