1. Patchew
  2. linux
  3. View series

[PATCH 0/5] Add missing OPP tables for Venus on qcom/arm64

Konrad Dybcio posted 5 patches 8 months, 2 weeks ago 
arch/arm64/boot/dts/qcom/msm8916.dtsi | 20 ++++++++++++++++++
arch/arm64/boot/dts/qcom/msm8996.dtsi | 39 ++++++++++++++++++++++++++++-------
arch/arm64/boot/dts/qcom/msm8998.dtsi | 30 +++++++++++++++++++++++++++
arch/arm64/boot/dts/qcom/sdm630.dtsi  | 35 +++++++++++++++++++++++++++++++
arch/arm64/boot/dts/qcom/sdm845.dtsi  | 24 ++++++++++-----------
5 files changed, 128 insertions(+), 20 deletions(-)
[PATCH 0/5] Add missing OPP tables for Venus on qcom/arm64
Posted by Konrad Dybcio 8 months, 2 weeks ago 
Sparked by <20250530-add-venus-for-qcs615-v8-0-c0092ac616d0@quicinc.com>

No external dependencies

Signed-off-by: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>
---
Konrad Dybcio (5):
      arm64: dts: qcom: msm8916: Add Venus OPP table
      arm64: dts: qcom: msm8996: Add Venus OPP table
      arm64: dts: qcom: msm8998: Add Venus OPP table
      arm64: dts: qcom: sdm630: Add Venus OPP table
      arm64: dts: qcom: sdm845: Fix Venus OPP entries

 arch/arm64/boot/dts/qcom/msm8916.dtsi | 20 ++++++++++++++++++
 arch/arm64/boot/dts/qcom/msm8996.dtsi | 39 ++++++++++++++++++++++++++++-------
 arch/arm64/boot/dts/qcom/msm8998.dtsi | 30 +++++++++++++++++++++++++++
 arch/arm64/boot/dts/qcom/sdm630.dtsi  | 35 +++++++++++++++++++++++++++++++
 arch/arm64/boot/dts/qcom/sdm845.dtsi  | 24 ++++++++++-----------
 5 files changed, 128 insertions(+), 20 deletions(-)
---
base-commit: 2a628f951ed54c30a232230b5b58349d2a8dbb11
change-id: 20250531-topic-venus_opp_arm64-378e98bf6071

Best regards,
-- 
Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>
Re: [PATCH 0/5] Add missing OPP tables for Venus on qcom/arm64
Posted by Stephan Gerhold 8 months, 1 week ago 
On Sat, May 31, 2025 at 02:27:18PM +0200, Konrad Dybcio wrote:
> Sparked by <20250530-add-venus-for-qcs615-v8-0-c0092ac616d0@quicinc.com>
> 
> No external dependencies
> 

Are you sure?

> Signed-off-by: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>
> ---
> Konrad Dybcio (5):
>       arm64: dts: qcom: msm8916: Add Venus OPP table
>       arm64: dts: qcom: msm8996: Add Venus OPP table
>       arm64: dts: qcom: msm8998: Add Venus OPP table
>       arm64: dts: qcom: sdm630: Add Venus OPP table

None of these platforms has a power domain that supports performance
states specified in the venus node of the DT, and the venus GDSC does
not have any parent either. I think you will need to update the venus
bindings and add

	.opp_pmdomain = (const char *[]) { "cx" /*???*/ },

for all these in the venus driver (plus backwards compat if not already
there). And then add that power domain additionally in the DT.

This series is also introducing new dtbs_check failures :/

qcom/apq8016-sbc.dtb: video-codec@1d00000: Unevaluated properties are not allowed ('operating-points-v2', 'opp-table' were unexpected)                                               
        from schema $id: http://devicetree.org/schemas/media/qcom,msm8916-venus.yaml#         
qcom/apq8096-db820c.dtb: video-codec@c00000: Unevaluated properties are not allowed ('operating-points-v2', 'opp-table' were unexpected)                                             
        from schema $id: http://devicetree.org/schemas/media/qcom,msm8996-venus.yaml#     
