linux-kernel - Re: [PATCH V2 1/6] dt-bindings: clock: qcom: Add SM8550 camera clock controller

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] [thread-next>] [day] [month] [year] [list]

Date:   Wed, 31 May 2023 21:20:59 +0200
From:   Krzysztof Kozlowski <krzysztof.kozlowski@...aro.org>
To:     Bryan O'Donoghue <bryan.odonoghue@...aro.org>,
        Jagadeesh Kona <quic_jkona@...cinc.com>,
        Andy Gross <agross@...nel.org>,
        Michael Turquette <mturquette@...libre.com>,
        Stephen Boyd <sboyd@...nel.org>,
        Rob Herring <robh+dt@...nel.org>,
        Krzysztof Kozlowski <krzysztof.kozlowski+dt@...aro.org>,
        Conor Dooley <conor+dt@...nel.org>
Cc:     Bjorn Andersson <andersson@...nel.org>,
        Konrad Dybcio <konrad.dybcio@...aro.org>,
        Vladimir Zapolskiy <vladimir.zapolskiy@...aro.org>,
        Vinod Koul <vkoul@...nel.org>, linux-arm-msm@...r.kernel.org,
        linux-clk@...r.kernel.org, devicetree@...r.kernel.org,
        linux-kernel@...r.kernel.org, Taniya Das <quic_tdas@...cinc.com>,
        Satya Priya Kakitapalli <quic_skakitap@...cinc.com>,
        Imran Shaik <quic_imrashai@...cinc.com>,
        Ajit Pandey <quic_ajipan@...cinc.com>
Subject: Re: [PATCH V2 1/6] dt-bindings: clock: qcom: Add SM8550 camera clock
 controller

On 26/05/2023 14:29, Bryan O'Donoghue wrote:
> On 25/05/2023 18:21, Jagadeesh Kona wrote:
>> Add device tree bindings for the camera clock controller on
>> Qualcomm SM8550 platform.
>>
>> Signed-off-by: Taniya Das <quic_tdas@...cinc.com>
>> Signed-off-by: Jagadeesh Kona <quic_jkona@...cinc.com>
>> ---
>> Changes since V1:
>>   - Removed new YAML file and reused SM8450 CAMCC YAML file for SM8550
>>
>>   .../bindings/clock/qcom,sm8450-camcc.yaml     |   8 +-
>>   include/dt-bindings/clock/qcom,sm8550-camcc.h | 187 ++++++++++++++++++
>>   2 files changed, 193 insertions(+), 2 deletions(-)
>>   create mode 100644 include/dt-bindings/clock/qcom,sm8550-camcc.h
>>
>> diff --git a/Documentation/devicetree/bindings/clock/qcom,sm8450-camcc.yaml b/Documentation/devicetree/bindings/clock/qcom,sm8450-camcc.yaml
>> index 87ae74166807..8dbc9004202f 100644
>> --- a/Documentation/devicetree/bindings/clock/qcom,sm8450-camcc.yaml
>> +++ b/Documentation/devicetree/bindings/clock/qcom,sm8450-camcc.yaml
>> @@ -13,11 +13,15 @@ description: |
>>     Qualcomm camera clock control module provides the clocks, resets and power
>>     domains on SM8450.
>>   
>> -  See also:: include/dt-bindings/clock/qcom,sm8450-camcc.h
>> +  See also::
>> +    include/dt-bindings/clock/qcom,sm8450-camcc.h
>> +    include/dt-bindings/clock/qcom,sm8550-camcc.h
>>   
>>   properties:
>>     compatible:
>> -    const: qcom,sm8450-camcc
>> +    enum:
>> +      - qcom,sm8450-camcc
>> +      - qcom,sm8550-camcc
> 
> Hmm,
> 
> So looking at Documentation/devicetree/bindings/clock/*camcc*.yaml we 
> seem to be repeating yaml over and over again with no substantial 
> difference between one description and another.
> 
> You've picked at the thread here by adding sm8550 into sm8450.
> 
> I think sm8250, sm8450, sm8550, sc7280 and ... probably sm6350 should 
> live in the one yaml description 
> Documentation/devicetree/bindings/clock/qcom,camcc.yaml
> 
> sm6350 looks a bit sparse/incomplete to me so perhaps leave that out. 
> The others sc7280, sm8250, sm8450 and sm8550 can/should all be moved 
> into the same yaml file with a list of compatibles.

Clocks are different. The ones with same clocks should be together, but
in other cases better to have separate schemas. It gets trickier to read
with multiple if:then:

Best regards,
Krzysztof