public inbox for devicetree@vger.kernel.org
 help / color / mirror / Atom feed
From: Krzysztof Kozlowski <krzk@kernel.org>
To: Luca Weiss <luca.weiss@fairphone.com>
Cc: 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>,
	Konrad Dybcio <konradybcio@kernel.org>,
	~postmarketos/upstreaming@lists.sr.ht,
	phone-devel@vger.kernel.org, linux-arm-msm@vger.kernel.org,
	linux-clk@vger.kernel.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/3] dt-bindings: clock: qcom: document the Milos GX clock controller
Date: Thu, 2 Apr 2026 15:19:56 +0200	[thread overview]
Message-ID: <991f781f-e188-480f-933b-b9a342166446@kernel.org> (raw)
In-Reply-To: <DHIO0VFBOHNX.381P06A2CRHAZ@fairphone.com>

On 02/04/2026 14:24, Luca Weiss wrote:
>>>> +  '#power-domain-cells':
>>>> +    const: 1
>>>> +
>>>> +  reg:
>>>> +    maxItems: 1
>>>
>>> reg should be the second property, like you have it in "required" part.
>>> I guess you copied it from kaanapali-gxclkctl.yaml, so lesson - qcom
>>> bindings have acceptable quality, but not good enough to take as correct
>>> starting point.
>>>
>>
>> OTOH, why this entire binding cannot be squashed in Kaanapali one?
>> What's the difference?
> 
> There's no GMXC power domain on Milos. Apart from that they're
> compatible from a bindings perspective.

Ah, right, I missed only two items here.

> 
> However it can re-use include/dt-bindings/clock/qcom,kaanapali-gxclkctl.h
> because the GX_CLKCTL_GX_GDSC definition would be identical.

Indeed and you use the same driver, so the header can be re-used. This
should be explained in the commit msg.

> 
> And also the driver (which can be used as-is) would be identical. In
> that driver qcom,kaanapali-gxclkctl.h is used so it makes sense to keep
> with the kaanapali header, or not? Making a qcom,milos-gxclkctl.h with
> the same definition is not wanted?
> 
Best regards,
Krzysztof

  reply	other threads:[~2026-04-02 13:20 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-06 13:48 [PATCH 0/3] Add support for GXCLK for Milos Luca Weiss
2026-03-06 13:48 ` [PATCH 1/3] dt-bindings: clock: qcom: document the Milos GX clock controller Luca Weiss
2026-03-07 15:30   ` Krzysztof Kozlowski
2026-04-02  8:23     ` Krzysztof Kozlowski
2026-04-02 12:24       ` Luca Weiss
2026-04-02 13:19         ` Krzysztof Kozlowski [this message]
2026-03-06 13:48 ` [PATCH 2/3] clk: qcom: Add support for GXCLK for Milos Luca Weiss
2026-03-16 11:03   ` Jagadeesh Kona
2026-03-31  2:37   ` Alexander Koskovich
2026-03-31 10:57     ` Jagadeesh Kona
2026-03-31  9:23   ` Taniya Das
2026-03-06 13:48 ` [PATCH 3/3] arm64: dts: qcom: milos: Add GX clock controller Luca Weiss
2026-03-16 11:04   ` Jagadeesh Kona
2026-03-16 11:36   ` Konrad Dybcio

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=991f781f-e188-480f-933b-b9a342166446@kernel.org \
    --to=krzk@kernel.org \
    --cc=andersson@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=konradybcio@kernel.org \
    --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=luca.weiss@fairphone.com \
    --cc=mturquette@baylibre.com \
    --cc=phone-devel@vger.kernel.org \
    --cc=robh@kernel.org \
    --cc=sboyd@kernel.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