From: Krzysztof Kozlowski <krzk@kernel.org>
To: joakim.zhang@cixtech.com, mturquette@baylibre.com,
sboyd@kernel.org, bmasney@redhat.com, robh@kernel.org,
krzk+dt@kernel.org, conor+dt@kernel.org, p.zabel@pengutronix.de,
gary.yang@cixtech.com
Cc: cix-kernel-upstream@cixtech.com, linux-clk@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v2 1/5] dt-bindings: soc: cix,sky1-system-control: add audss system control
Date: Fri, 5 Jun 2026 11:21:00 +0200 [thread overview]
Message-ID: <b005d5cc-3b9b-47a6-b6fe-91ace2db4089@kernel.org> (raw)
In-Reply-To: <17528d9a-738c-48fe-ac24-b8d90875a74f@kernel.org>
On 05/06/2026 11:18, Krzysztof Kozlowski wrote:
> On 05/06/2026 05:22, joakim.zhang@cixtech.com wrote:
>> compatible:
>> - items:
>> - - enum:
>> - - cix,sky1-system-control
>> - - cix,sky1-s5-system-control
>> - - const: syscon
>> + oneOf:
>> + - items:
>> + - enum:
>> + - cix,sky1-system-control
>> + - cix,sky1-s5-system-control
>> + - const: syscon
>> + - items:
>> + - const: cix,sky1-audss-system-control
>> + - const: simple-mfd
>> + - const: syscon
>>
>> reg:
>> maxItems: 1
>> @@ -27,6 +32,11 @@ properties:
>> '#reset-cells':
>> const: 1
>>
>> + clock-controller:
>> + $ref: /schemas/clock/cix,sky1-audss-clock.yaml#
>> + description:
>> + AUDSS internal clock provider (cix,sky1-audss-system-control only).
>
> Are you sure this patch builds? Your cover letter should explain merging
I am sure it does not...
I recommend switching to compatible-style of defining subnodes in parent
schema which would decouple patches.
example:
https://elixir.bootlin.com/linux/v7.1-rc6/source/Documentation/devicetree/bindings/display/msm/qcom,sm8750-mdss.yaml#L41
> dependencies/strategy/constraints in the first chapter. You start with
> THE MOST important information.
>
> You need to disallow node for other variants.
>
>
Best regards,
Krzysztof
next prev parent reply other threads:[~2026-06-05 9:21 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-05 3:22 [PATCH v2 0/5] Add Cix Sky1 AUDSS clock and reset support joakim.zhang
2026-06-05 3:22 ` [PATCH v2 1/5] dt-bindings: soc: cix,sky1-system-control: add audss system control joakim.zhang
2026-06-05 4:40 ` Rob Herring (Arm)
2026-06-05 9:18 ` Krzysztof Kozlowski
2026-06-05 9:21 ` Krzysztof Kozlowski [this message]
2026-06-09 6:25 ` Joakim Zhang
2026-06-09 6:25 ` Joakim Zhang
2026-06-09 6:44 ` Krzysztof Kozlowski
2026-06-05 3:22 ` [PATCH v2 2/5] reset: cix: add audss support to sky1 reset driver joakim.zhang
2026-06-05 3:22 ` [PATCH v2 3/5] dt-bindings: clock: cix,sky1-audss-clock: add audss clock controller joakim.zhang
2026-06-05 9:24 ` Krzysztof Kozlowski
2026-06-09 6:27 ` Joakim Zhang
2026-06-05 3:22 ` [PATCH v2 4/5] clk: cix: add sky1 " joakim.zhang
2026-06-05 7:42 ` Philipp Zabel
2026-06-05 3:22 ` [PATCH v2 5/5] arm64: dts: cix: sky1: add audss system control joakim.zhang
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=b005d5cc-3b9b-47a6-b6fe-91ace2db4089@kernel.org \
--to=krzk@kernel.org \
--cc=bmasney@redhat.com \
--cc=cix-kernel-upstream@cixtech.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=gary.yang@cixtech.com \
--cc=joakim.zhang@cixtech.com \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mturquette@baylibre.com \
--cc=p.zabel@pengutronix.de \
--cc=robh@kernel.org \
--cc=sboyd@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