From: Srinivas Kandagatla <srinivas.kandagatla@oss.qualcomm.com>
To: sashiko-reviews@lists.linux.dev
Cc: conor+dt@kernel.org, devicetree@vger.kernel.org, robh@kernel.org,
linux-clk@vger.kernel.org
Subject: Re: [PATCH 1/4] dt-bindings: clock: Add LPASS AUDIOCC and reset controller for Glymur
Date: Tue, 22 Sep 2026 20:05:15 +0100 [thread overview]
Message-ID: <bc795351-dcbf-492a-814f-2cb1d009f6bc@oss.qualcomm.com> (raw)
In-Reply-To: <20260922185449.51A221F000FF@smtp.kernel.org>
On 9/22/26 7:54 PM, sashiko-bot@kernel.org wrote:
> Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
> - [Low] dt-bindings: incorrect `#clock-cells` requirement for reset-only provider
This binding is for clock controller which also has reset controls
Its pretty much inline with what is done with other lpass audiocc bindings.
--srini
> --
>
> commit 347d3aed7b27ab7cf248e5a7c46279253cf08e0e
> Author: Srinivas Kandagatla <srinivas.kandagatla@oss.qualcomm.com>
>
> dt-bindings: clock: Add LPASS AUDIOCC and reset controller for Glymur
>
> This commit introduces device tree bindings for the LPASS audio clock and
> reset controller on Glymur. It defines the compatible string and required
> properties for the device node.
>
>> diff --git a/Documentation/devicetree/bindings/clock/qcom,glymur-lpasscc.yaml b/Documentation/devicetree/bindings/clock/qcom,glymur-lpasscc.yaml
>> new file mode 100644
>> index 0000000000000..c047c0174a93d
>> --- /dev/null
>> +++ b/Documentation/devicetree/bindings/clock/qcom,glymur-lpasscc.yaml
> [ ... ]
>> +properties:
>> + compatible:
>> + enum:
>> + - qcom,glymur-lpassaudiocc
>> +
>> + reg:
>> + maxItems: 1
>> +
>> + '#clock-cells':
>> + const: 1
>> +
>> + '#reset-cells':
>> + const: 1
>> +
>> +required:
>> + - compatible
>> + - reg
>> + - '#clock-cells'
>
> [Severity: Low]
> Since the commit message specifies that the audio clock controller only
> provides reset support when it is under the control of Q6DSP, and zero
> clocks are exported to Linux, should '#clock-cells' be required here?
>
> Making '#clock-cells' a required property forces device tree authors to
> include an unused, dummy property that incorrectly models the hardware's
> capabilities just to pass DT schema validation. Similar reset-only clock
> controller bindings (e.g., qcom,sm6115-lpasscc.yaml) correctly omit the
> '#clock-cells' property entirely.
>
>> + - '#reset-cells'
>
next prev parent reply other threads:[~2026-09-22 19:05 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-22 18:44 [PATCH 0/4] clk: qcom: Add LPASS clock/reset controllers for Glymur Srinivas Kandagatla
2026-09-22 18:44 ` [PATCH 1/4] dt-bindings: clock: Add LPASS AUDIOCC and reset controller " Srinivas Kandagatla
2026-09-22 18:54 ` sashiko-bot
2026-09-22 19:05 ` Srinivas Kandagatla [this message]
2026-09-28 9:59 ` Krzysztof Kozlowski
2026-09-28 10:00 ` Srinivas Kandagatla
2026-09-22 18:44 ` [PATCH 2/4] dt-bindings: clock: Add LPASSCC " Srinivas Kandagatla
2026-09-28 9:59 ` Krzysztof Kozlowski
2026-09-22 18:44 ` [PATCH 3/4] clk: qcom: Add lpass audio clock controller driver " Srinivas Kandagatla
2026-09-22 18:53 ` sashiko-bot
2026-09-22 20:40 ` Abel Vesa
2026-09-24 9:02 ` Taniya Das
2026-09-29 15:37 ` Uwe Kleine-König
2026-09-22 18:44 ` [PATCH 4/4] clk: qcom: Add lpass " Srinivas Kandagatla
2026-09-22 20:41 ` Abel Vesa
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=bc795351-dcbf-492a-814f-2cb1d009f6bc@oss.qualcomm.com \
--to=srinivas.kandagatla@oss.qualcomm.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=linux-clk@vger.kernel.org \
--cc=robh@kernel.org \
--cc=sashiko-reviews@lists.linux.dev \
/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