qcom/msm8998-lenovo-miix-630.dtb: video-codec@cc00000: Unevaluated properties are not allowed ('operating-points-v2', 'opp-table' were unexpected)                                   
        from schema $id: http://devicetree.org/schemas/media/qcom,msm8996-venus.yaml#       

>       arm64: dts: qcom: sdm845: Fix Venus OPP entries

This one has .opp_pmdomain and "cx" in the bindings, so it's probably
fine (didn't check if the current OPPs are really wrong).

Thanks,
Stephan
Re: [PATCH 0/5] Add missing OPP tables for Venus on qcom/arm64
Posted by Konrad Dybcio 8 months ago 
On 6/2/25 10:09 AM, Stephan Gerhold wrote:
> On Sat, May 31, 2025 at 02:27:18PM +0200, Konrad Dybcio wrote:
>> Sparked by <20250530-add-venus-for-qcs615-v8-0-c0092ac616d0@quicinc.com>
>>
>> No external dependencies
>>
> 
> Are you sure?
> 
>> Signed-off-by: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>
>> ---
>> Konrad Dybcio (5):
>>       arm64: dts: qcom: msm8916: Add Venus OPP table
>>       arm64: dts: qcom: msm8996: Add Venus OPP table
>>       arm64: dts: qcom: msm8998: Add Venus OPP table
>>       arm64: dts: qcom: sdm630: Add Venus OPP table
> 
> None of these platforms has a power domain that supports performance
> states specified in the venus node of the DT, and the venus GDSC does
> not have any parent either. I think you will need to update the venus
> bindings and add
> 
> 	.opp_pmdomain = (const char *[]) { "cx" /*???*/ },
> 
> for all these in the venus driver (plus backwards compat if not already
> there). And then add that power domain additionally in the DT.

Making use of these tables would certainly be welcome.. This patchset
was aimed at pushing them to fdt, so that we can debate dropping the
hardcoded values in the driver in the future.

> 
> This series is also introducing new dtbs_check failures :/
> 
> qcom/apq8016-sbc.dtb: video-codec@1d00000: Unevaluated properties are not allowed ('operating-points-v2', 'opp-table' were unexpected)                                               
>         from schema $id: http://devicetree.org/schemas/media/qcom,msm8916-venus.yaml#         
> qcom/apq8096-db820c.dtb: video-codec@c00000: Unevaluated properties are not allowed ('operating-points-v2', 'opp-table' were unexpected)                                             
>         from schema $id: http://devicetree.org/schemas/media/qcom,msm8996-venus.yaml#     
> qcom/msm8998-lenovo-miix-630.dtb: video-codec@cc00000: Unevaluated properties are not allowed ('operating-points-v2', 'opp-table' were unexpected)                                   
>         from schema $id: http://devicetree.org/schemas/media/qcom,msm8996-venus.yaml#       

Yikes, I didn't check as I assumed the bindings would be common - but
this always seems to bite.

> 
>>       arm64: dts: qcom: sdm845: Fix Venus OPP entries
> 
> This one has .opp_pmdomain and "cx" in the bindings, so it's probably
> fine (didn't check if the current OPPs are really wrong).
> 
> Thanks,
> Stephan
Re: [PATCH 0/5] Add missing OPP tables for Venus on qcom/arm64
Posted by Konrad Dybcio 8 months ago 
On 6/11/25 10:43 PM, Konrad Dybcio wrote:
> On 6/2/25 10:09 AM, Stephan Gerhold wrote:
>> On Sat, May 31, 2025 at 02:27:18PM +0200, Konrad Dybcio wrote:
>>> Sparked by <20250530-add-venus-for-qcs615-v8-0-c0092ac616d0@quicinc.com>
>>>
>>> No external dependencies
>>>
>>
>> Are you sure?
>>
>>> Signed-off-by: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>
>>> ---
>>> Konrad Dybcio (5):
>>>       arm64: dts: qcom: msm8916: Add Venus OPP table
>>>       arm64: dts: qcom: msm8996: Add Venus OPP table
>>>       arm64: dts: qcom: msm8998: Add Venus OPP table
>>>       arm64: dts: qcom: sdm630: Add Venus OPP table
>>
>> None of these platforms has a power domain that supports performance
>> states specified in the venus node of the DT, and the venus GDSC does
>> not have any parent either. I think you will need to update the venus
>> bindings and add
>>
>> 	.opp_pmdomain = (const char *[]) { "cx" /*???*/ },
>>
>> for all these in the venus driver (plus backwards compat if not already
>> there). And then add that power domain additionally in the DT.
> 
> Making use of these tables would certainly be welcome.. This patchset
> was aimed at pushing them to fdt, so that we can debate dropping the
> hardcoded values in the driver in the future.

I don't think we can just plug them in to the driver right now, as
it would also happen to break backwards compat (since
devm_pm_domain_attach_list() seems to not be particularly happy about
missing resources) - though arguments can be made both ways: "it
could have never *really* worked" vs "don't poke at the old driver for
old hardware too much, as it's gonna break"

Konrad
Re: [PATCH 0/5] Add missing OPP tables for Venus on qcom/arm64
Posted by Stephan Gerhold 7 months, 3 weeks ago 
On Wed, Jun 11, 2025 at 10:46:17PM +0200, Konrad Dybcio wrote:
> On 6/11/25 10:43 PM, Konrad Dybcio wrote:
> > On 6/2/25 10:09 AM, Stephan Gerhold wrote:
> >> On Sat, May 31, 2025 at 02:27:18PM +0200, Konrad Dybcio wrote:
> >>> Sparked by <20250530-add-venus-for-qcs615-v8-0-c0092ac616d0@quicinc.com>
> >>>
> >>> No external dependencies
> >>>
> >>
> >> Are you sure?
> >>
> >>> Signed-off-by: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>
> >>> ---
> >>> Konrad Dybcio (5):
> >>>       arm64: dts: qcom: msm8916: Add Venus OPP table
> >>>       arm64: dts: qcom: msm8996: Add Venus OPP table
> >>>       arm64: dts: qcom: msm8998: Add Venus OPP table
> >>>       arm64: dts: qcom: sdm630: Add Venus OPP table
> >>
> >> None of these platforms has a power domain that supports performance
> >> states specified in the venus node of the DT, and the venus GDSC does
> >> not have any parent either. I think you will need to update the venus
> >> bindings and add
> >>
> >> 	.opp_pmdomain = (const char *[]) { "cx" /*???*/ },
> >>
> >> for all these in the venus driver (plus backwards compat if not already
> >> there). And then add that power domain additionally in the DT.
> > 
> > Making use of these tables would certainly be welcome.. This patchset
> > was aimed at pushing them to fdt, so that we can debate dropping the
> > hardcoded values in the driver in the future.
> 
> I don't think we can just plug them in to the driver right now, as
> it would also happen to break backwards compat (since
> devm_pm_domain_attach_list() seems to not be particularly happy about
> missing resources) - though arguments can be made both ways: "it
> could have never *really* worked" vs "don't poke at the old driver for
> old hardware too much, as it's gonna break"
> 

You could just make it ignore the returned error for the call to

	ret = devm_pm_domain_attach_list(dev, &opp_pd_data, &core->opp_pmdomain);

? Perhaps with some extra flag that only enables that for the older
platforms.

I suppose having the DT complete is also helpful, even without the
driver changes. But at the end this would be untested "dead" properties
that may turn out being subtly wrong when someone tries to actually
enable it. So having it properly enabled and tested would be good,
especially since the required changes don't sound too massive and
intrusive to me.

Thanks,
Stephan
Re: [PATCH 0/5] Add missing OPP tables for Venus on qcom/arm64
Posted by Rob Herring (Arm) 8 months, 1 week ago 
On Sat, 31 May 2025 14:27:18 +0200, Konrad Dybcio wrote:
> Sparked by <20250530-add-venus-for-qcs615-v8-0-c0092ac616d0@quicinc.com>
> 
> No external dependencies
> 
> Signed-off-by: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>
> ---
> Konrad Dybcio (5):
>       arm64: dts: qcom: msm8916: Add Venus OPP table
>       arm64: dts: qcom: msm8996: Add Venus OPP table
>       arm64: dts: qcom: msm8998: Add Venus OPP table
>       arm64: dts: qcom: sdm630: Add Venus OPP table
>       arm64: dts: qcom: sdm845: Fix Venus OPP entries
> 
>  arch/arm64/boot/dts/qcom/msm8916.dtsi | 20 ++++++++++++++++++
>  arch/arm64/boot/dts/qcom/msm8996.dtsi | 39 ++++++++++++++++++++++++++++-------
>  arch/arm64/boot/dts/qcom/msm8998.dtsi | 30 +++++++++++++++++++++++++++
>  arch/arm64/boot/dts/qcom/sdm630.dtsi  | 35 +++++++++++++++++++++++++++++++
>  arch/arm64/boot/dts/qcom/sdm845.dtsi  | 24 ++++++++++-----------
>  5 files changed, 128 insertions(+), 20 deletions(-)
> ---
> base-commit: 2a628f951ed54c30a232230b5b58349d2a8dbb11
> change-id: 20250531-topic-venus_opp_arm64-378e98bf6071
> 
> Best regards,
> --
> Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>
> 
> 
> 


My bot found new DTB warnings on the .dts files added or changed in this
series.

Some warnings may be from an existing SoC .dtsi. Or perhaps the warnings
are fixed by another series. Ultimately, it is up to the platform
maintainer whether these warnings are acceptable or not. No need to reply
unless the platform maintainer has comments.

If you already ran DT checks and didn't see these error(s), then
make sure dt-schema is up to date:

  pip3 install dtschema --upgrade


This patch series was applied (using b4) to base:
 Base: using specified base-commit 2a628f951ed54c30a232230b5b58349d2a8dbb11

If this is not the correct base, please add 'base-commit' tag
(or use b4 which does this automatically)

New warnings running 'make CHECK_DTBS=y for arch/arm64/boot/dts/qcom/' for 20250531-topic-venus_opp_arm64-v1-0-54c6c417839f@oss.qualcomm.com:

arch/arm64/boot/dts/qcom/msm8916-samsung-a5u-eur.dtb: video-codec@1d00000 (qcom,msm8916-venus): Unevaluated properties are not allowed ('operating-points-v2', 'opp-table' were unexpected)
	from schema $id: http://devicetree.org/schemas/media/qcom,msm8916-venus.yaml#
arch/arm64/boot/dts/qcom/msm8916-samsung-j3ltetw.dtb: video-codec@1d00000 (qcom,msm8916-venus): Unevaluated properties are not allowed ('operating-points-v2', 'opp-table' were unexpected)
	from schema $id: http://devicetree.org/schemas/media/qcom,msm8916-venus.yaml#
arch/arm64/boot/dts/qcom/apq8096-ifc6640.dtb: video-codec@c00000 (qcom,msm8996-venus): Unevaluated properties are not allowed ('operating-points-v2', 'opp-table' were unexpected)
	from schema $id: http://devicetree.org/schemas/media/qcom,msm8996-venus.yaml#
arch/arm64/boot/dts/qcom/msm8916-samsung-a3u-eur.dtb: video-codec@1d00000 (qcom,msm8916-venus): Unevaluated properties are not allowed ('operating-points-v2', 'opp-table' were unexpected)
	from schema $id: http://devicetree.org/schemas/media/qcom,msm8916-venus.yaml#
arch/arm64/boot/dts/qcom/msm8916-motorola-surnia.dtb: video-codec@1d00000 (qcom,msm8916-venus): Unevaluated properties are not allowed ('operating-points-v2', 'opp-table' were unexpected)
	from schema $id: http://devicetree.org/schemas/media/qcom,msm8916-venus.yaml#
arch/arm64/boot/dts/qcom/msm8916-wingtech-wt88047.dtb: video-codec@1d00000 (qcom,msm8916-venus): Unevaluated properties are not allowed ('operating-points-v2', 'opp-table' were unexpected)
	from schema $id: http://devicetree.org/schemas/media/qcom,msm8916-venus.yaml#
arch/arm64/boot/dts/qcom/msm8916-thwc-ufi001c.dtb: video-codec@1d00000 (qcom,msm8916-venus): Unevaluated properties are not allowed ('operating-points-v2', 'opp-table' were unexpected)
	from schema $id: http://devicetree.org/schemas/media/qcom,msm8916-venus.yaml#
arch/arm64/boot/dts/qcom/msm8916-motorola-osprey.dtb: video-codec@1d00000 (qcom,msm8916-venus): Unevaluated properties are not allowed ('operating-points-v2', 'opp-table' were unexpected)
	from schema $id: http://devicetree.org/schemas/media/qcom,msm8916-venus.yaml#
arch/arm64/boot/dts/qcom/msm8916-motorola-harpia.dtb: video-codec@1d00000 (qcom,msm8916-venus): Unevaluated properties are not allowed ('operating-points-v2', 'opp-table' were unexpected)
	from schema $id: http://devicetree.org/schemas/media/qcom,msm8916-venus.yaml#
arch/arm64/boot/dts/qcom/msm8916-samsung-e5.dtb: video-codec@1d00000 (qcom,msm8916-venus): Unevaluated properties are not allowed ('operating-points-v2', 'opp-table' were unexpected)
	from schema $id: http://devicetree.org/schemas/media/qcom,msm8916-venus.yaml#
arch/arm64/boot/dts/qcom/msm8916-samsung-rossa.dtb: video-codec@1d00000 (qcom,msm8916-venus): Unevaluated properties are not allowed ('operating-points-v2', 'opp-table' were unexpected)
	from schema $id: http://devicetree.org/schemas/media/qcom,msm8916-venus.yaml#
arch/arm64/boot/dts/qcom/apq8016-sbc-d3-camera-mezzanine.dtb: video-codec@1d00000 (qcom,msm8916-venus): Unevaluated properties are not allowed ('operating-points-v2', 'opp-table' were unexpected)
	from schema $id: http://devicetree.org/schemas/media/qcom,msm8916-venus.yaml#
arch/arm64/boot/dts/qcom/msm8998-lenovo-miix-630.dtb: video-codec@cc00000 (qcom,msm8998-venus): Unevaluated properties are not allowed ('operating-points-v2', 'opp-table' were unexpected)
	from schema $id: http://devicetree.org/schemas/media/qcom,msm8996-venus.yaml#
arch/arm64/boot/dts/qcom/msm8916-samsung-grandmax.dtb: video-codec@1d00000 (qcom,msm8916-venus): Unevaluated properties are not allowed ('operating-points-v2', 'opp-table' were unexpected)
	from schema $id: http://devicetree.org/schemas/media/qcom,msm8916-venus.yaml#
arch/arm64/boot/dts/qcom/msm8916-alcatel-idol347.dtb: video-codec@1d00000 (qcom,msm8916-venus): Unevaluated properties are not allowed ('operating-points-v2', 'opp-table' were unexpected)
	from schema $id: http://devicetree.org/schemas/media/qcom,msm8916-venus.yaml#
arch/arm64/boot/dts/qcom/msm8916-samsung-e7.dtb: video-codec@1d00000 (qcom,msm8916-venus): Unevaluated properties are not allowed ('operating-points-v2', 'opp-table' were unexpected)
	from schema $id: http://devicetree.org/schemas/media/qcom,msm8916-venus.yaml#
arch/arm64/boot/dts/qcom/apq8096-db820c.dtb: video-codec@c00000 (qcom,msm8996-venus): Unevaluated properties are not allowed ('operating-points-v2', 'opp-table' were unexpected)
	from schema $id: http://devicetree.org/schemas/media/qcom,msm8996-venus.yaml#
arch/arm64/boot/dts/qcom/msm8916-longcheer-l8150.dtb: video-codec@1d00000 (qcom,msm8916-venus): Unevaluated properties are not allowed ('operating-points-v2', 'opp-table' were unexpected)
	from schema $id: http://devicetree.org/schemas/media/qcom,msm8916-venus.yaml#
arch/arm64/boot/dts/qcom/msm8916-yiming-uz801v3.dtb: video-codec@1d00000 (qcom,msm8916-venus): Unevaluated properties are not allowed ('operating-points-v2', 'opp-table' were unexpected)
	from schema $id: http://devicetree.org/schemas/media/qcom,msm8916-venus.yaml#
arch/arm64/boot/dts/qcom/msm8916-samsung-j5.dtb: video-codec@1d00000 (qcom,msm8916-venus): Unevaluated properties are not allowed ('operating-points-v2', 'opp-table' were unexpected)
	from schema $id: http://devicetree.org/schemas/media/qcom,msm8916-venus.yaml#
arch/arm64/boot/dts/qcom/msm8996-xiaomi-gemini.dtb: video-codec@c00000 (qcom,msm8996-venus): Unevaluated properties are not allowed ('operating-points-v2', 'opp-table' were unexpected)
	from schema $id: http://devicetree.org/schemas/media/qcom,msm8996-venus.yaml#
arch/arm64/boot/dts/qcom/msm8916-samsung-gprimeltecan.dtb: video-codec@1d00000 (qcom,msm8916-venus): Unevaluated properties are not allowed ('operating-points-v2', 'opp-table' were unexpected)
	from schema $id: http://devicetree.org/schemas/media/qcom,msm8916-venus.yaml#
arch/arm64/boot/dts/qcom/msm8996-oneplus3t.dtb: video-codec@c00000 (qcom,msm8996-venus): Unevaluated properties are not allowed ('operating-points-v2', 'opp-table' were unexpected)
	from schema $id: http://devicetree.org/schemas/media/qcom,msm8996-venus.yaml#
arch/arm64/boot/dts/qcom/msm8916-longcheer-l8910.dtb: video-codec@1d00000 (qcom,msm8916-venus): Unevaluated properties are not allowed ('operating-points-v2', 'opp-table' were unexpected)
	from schema $id: http://devicetree.org/schemas/media/qcom,msm8916-venus.yaml#
arch/arm64/boot/dts/qcom/msm8916-lg-c50.dtb: video-codec@1d00000 (qcom,msm8916-venus): Unevaluated properties are not allowed ('operating-points-v2', 'opp-table' were unexpected)
	from schema $id: http://devicetree.org/schemas/media/qcom,msm8916-venus.yaml#
arch/arm64/boot/dts/qcom/msm8916-samsung-grandprimelte.dtb: video-codec@1d00000 (qcom,msm8916-venus): Unevaluated properties are not allowed ('operating-points-v2', 'opp-table' were unexpected)
	from schema $id: http://devicetree.org/schemas/media/qcom,msm8916-venus.yaml#
arch/arm64/boot/dts/qcom/msm8916-samsung-j5x.dtb: video-codec@1d00000 (qcom,msm8916-venus): Unevaluated properties are not allowed ('operating-points-v2', 'opp-table' were unexpected)
	from schema $id: http://devicetree.org/schemas/media/qcom,msm8916-venus.yaml#
arch/arm64/boot/dts/qcom/msm8916-samsung-gt58.dtb: video-codec@1d00000 (qcom,msm8916-venus): Unevaluated properties are not allowed ('operating-points-v2', 'opp-table' were unexpected)
	from schema $id: http://devicetree.org/schemas/media/qcom,msm8916-venus.yaml#
arch/arm64/boot/dts/qcom/apq8016-sbc.dtb: video-codec@1d00000 (qcom,msm8916-venus): Unevaluated properties are not allowed ('operating-points-v2', 'opp-table' were unexpected)
	from schema $id: http://devicetree.org/schemas/media/qcom,msm8916-venus.yaml#
arch/arm64/boot/dts/qcom/msm8996pro-xiaomi-natrium.dtb: video-codec@c00000 (qcom,msm8996-venus): Unevaluated properties are not allowed ('operating-points-v2', 'opp-table' were unexpected)
	from schema $id: http://devicetree.org/schemas/media/qcom,msm8996-venus.yaml#
arch/arm64/boot/dts/qcom/msm8996pro-xiaomi-scorpio.dtb: video-codec@c00000 (qcom,msm8996-venus): Unevaluated properties are not allowed ('operating-points-v2', 'opp-table' were unexpected)
	from schema $id: http://devicetree.org/schemas/media/qcom,msm8996-venus.yaml#
arch/arm64/boot/dts/qcom/msm8916-samsung-serranove.dtb: video-codec@1d00000 (qcom,msm8916-venus): Unevaluated properties are not allowed ('operating-points-v2', 'opp-table' were unexpected)
	from schema $id: http://devicetree.org/schemas/media/qcom,msm8916-venus.yaml#
arch/arm64/boot/dts/qcom/msm8916-lg-m216.dtb: video-codec@1d00000 (qcom,msm8916-venus): Unevaluated properties are not allowed ('operating-points-v2', 'opp-table' were unexpected)
	from schema $id: http://devicetree.org/schemas/media/qcom,msm8916-venus.yaml#
arch/arm64/boot/dts/qcom/msm8996-oneplus3.dtb: video-codec@c00000 (qcom,msm8996-venus): Unevaluated properties are not allowed ('operating-points-v2', 'opp-table' were unexpected)
	from schema $id: http://devicetree.org/schemas/media/qcom,msm8996-venus.yaml#
arch/arm64/boot/dts/qcom/msm8916-asus-z00l.dtb: video-codec@1d00000 (qcom,msm8916-venus): Unevaluated properties are not allowed ('operating-points-v2', 'opp-table' were unexpected)
	from schema $id: http://devicetree.org/schemas/media/qcom,msm8916-venus.yaml#
arch/arm64/boot/dts/qcom/msm8916-thwc-uf896.dtb: video-codec@1d00000 (qcom,msm8916-venus): Unevaluated properties are not allowed ('operating-points-v2', 'opp-table' were unexpected)
	from schema $id: http://devicetree.org/schemas/media/qcom,msm8916-venus.yaml#
arch/arm64/boot/dts/qcom/msm8916-samsung-gt510.dtb: video-codec@1d00000 (qcom,msm8916-venus): Unevaluated properties are not allowed ('operating-points-v2', 'opp-table' were unexpected)
	from schema $id: http://devicetree.org/schemas/media/qcom,msm8916-venus.yaml#
arch/arm64/boot/dts/qcom/msm8916-huawei-g7.dtb: video-codec@1d00000 (qcom,msm8916-venus): Unevaluated properties are not allowed ('operating-points-v2', 'opp-table' were unexpected)
	from schema $id: http://devicetree.org/schemas/media/qcom,msm8916-venus.yaml#
arch/arm64/boot/dts/qcom/msm8916-wingtech-wt86518.dtb: video-codec@1d00000 (qcom,msm8916-venus): Unevaluated properties are not allowed ('operating-points-v2', 'opp-table' were unexpected)
	from schema $id: http://devicetree.org/schemas/media/qcom,msm8916-venus.yaml#
arch/arm64/boot/dts/qcom/msm8916-gplus-fl8005a.dtb: video-codec@1d00000 (qcom,msm8916-venus): Unevaluated properties are not allowed ('operating-points-v2', 'opp-table' were unexpected)
	from schema $id: http://devicetree.org/schemas/media/qcom,msm8916-venus.yaml#
arch/arm64/boot/dts/qcom/msm8916-wingtech-wt86528.dtb: video-codec@1d00000 (qcom,msm8916-venus): Unevaluated properties are not allowed ('operating-points-v2', 'opp-table' were unexpected)
	from schema $id: http://devicetree.org/schemas/media/qcom,msm8916-venus.yaml#
arch/arm64/boot/dts/qcom/msm8916-acer-a1-724.dtb: video-codec@1d00000 (qcom,msm8916-venus): Unevaluated properties are not allowed ('operating-points-v2', 'opp-table' were unexpected)
	from schema $id: http://devicetree.org/schemas/media/qcom,msm8916-venus.yaml#
arch/arm64/boot/dts/qcom/msm8216-samsung-fortuna3g.dtb: video-codec@1d00000 (qcom,msm8916-venus): Unevaluated properties are not allowed ('operating-points-v2', 'opp-table' were unexpected)
	from schema $id: http://devicetree.org/schemas/media/qcom,msm8916-venus.yaml#

Patchew 2.1-devel-b67e4c2

© 2016 - 2026 Red Hat, Inc.