linux-kernel - Re: [PATCH 1/8] media: dt-bindings: qcom-kaanapali-iris: Add kaanapali video codec binding

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <09d08a54-2a84-42db-bbab-050dc1487f6e@kernel.org>
Date: Tue, 7 Oct 2025 22:58:12 +0900
From: Krzysztof Kozlowski <krzk@...nel.org>
To: Vikash Garodia <vikash.garodia@....qualcomm.com>,
 Dmitry Baryshkov <dmitry.baryshkov@....qualcomm.com>
Cc: Konrad Dybcio <konrad.dybcio@....qualcomm.com>,
 Dikshita Agarwal <dikshita.agarwal@....qualcomm.com>,
 Abhinav Kumar <abhinav.kumar@...ux.dev>, Bryan O'Donoghue <bod@...nel.org>,
 Mauro Carvalho Chehab <mchehab@...nel.org>, Rob Herring <robh@...nel.org>,
 Krzysztof Kozlowski <krzk+dt@...nel.org>, Conor Dooley
 <conor+dt@...nel.org>, Philipp Zabel <p.zabel@...gutronix.de>,
 linux-arm-msm@...r.kernel.org, linux-media@...r.kernel.org,
 devicetree@...r.kernel.org, linux-kernel@...r.kernel.org,
 Vishnu Reddy <quic_bvisredd@...cinc.com>
Subject: Re: [PATCH 1/8] media: dt-bindings: qcom-kaanapali-iris: Add
 kaanapali video codec binding

On 02/10/2025 18:18, Vikash Garodia wrote:
>>>     then:
>>>       properties:
>>>         power-domains:
>>>           maxItems: 6
>>>
>>>     else:
>>>       properties:
>>>         power-domains:
>>>           maxItems: 7
>>>
>>> Also, what is the downside in existing approach where we say that the hardware
>>> can be functional with 5 pds, and 2 are optional based on hardware having them
>>> or not ? So all combinations of [5, 6, 7] pds are valid. IIUC, the optional
>>> entries are made for such cases where some hardware parts are variable, please
>>> correct my understanding.
>>
>> Kaanapali hardware is not variable, is it?
> 
> By variable i meant the hardware is functional with or without those bindings,
> hence was keeping them as an interface but optional. If that fits into optional
> category, i can keep it existing way, otherwise will update to fix binding.

You describe here how SoC is wired/engineered/created. Can you create a
board with the Kaanapali SoC where the power domain is not there?

Best regards,
Krzysztof