Linux clock framework development
 help / color / mirror / Atom feed
From: Shawn Guo <shengchao.guo@oss.qualcomm.com>
To: sashiko-reviews@lists.linux.dev
Cc: linux-clk@vger.kernel.org, conor+dt@kernel.org, robh@kernel.org,
	devicetree@vger.kernel.org
Subject: Re: [PATCH 1/3] dt-bindings: clock: qcom,sm8450-videocc: Fix clock inputs for Glymur
Date: Fri, 25 Sep 2026 08:03:39 +0800	[thread overview]
Message-ID: <arW6W_2Azq0GLF9P@QCOM-aGQu4IUr3Y> (raw)
In-Reply-To: <20260924162500.C92FC1F000FF@smtp.kernel.org>

On Thu, Sep 24, 2026 at 04:25:00PM +0000, sashiko-bot@kernel.org wrote:
> Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
> - [Medium] dt-bindings: hallucinated qcom,nord-videocc omitted from top-level enum
> --
> 
> commit 0ca2f034154349c48cdd7a693b1d8282d6886964
> Author: Shawn Guo <shengchao.guo@oss.qualcomm.com>
> 
> dt-bindings: clock: qcom,sm8450-videocc: Fix clock inputs for Glymur
> 
> The commit updates the clock inputs for the Glymur, Nord, and SM8750
> variants in the bindings from exactly two items to up to three items. This
> change allows device trees to supply the sleep clock input required by
> these drivers, resolving an issue where it would register as an orphan
> clock.
> 
> > diff --git a/Documentation/devicetree/bindings/clock/qcom,sm8450-videocc.yaml b/Documentation/devicetree/bindings/clock/qcom,sm8450-videocc.yaml
> > index 910c6d5672b86..dc01c37dcd0e3 100644
> > --- a/Documentation/devicetree/bindings/clock/qcom,sm8450-videocc.yaml
> > +++ b/Documentation/devicetree/bindings/clock/qcom,sm8450-videocc.yaml
> 
> [ ... ]
> 
> > @@ -77,6 +76,27 @@ allOf:
> >      then:
> >        required:
> >          - required-opps
> > +  - if:
> > +      properties:
> > +        compatible:
> > +          contains:
> > +            enum:
> > +              - qcom,glymur-videocc
> > +              - qcom,nord-videocc
> 
> [Severity: Medium]
> Is qcom,nord-videocc missing from the top-level properties/compatible enum
> list? When a compatible string is introduced in the allOf/if conditional
> logic but omitted from the top-level enum list (under unevaluatedProperties:
> false), any device tree node using it will unconditionally fail validation.
> 
> Additionally, the commit message mentions that videocc-glymur.c handles
> qcom,nord-videocc, but this identifier does not appear to exist anywhere in
> the kernel tree. Could this compatible string be an LLM hallucination?

The series is based on linux-next, wehre qcom,nord-videocc has landed.

Shawn

> 
> > +              - qcom,sm8750-videocc
> > +    then:
> > +      properties:
> > +        clocks:
> > +          items:
> > +            - description: Board XO source
> > +            - description: Board always-on XO source
> > +            - description: Sleep clock source
> > +    else:
> > +      properties:
> > +        clocks:
> > +          items:
> > +            - description: Board XO source
> > +            - description: Video AHB clock from GCC
> >  
> >  unevaluatedProperties: false
> >
> 
> -- 
> Sashiko AI review · https://sashiko.dev/#/patchset/20260924161152.1162301-1-shengchao.guo@oss.qualcomm.com?part=1

  reply	other threads:[~2026-09-25  0:03 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-24 16:11 [PATCH 0/3] qcom: videocc: Fix sleep clock on Glymur/SM8750 Shawn Guo
2026-09-24 16:11 ` [PATCH 1/3] dt-bindings: clock: qcom,sm8450-videocc: Fix clock inputs for Glymur Shawn Guo
2026-09-24 16:25   ` sashiko-bot
2026-09-25  0:03     ` Shawn Guo [this message]
2026-09-29  7:57   ` Krzysztof Kozlowski
2026-09-29 14:08     ` Shawn Guo
2026-09-24 16:11 ` [PATCH 2/3] arm64: dts: qcom: glymur: Add videocc sleep clock Shawn Guo
2026-09-25  9:48   ` Abel Vesa
2026-09-25 15:35     ` Shawn Guo
2026-09-25 15:49   ` Jagadeesh Kona
2026-09-26  0:18     ` Shawn Guo
2026-09-24 16:11 ` [PATCH 3/3] arm64: dts: qcom: sm8750: Fix videocc clock inputs Shawn Guo
2026-09-25  9:47   ` Abel Vesa
2026-09-25 15:29     ` Shawn Guo
2026-09-29  8:06       ` Krzysztof Kozlowski

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=arW6W_2Azq0GLF9P@QCOM-aGQu4IUr3Y \
    --to=shengchao.guo@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