linux-kernel - Re: [PATCH v2 1/3] dt-bindings: i2c: qcom-cci: Document qcs8300 compatible

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: <fd075b5f-3766-474a-bffe-c1c402cfca81@quicinc.com>
Date: Wed, 17 Sep 2025 11:52:41 +0530
From: Nihal Kumar Gupta <quic_nihalkum@...cinc.com>
To: Konrad Dybcio <konrad.dybcio@....qualcomm.com>,
        Rob Herring
	<robh@...nel.org>,
        Vikram Sharma <quic_vikramsa@...cinc.com>
CC: <vladimir.zapolskiy@...aro.org>, <bryan.odonoghue@...aro.org>,
        <mchehab@...nel.org>, <krzk+dt@...nel.org>, <conor+dt@...nel.org>,
        <andersson@...nel.org>, <konradybcio@...nel.org>,
        <hverkuil-cisco@...all.nl>, <cros-qcom-dts-watchers@...omium.org>,
        <catalin.marinas@....com>, <will@...nel.org>,
        <linux-arm-kernel@...ts.infradead.org>, <quic_svankada@...cinc.com>,
        <linux-media@...r.kernel.org>, <linux-arm-msm@...r.kernel.org>,
        <devicetree@...r.kernel.org>, <linux-kernel@...r.kernel.org>,
        Ravi Shankar <quic_rshankar@...cinc.com>
Subject: Re: [PATCH v2 1/3] dt-bindings: i2c: qcom-cci: Document qcs8300
 compatible



On 16-09-2025 16:41, Konrad Dybcio wrote:
>>> Wrap commit messages at 72 chars. And explain how it's the same or 
>>> different from existing SoCs in the commit message. Don't explain the 
>>> diff. We can read that ourselves.
>>>
>> SA8775P(Lemans) has 4 CCIs, while QCS8300 (Monaco) has 3 CCI, with the 
>> only difference being the GPIOs used for SDA/SCL pins.
>>
>> Currently, the CCI driver probe happens through the "qcom,msm8996-cci" 
>> compatible string. Could we use the existing SA8775P compatible string
>> "qcom,sa8775p-cci" or we should remove it? 
>>
>> Please advise on the preferred approach for upstream compliance.
> Try:
> 
> """
> The three instances of CCI found on the QCS8300 are functionally
> the same as on a number of existing Qualcomm SoCs.
> 
> Introduce a new SoC-specific compatible, with a common fallback.
> """
> 

ACK, Will address this in next version.
> Konrad